Hi,
is there smoewhere a simple example of a source for programlauncher. I looked at e.g. PortableOpenoffice and I'm quite confused.
As I haven't done anything really complicated with NSIS yet, I need something really simple.
Or at least a very good commented source: What is done and why?
A starting point would be what to do when a application writes to e.g. the profile directory. How to avoid that assuming that the software has no commandline option for that.
Reason: I have several applications here (mainly commercial) that I want to make portable (for my own use). Of course I then would share my results.
But first there is the hard way of learning it..
Can anyone help me?
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
Read the manual. Or use the template or UniLaunch.
----
R McCue
"If you're not part of the solution, you're part of the precipitate."
I know I'd have to read the manual of NSIS (right?) but there I'll only see how to install applications.
I'll take a look at the template. Hope this helps me understadn what is done...
It's not all about installing.
My code for UniLaunch is simple but if all you want to do is port apps, use the template or UniLaunch. Either will do.
----
R McCue
"If you're not part of the solution, you're part of the precipitate."
There are a number of different methods of making applications work as portable applications, it just so happens the common choice around here is NSIS. This is because it provides a standard compiler and comes with a number of different features and plugins to link up with the opporating system. What I'm trying to get at is that you don't have to use NSIS.
As for how NSIS is used to make applications portable, all source code is provided with the applications. All you have to do is take a look at it and go through it line by line with the NSIS manual and online resources. Although NSIS is a horrible scripting/programming language, it provides a great means of making applications portable as it has all the tools needed to do so.
First you have to find out where all data for the application is saved (in documents folder, in the registry, on the C drive, etc). After that, you should try to find out what functionality the application itself gives to get around it's saving the data where it does (command-line parameters, INI settings, etc). This is where the NSIS comes in, you have to wrap up the data so that the application is tricked to save it locally in the application path. You can do this in a number of different ways and it completely depends on the application. Take a look at some of the other portable applications on the site, and I'm sure you'll figure out how it's generally done. Good luck!
Rob Loach [Website] [Projects]
Thanks a lot, this was helpful. I think I really have to go through it step by step...
Just fro others, that might be interested. Make sure you have a clean machine and then use e.g. Total Uninstall to track what was changed during installation or during work with the software.