Hi John,
I had a quick look at the PortableApps Menu source this weekend.
As I have many applications that need to be stored in folders outside the PA structure I am currently thinking about
a) writing a tool for creating launchers automatically or
b) enhancing your Menu to support Windows lnk files.
I think this would be a great enhancement for users like me who are trying to keep the structure of your PA applications and have their own apps on the same drive but in a different folder, e.g. PortableTools ;). It's easier to update and maintain. Some apps also have fixed paths. The benefit comes from integrating those "external" apps into the menu.
I've already found a closed source tool for a) in the forum but it lacks proper support of different working folders and application icons have to be integrated manually using e.g. ResHacker.
Regarding a) I could implement a small tool taking the needed informations (name, workpath, icon and so on, with drop-and-drag support) to create exe files and drop them into an appropriate folders inside the PA structure.
b) would also be possible by using something like the informations returned from a CLSID_ShellLink instance. As you know the problem with ShellLinks is that they tend to rely on fixed drive letters which might create problems if the portable device is attached to a different one.
The overall quality of your code is pretty good but I would suggest trying to keep it more in a Delphi way, regarding the naming conventions and indenting. There are also several issues when porting it to D2009 (but due to the missing Win9x support this might not be relevant now) due to the old expectation of Char = 1 Byte.
Your turn, send me your comments about.
Cheers,
Arvid
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
a)Automatic = very difficult to make universal
b).lnk files wouldn't work when the drive letter changes and don't support relative paths
However, I have done something very similar to this by creating a launcher that reads from an INI file a relative path, then gets the drive letter, puts the two together and launches the program. Then all you have to change is the INI file for it to work for any program anywhere on your drive. The app icon is another matter that would require reshacker to get the icon file out of the original app, then probably recompiling the launcher, at which point perhaps rather than putting the shortcut in an INI you could put it in a define in your launcher then just recompile for every app you want done in this way... or not...
Quamquam omniam nescio, nec nihil scio.