krita-5.0.6-x86_64 --portablized for Fossapup64

[mikeslr]

Why Krita? I can't draw worth a damn. But I can cut and paste. Great for foregrounds. But what if you want a background. Well, obviously you draw the background first, then paste the foreground elements into it. Except (a) you may not know in advance what you want your background to look like; and (b) I wasn't thinking that far ahead and now had the foreground.
Well, gimp employs layers. So the easy way is to create a layer, draw the background over it, save the background layer separately, then load them: first the background, then the foreground. Except, it turns out that gimp doesn't seem to permit separately saving layers. While krita does.

But every recent version of Krita available as a AppImage failed to open. Starting it from a terminal revealed the it was trying to 'mix' its libraries with those provided by my operating system, Fossapup64.

So, after creating a portable --see the discussion here-- viewtopic.php?p=57775#p57775-- I flinched a technique from fredx181's portable firefox, and MikeWalsh:
1) Created a 'containing folder' named krita-portable.
2) Copied the extracted krita folder --just renamed krita-- into it.
3) Literally stole fredx181's 'ff' script from portable firefox.
4) Renamed the script 'kt' and copied it into the krita-portable folder, adjacent to the 'krita' folder.
5) Edited the 'kt' script to just read:

#!/bin/sh

#LAUNCHDIR="$(cd "$(dirname "$0")"; pwd)"
LAUNCHDIR="$(dirname "$(readlink -f "$0")")"
mkdir "$LAUNCHDIR/base" 2> /dev/null
LD_LIBRARY_PATH=$LAUNCHDIR/:$LAUNCHDIR/usr/${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} "$LAUNCHDIR/krita/AppRun" "$@"

Note, sorry about the use of 'tiny' for the last line; otherwise it displays as 2 lines which might cause even more confusion.
I don't think the line beginning with 'mkdir' is necessary. But it doesn't hurt.
The 'AppRun' of the last line is what starts krita after the 'LD_LIBRARY_PATH...' instructs it to ONLY look within its folder for libraries. The krita appimage provided the AppRun file as a symbolic link to the /usr/bin/krita binary within the krita folder.

With the 'kt' script made executable, krita starts and seems to run OK when 'kt' is left-clicked.
. Edit: No it doesn't. Have to open a terminal (in the folder) and type kt. Will investigate. But see my post 3 down (after MikeWalsh's).
-=-=-=-=-
Well, now to actually learn enough about krita to actually do what it says it can.

DOWNLOAD from here:
https://krita.org/en/download/krita-desktop/

[sfein1000]

I always welcome portables, but...
I'm surprised you've had issues. I've been running krita-5.0.6-x86_64.appimage on Fossapup64 for a couple of weeks now. I do not have a savefile/folder so I wonder if maybe it's one of your saved settings.

Also, not an expert in Gimp by any stretch of the imagination, but couldn't you create your first layer (in your example this is the foreground I guess). Do your drawing. Then create a new layer for your background. Draw on it. Then just rearrange the layers? As long as the layers are created transparent that would work, or maybe I misunderstand your requirement.

In any case, this thread is about your portable and as mentioned, portables are good alternatives to appimages. I swap between my Firefox portable and appimage versions depending on my mood. Portable are especially nice when there is an app update.

[mikewalsh]

@sfein1000 :-

Also, not an expert in Gimp by any stretch of the imagination, but couldn't you create your first layer (in your example this is the foreground I guess). Do your drawing. Then create a new layer for your background. Draw on it. Then just rearrange the layers? As long as the layers are created transparent that would work, or maybe I misunderstand your requirement.

^^^ Lololol!

Heh. A wee bit of background is in order at this point, I think. Just for "future reference", like....

Michael is a very long-standing member of this community. He's been here with us for several years longer than I have.

Whether because of his legal background, or not - I couldn't say - Mike likes to post threads/posts in what I call "thought-provoking" mode. He often poses questions, or aspects of Puppy, in such a way as to make the rest of us think; is such-and-such readily understandable by those unfamiliar with Puppy? Would noobs understand something? Would they be able to figure stuff out by themselves? Etc, etc...

Don't let him fool you. Mike is extremely knowledgeable about pretty much most aspects of Puppy. It's very rare that he posts what you would call a genuine "plea for help"; again, I would hazard a guess that his legal training means he's very good at researching things. He's often able to dig things up that even I would have trouble finding!

One thing's for sure, though. His posts are NEVER "boring"....and are always worth reading. He comes across as just an average Puppy user, but he helps far more people than I do, and indeed many others, too.

He's one of our unofficial "community advisors", and as such garners a lot more respect than he would have you believe! He's one of the "good guys", for sure.

(As for his technique in the first post, you'll get used to that with us. We often "borrow" methods and ways of doing things from each other; it's quite normal for this community, and is a back-handed way of complimenting somebody who's developed a way of doing something that proves useful for everyone....)

Mike.

[mikeslr]

Thanks, Mike, for the complement. Self denigrating explanation follows after important status report.

I'm about to steal some more of your work. Seems krita writes config files to /root. I recall that within the last year or so your LAUNCH scripts for some portable-apps --e.g. Kodi?-- have included arguments to move files out of /root into the portable folder then symlink them back.

Still don't know why krita can be started by opening a terminal issuing the name of the script as a command; but can't be started by Left-Clicking the script. I'll try to ferret out the impediment starting by re-examining the LAUNCH scripts you've used. They do work for their respective portables. But it may not be all that important if moving the script onto 'the path' and/or as the Exec= argument in a /usr/share/desktop opens 'the portable'.
-=-=-=-=-=-
The fact is that I have (probably always had) a piss-poor memory. But I always have had the ability to visualize a situation and its changes. A life-time ago while in college I had submit a report about something. I used to remember what; but by now I've forgotten that. But I remember where in the 'open-stacks' Library --on what floor, in what stack, and where on the stack a book I quoted was to be found. There's a picture in my mind of me being at the stack and opening the book.

Do you remember learning about vectors in physics and valences in chemistry and the diagrams used to represent changes. Well, that's sort of how my mind works. I see systems; patterns.

"Everyone is presumed to know the Law", is a Legal Principle of necessity because in its absence no one could ever be held responsible or guilty. The truth is that beyond a vague impression no one knows the "Law". It is a knowledge tree with far too many branches, constantly changing with some branches becoming obsolete or growing to overshadow others. Attorneys in specialized substantive fields (e.g. Civil Rights, Divorce, Medical Malpractice) could limit their acquisition of current knowledge to the cases being reported in their field; and the Legal Periodicals analyzing those cases. As an attorney specializing in Appellate and Bankruptcy Practice, I only had to know the rarely changing procedures of those Courts. But the substantive Law applicable applicable to my client's problem could be anything: e.g. one day, a dog bite case; the next, what Laws were applicable in a suit brought by a German citizen and resident cheated by an American Brokerage firm.

I never made the mistake of thinking I knew the Law. I only knew 'where to find it.' And that gave me an advantage. Specialists frequently operate with 'tunnel vision'. I had a vague idea of what developments were taking place in all fields of Law and an appreciation of which had precedence and which ran contrary to that vague feeling called Justice that Appellate and Bankruptcy Judges stove to render. All I had to do was the hard work of finding influential cases that supported 'Justice' as my clients saw it.

As far as spelling things out, well, you're right. My Practice has influenced how and why I write. Among my clients as a Bankruptcy attorney were lawyers and doctors, and just ordinary folk trying to get by on an hourly wage who may not have finished High School and may not have English as their 'mother-tongue'. My ethical obligation was not merely to represent them; but to clearly explain to them what was happening, what options they had, and why. My obligation was not to do what I thought best for them; but to do 'what they thought best if they had my knowledge'.
As an Appellate Attorney, I knew that the Judges before whom I appeared were likely to have been 'specialists' and, thus, have little actual knowledge of he substantive law of the case now before them. And certainly no knowledge of the facts of that case beyond what they learned from my Brief (essay) and that of my opposing counsels.

So, in writing about 'How to get things done' under Puppys, I begin with the idea that I know nothing beyond that I see systems. The question I ask is 'What do I have to change to alter that system to accomplish my goal.' I then spell out what I did figuring someone else, also knowing nothing, may find my recipe useful. I figure if they already know something they can quickly scan through the 'known' parts.

[bigpup]

Thanks for this!

I am looking in the first post.
Where is the download link?

[mikeslr]

Thanks for this!

I am looking in the first post.
Where is the download link?

Thought I had provided it. Told you I had a piss-poor memory. It's here, https://krita.org/en/download/krita-desktop/

[maifan]

Thanks for sharing! your info give me some guidance.
Krita is free yet great for digital painting on Linux, I love it very much.