I have some time to kill every couple days, and a basic understanding of programming, so is there a guide that's a bit more detailed than the one at https://portableapps.com/development ? I want to see if I can take programs (open source, obviously)that are already psuedo-portable (like in a .zip or .7z archive), and just make a .paf out of that. Nothing special, just writing paths, adding a splash PA logo, and then making the .paf itself.
New: System Informer (Apr 21, 2024), Platform 29.5 (Apr 24, 2024)
1,000+ portable packages, 1.1 billion downloads
Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
digitxp was working on some unofficial PAF specs recently, possibly check those out. Package the app up using the best possible launcher, change everything within the directories under AppNamePortable, and post the installer. If you have any problems, let us know. Once it's posted, I'll catch all the small stuff like icon formats, compression, etc so you'll have a better understanding.
Let me rephrase it. Basic programming skills. As in, I didn't understand the last 2 sentences of what you just said. Think you could dumb it down a bit, to incredibly tiny steps?
Oh, I also saw this http://nascent-project.org/digitxp/PAF%20Specs/PAFSpecs.html in a forum search. That seems like it would be useful.
Ok, I did some digging and I think I did it right, but how exactly do I make the .paf itself? Because I made myself a test app using that link, and then I made a folder, but how do I get it into the executable?
Use the installer .nsi file in \Source to compile the app into the .paf.exe installer. You need to edit that one for your app too before you use it.
While you're at it, check info on this site out: http://cubegames.net/development/
Cancer Survivors -- Remember the fight, celebrate the victory!
Help control the rugrat population -- have yourself spayed or neutered!
Buddha, I went there and saw this: "To make a PortableApps.com Installer, download the latest release and copy Installer.nsi to AppNamePortable\Other\AppNamePortableSource\Installer.nsi and edit the details inside"
Where do I get the installer.nsi from?
from an existing portable app...all the stuff you need is included, and just has to be modified to match your setup.
If the app you are attempting to make portable uses the registry, look at 7-zip Portable for the launcher setup.
If the app you want to make portable uses a simple settings file, look at SumatraPDF Portable for the launcher setup.
If the app you want to make portable uses APPDATA or USERPROFILE, look at KompoZer Portable for the launcher setup.
I'd recommend taking the installer.nsi from SumatraPDF, because some of the other apps need special pre-install work to be done with them.
The developer formerly known as ZGitRDun8705
"installer.nsi" is the old name, and PortableSource is the old location. Newer packages use the name PortableApps.comInstaller.nsi. The NSI files are already in Other\Source, and should stay there, in the current state of the launcher/installer evolution.
If you download one of the recent releases, say, WinDirStat Portable, you'll have all of the source code in the Other\Source directory. You'll also need the Developer splash screen image (search for it) in the same directory and named (in this example) WinDirStatPortable.jpg (leave the "real" splash image for those producing "real" releases after the beta cycle is complete). Download NSIS and the plugins/includes that are needed by the package, and try to compile the .NSI files. Once you have all the plugins and includes, you should be able to compile both of the NSI files in that directory. (There's a single normal warning on the PortableApps.comInstaller.nsi compile.)
Once you have NSIS set up, you can proceed to try editing the NSI files, a bit at a time. Recompile and test what you did.
The Installer file is set up so you only have to change a few lines to put in e.g. the name of the package. Everything else should just compile into the paf.exe file. So really, your chore is to make the launcher .nsi file work.
MC
How do I compile it after I've done that?
As I linked to earler in this thread. Install it then right click on My File.nsi and click compile. Or you can download NSIS portable from the beta testing forum. Open the menu click Compile NSIS Script. Then drag and drop the My File.nsi into the big open spot on the new window.
Release Team Member
Yes it is a format that you must use to submit something but all you do to make a .paf is rename "MyApp.exe" to "MyApp.paf.exe".
Release Team Member
but the .paf.exe is a special type of installer. I wish John made the Installer BSD (so it's compatible commercially)
Insert original signature here with Greasemonkey Script.