Portable App Development

64 bit windows XP is not compatabel with portableapps

I found Klonk's Template to be so useful in creating launchers, I decided to try my hand at it.
Mainly so I could learn NSIS more.
Version 1.1.1 fixes subsequent launch in InitApp (left it out, oops)
Version 1.1 adds registry handling and subsequent launch handling.
Registry entries are moved to {entry}_BAK in the registry rather than copied to a reg file on the portable drive, saving write cycles and write time.

Hello,

I was looking at this comment by John T. Haller, and I was wondering how close to completion the Portable Apps Format is. I'm going to be using it in Application Manager Portable when the final version is made available (apps in the repository will have to be in that format, and the installer application needs to know how to deal with it).

Thanks.

Rick Smith // Paladin225

I wonder if this is something that would have any bearing on what goes on here. They can't go after or muck with individuals with singular programs, for the most part, but those that make things easier or condsolidated, like a 'suite' could be hassled.

Hi,

I'm working on developing a laucnher for Adobe Photoshop CS2, suing Klonk's awesome PAT. I've taken care of the CS2 reg keys no problem, but I can't figure out how to catch a .dat file stored in a folder in the Documents and Settings/All Users/. Can anyone shed some light on this please?

Thanks in advance.

What is it for ?
The purpose of this discussion is to define guidelines for using JRE/GTK within the Portable Application Template as definied by Karl Loncarek here.

History
The original discussion starts here and here.

What are the first available guidelines ?

Directory structure

What is it used for? It doesn't seem to affect anything in the PortableApps menu, nor is it read from in the PAM source. It must serve a purpose though?

Hi all,

Is there a plugin for NSIS that lets it log into a remote FTP server and download/upload stuff? I think I have an idea...

Rick Smith // Paladin225

ASuite has an option to run apps when it starts. I'm hoping PAM will eventually have this option as well, so this suggestion is for both.
The option to run an app when the menu starts should also have a prompt option.
i.e. App xyz is set to autolaunch, would you like to launch it. Yes | NO

The PortableApps launchers already get the process id in order to monitor for the process close to do cleanup. The launchers also already support getting and passing arguments.
I would like to suggest that the launchers support a /exit argument which if received would use the same close process command that windows uses when shutting down.
This would allow menu apps like PAM/PStart/ASuite to close the applications when the menu is closed. Assuming the functionality will be added to PAM eventually.