Collection of portable application launcher in PortableApps.com Format.
This is a repository to collect and manage portable software launchers we make.
Note that only the launcher will be shared in this repository in the form of source code. Hope this avoids some legal issues.
We'll set out to portablize software in every field, including open source as well as proprietary.
We are not warez. No app package will distributed in this repository.
We didn't crack a software. All authentication steps and the process of assent of EULA will be retained in the software.
This repository is not affiliated with the PortableApps.com Team.
We simply collected and organized the application launchers we wrote based on the PortableApps.com format into this repository.
We understand that we may get into some legal troubles regarding proprietary software, and if anyone's rights are offended, !!PLEASE CONTACT US!! instead of PortableApps.com.
The folders in this repository are organized in this way:
/Publisher/AppName/(Source codes of the launcher)
Every folder for the app may contain appinfo.ini, appicon.ico, launcher file (〇〇Portable.ini), Custom.nsh, or NSIS scripts (*.nsi).
Since we won't be releasing packaged portable apps, users will need to build the launcher themselves. Some of our launchers are universal launchers generated using the PortableApps.com Launcher Generator (with 〇〇Portable.ini and Custom.nsh), and some are native launchers written in the NSIS language (with 〇〇Portable.nsi or 〇〇PortableU.nsi ).
- PortableApps.com Launcher Generator (download it from here).
-
Go to the subdirectory of this repository that stores the portable application launcher files you want. Download the appinfo.ini, appicon.ico, 〇〇Portable.ini , Custom.nsh (if any). If any of the files are classified as a different version, the file of the same version is selected, if not, the previous version is selected.
-
Create a directory to place the contents of the portable app. The folder name does not affect the build process, but usually we name it "〇〇Portable" based on the AppID.
-
Create an App directory at the root of the portable app folder.
-
Open the App directory, create an AppInfo directory under the App directory.
-
Open the AppInfo directory, put appinfo.ini and appicon.ico in this directory.
-
Create a Launcher directory AppInfo directory.
-
Open the Launcher directory, put 〇〇Portable.ini and Custom.nsh (if any) in this directory.
-
Go back to the root of the portable app folder. Run PortableApps.com Launcher Generator and follow the steps to create a launcher, or simply drag the Portable Apps directory to PortableApps.comLauncherGenerator.exe to create a launcher.
You need to have the binaries of your app before you run the launcher.
Put the binaries of your app in the App directory. Makesure the relative path of your app executable matches with the value of ProgramExecutable or ProgramExecutable64 written in the launcher file ( 〇〇Portable.ini ).
Although PAL can serve as the portable launcher for most of our software, sometimes, when we deal with some software, PAL cannot meet our needs.
There are several situations where we need to write our own launcher:
- The application consists of several sub-applications and each of which needs needs to have its own launcher.
- The launcher need to deal with path with unicode character. (commonly found in software in the CJK area)
- Console application.
Here's how to compile these type of launchers.
- NSIS (download from official site, or the portable one from PortableApps.com. To create a unicode-aware launcher, use NSIS Portable Unicode).
-
Download NSI script of your portable app from our repository.
-
Create a directory to place the contents of the portable app.
-
Create a Other directory. Open the Other directory, create a Source directory.
-
Put the NSI script in Source directory.
-
Run NSIS, open the script and compile it.
In root of the portable app folder create a App directory and put the binaries of the app in the App directory.
Some launchers may depend on certain plugins (e.g. nsJSON etc.). This information is documented in the application's corresponding README file. To build such a portable launcher, place the plugins in the appropriate directory. The default plugins directory for the launcher is located in Other\Source\Plugins
There are many ways in which you can participate in this project, for example:
-
Help us to test the laucher. Sometimes, although the launcher works, there are some files or registry keys that we ignore and don't collect them back into the Data directory or delete them. Report us if there are any issues.
-
Contribute your portable app launcher.
To contribute the source code of your app launcher, you can fork the repository, push your changes into it and create an Issue.
Please add your name to the AUTHORS file to acknowledge your contribution.
Write down the change, the date, and your name (pseudonym is OK) with email to the CHANGELOG file to help us track it.
Note that our coding style and conventions are different from the PortableApps.com Team.
See the contributing guide for detailed instructions on how to join our development.
All original developers of applications are welcome to use our work to distribute portable versions of their applications.
PortableApps.com is also very welcome to add our work to your PortableApps.com Directory or Marketplace.
As a reminder, our coding style and coding conventions are different from PortableApps.com (for example, we use NSIS scripts to generate default files instead of DefaultData directory, Data directory is managed in Mac folder structure style instead of Windows style). If you care about this, You can customize it yourself. Some information in the README, NEWS and CHANGELOG may be useful to you.
MIT License (not including icon resources).