(NOTICE:- Jonno Thomas & co don't like you using older versions of Openshot; there's no link to a repo of older releases on the main site. However, for anyone wanting older, 2-series Qt5 AppImage versions - for whatever reason! - they can be found at the project's Github page:-
https://github.com/OpenShot/openshot-qt/releases )
------------------------------------------------------------------
Evening, gang.
Here's a pair of portable video-editors that combine the best aspects of both the AppImage and the 'portable' format.
OpenshotQT-portable & Shotcut-portable
Many of you know by now that I'm a huge fan of the AppImage format. Loads & loads of these apps will run happily in Puppy; some need a bit of tweaking.....some won't run at all. Nevertheless, where they do run, there's always that one 'side-effect' I'm NOT so keen on; everywhere you run them, they leave behind permanent config files and/or caches.
This is fine if you only ever run one Puppy. Many of us like to run more than one, and for this situation, there's one of two solutions. You either :-
- have a 'common' copy of those config files, sym-linked into each Puppy at the appropriate location, or....
- you have a single copy of those files, contained within the portable itself, which are used by the application every single time it runs (and which leave no trace behind).
The latter is the approach taken with these portable applications. It's more effective, because this way you can run the app from a flash-drive for the ultimate in portability if you want to, and move from one machine to another. You're not limited to a single machine.
----------------------------------------------------
Each 'portable' contains an AppImage, and a 'Launch' script. On the first run, a config directory is created beside them, and another directory, of exactly the name the app is expecting to create for its profile, is created inside that.
At run-time, the inner 'config' directory - empty at this point - is sym-linked out to the location where the app normally creates it with a standard package install. The first run then 'populates' the config directory.....but because this is a sym-link, it's really writing this stuff into the portable directory. The app reads data from where it expects to find it, and fires up.
At shut-down, the sym-link is then removed.
--------------------------------------------------
And the best bit about all this? If, as & when you want to upgrade to a newer version - which usually occurs sooner or later! - I, personally, don't need to re-build these any more. All that is necessary is for you, the Puppy user, to visit each app's respective website & download the newest available AppImage. Once you have it, unzip it if required - some zip them, some don't - and re-name the AppImage to match the one you have in the portable, removing the .AppImage suffix in the process. You can do this, because AppImages can be re-named to absolutely anything you like, as long or as short as you want; it's the 'act' of clicking on the outer layer of an AppImage that transfers the executable action to the "AppRun "script within. This is what ultimately sets things in motion.
Then, just swap the old AppImage for the new one.... Sorted.
You can find the two portable video editors at the following locations :-
Navigate through, and help yourselves to the one you want, along with MD5sum if required.
-------------------------------------------------
URLs to obtain the newest versions of the AppImages are as follows (these are direct links):-
Resources
Quick-start tutorials:-
---------------------------------------------------------------------
Both of these are very powerful, yet pretty simple to use. Even 'noobs' get on well with them after just a short while. Hope they're useful for some of you. Enjoy! 
Mike. 
