Apaf come bundled as a directory including all the software required to run it properly.
On Mac OS X, all the application bundle are already a directory, so that the end user perceive it as a desktop application and can drag-n-drop it where he need to run.
However on Windows it's a little bit more tricky, as the user expect to download a single .exe (the apaf installer), click on it and have the application ready.
Apaf should provide within it's build-system a facility to "package" the windows application as a single .exe with the apaf application icon.
When the user download it and click on it, it should automatically:
extract to the current directory with the apaf application name
startup the application inside the apaf application directory
in case the application is already extracted, directly startup the apaf application inside the apaf application directory
This would provide a valuable end-user experience reducing the amount of "clicks" required to startup an apaf application on windows.
Apaf come bundled as a directory including all the software required to run it properly.
On Mac OS X, all the application bundle are already a directory, so that the end user perceive it as a desktop application and can drag-n-drop it where he need to run.
However on Windows it's a little bit more tricky, as the user expect to download a single .exe (the apaf installer), click on it and have the application ready.
Apaf should provide within it's build-system a facility to "package" the windows application as a single .exe with the apaf application icon.
When the user download it and click on it, it should automatically:
This would provide a valuable end-user experience reducing the amount of "clicks" required to startup an apaf application on windows.