Adopted a program called AppName generated the registry key HKEY_CURRENT_USER\Software\AppName. This registry key may be exported to the file appname.reg.
In the file AppnamePortable.ini I create the following 2 sections:
[Activate] Registry=true [RegistryKeys] appname=HKCU\Software\AppName
Is it necessary for me before the first start of the portable program, that I insert an empty file named appname.reg in the folder Data\settings?
Or is it sufficient to use the above described code, which then automatically creates the appropriate registry key HKEY_CURRENT_USER\Software\AppName and the file appname.reg in the folder Data\settings?
The Launcher takes care of it.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
I think it is useful for understanding the operation of the launcher, the individual steps explain in more detail. The procedure is somewhat laborious and consists of the steps described below. For the following explanations will be assumed, that the launcher uses the code, which I mentioned in my original message.
The operations will be carried out as follow:
I hope that these instructions are complete and correct. Please supplement or correct these instructions, if them contain some failures.
How is it laborious? You set the stuff in an INI and the launcher does all the work for you. You only need the .REG file to exist ahead of time in DefaultData if you need to have a set of settings different from what the app will create for itself.
Sometimes, the impossible can become possible, if you're awesome!
Of course it's clear for me, that the launcher perform all of these above described operations completely automated. The reason for the listing of these instructions is rather that in this way a background knowledge should be imparted to the often too abstract explanations to make statements in the PortableApps.com Launcher documentation more transparent.
However, me one point is still not entirely clear. In Nr. 1 of my instruction I described, that the launcher saves the empty registry key "HKCU\Software\AppName" in the folder Data\settings. Suppose that we are in a more complex situation, which is one where there is another copy of the same program "resident" on the same computer. Accordingly already exist a registry key "HKCU\Software\AppName". My question is now, if it's possible, that the launcher creates another registry key "HKCU\Software\AppName" (which doesn't have any entries) without the usage of the registry and saves this key in the file appname.reg within the folder Data\settings?
#1 is not done.
Previously known as kAlug.
What you're asking doesn't quite work. It's about as obvious as it can get. If a user runs a local copy of the app while the portable one is running, it becomes another copy of the portable one. If the local one is already running, the portable one will not run. I don't quite get why you're overcomplicating this.
Sometimes, the impossible can become possible, if you're awesome!
Due to some changes I have revised the above instructions. Of course the launcher will perform all of these below described operations completely automated. Only the described operation in No. 4 must be performed manually by the user.
The launcher use the following both sections in the file "AppnamePortable.ini":
Here now the revised instructions:
#4 should read developer/publisher. If they want a different set of default settings than the app itself creates on first run when the registry is entry, they should put it in DefaultData. Note that this is usually not necessary.
Sometimes, the impossible can become possible, if you're awesome!
Thank you for this correction to my unclear wording "user" in No. 4. I had already thought about this ambiguity itself.
I also assume, that it's necessary to store the file "appname_predefined.reg" in the folder DefaultData\settings (instead of the folder DefaultData). Then only in this case the file "appname_predefined.reg" will be pasted in the folder Data\settings. Is this assumption correct so far?
That is correct.
Sometimes, the impossible can become possible, if you're awesome!
I have now create my 3. portable app. But I need a permission of the developer, because the app is freeware but not open source. For this reason I sent him an appropriate email. Should I wait with the publication in the Beta forum until I get permission from the developer?
If you're able to setup the installer.ini to download the files, instead of including them, you can set it up as an online installer while you wait for permission.
But what should I do, if I don't get an answer to my email? Can I interpret this as a permission?
The way copyright law works is that you're not allowed to do things with other people's works without their express consent. Open source licenses give this consent. Freeware licenses generally do not (unless they specifically allow modification, repackaging, etc). To repackage and redistribute without permission is illegal. There are other portable software sites that operate illegally in this fashion. We only operate 100% legally here.
Sometimes, the impossible can become possible, if you're awesome!
In the readme.txt I found the following content:
Here is mentioned, that I can freely redistribute it. But my portable version is surely also a repackaged product and in this respect I can't find any statement to this point. Therefore I think it's the best, that I wait on this permission.