#KRITA LINUX PORTABLE#

He comes across as just an average Puppy user, but he helps far more people than I do, and indeed many others, too. His posts are NEVER 'boring'.and are always worth reading. He's often able to dig things up that even I would have trouble finding! 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. Mike is extremely knowledgeable about pretty much most aspects of Puppy. 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.ĭon't let him fool you. 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's been here with us for several years longer than I have. Michael is a very long-standing member of this community. A wee bit of background is in order at this point, I think. Then just rearrange the layers? As long as the layers are created transparent that would work, or maybe I misunderstand your requirement.

Then create a new layer for your background. Well, now to actually learn enough about krita to actually do what it says it can.Īlso, 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).

But see my post 3 down (after MikeWalsh's). Have to open a terminal (in the folder) and type kt. With the 'kt' script made executable, krita starts and seems to r un OK when 'kt' is left-clicked. The krita appimage provided the AppRun file as a symbolic link to the /usr/bin/krita binary within the krita folder. 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. I don't think the line beginning with 'mkdir' is necessary. LD_LIBRARY_PATH=$LAUNCHDIR/:$LAUNCHDIR/usr/ $ '$LAUNCHDIR/krita/AppRun' sorry about the use of 'tiny' for the last line otherwise it displays as 2 lines which might cause even more confusion.

#KRITA LINUX PORTABLE#

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:ġ) Created a 'containing folder' named krita-portable.Ģ) Copied the extracted krita folder -just renamed krita- into it.ģ) Literally stole fredx181's 'ff' script from portable firefox.Ĥ) Renamed the script 'kt' and copied it into the krita-portable folder, adjacent to the 'krita' folder. Starting it from a terminal revealed the it was trying to 'mix' its libraries with those provided by my operating system, Fossapup64. While krita does.īut every recent version of Krita available as a AppImage failed to open. Except, it turns out that gimp doesn't seem to permit separately saving 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 (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, obviously you draw the background first, then paste the foreground elements into it.

Krita linux