I would like to customize the installer. During the installation of the app should be displayed a custom page to the user. This custom installer page should contain a special titel and an information for the user. Can someone offer me instructions or the code, so that I am able to realize that feature?
New: Supermium (Apr 11, 2024), Platform 29.4 (Apr 10, 2024)
1,000+ portable packages, 1.1 billion downloads
Please donate today
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
This is not permitted with the PortableApps.com Installer. You can only use the standard pages. Anything displayed to the user in terms of information should be on the license page. This is to allow all installers to be automated with the app store and updater.
Sometimes, the impossible can become possible, if you're awesome!
So far in the license page only the EULA.txt file is displayed. How can I add another message box to the license page?
Hi tapsklaps,
you can use an EULA.rtf instead. If that fits the developers requirements you could add the message on top of the Eula in big red letters this way.
It could look something like this.
The other option could be the splashscreen once an app gets official.
Wo both have the same idea
We're going to be doing away with RTF in the near future.
Sometimes, the impossible can become possible, if you're awesome!
Oh, that's a pity. But rtf is a slightly ancient format anyway.
Is there any other solution for the problem in question?
In this case (PicPick) the original app's developer granted permission for the portable app provided that the message "FOR HOME USER (PERSONAL USE ONLY)" is shown prior install in a prominent way. The EULA is only a workaround for this.
I first thought of some custom code for the installer (hence the opening question of tapsklaps i think) but already saw the problem of automatic and silent installation. I included a simple detection of license.ini but was aware that that was not enough when I had a look at the installer source. Thought of something like in function PreLicense but decided to drop it because it would make things to complicated and prone to errors (especially as I don't know what is planned for mass installing and license agreements - you once mentioned that this could be rearranged sometimes)
Meanwhile I once again contacted the developers of PicPick regarding that topic. They also recommend me, that the information "FOR HOME USER (PERSONAL USE ONLY)"should be displayed in an additional message box during the installation. Personally I believe, that it not makes much difference whether this information appears in a separate dialog box or is included in the file EULA.txt. So I'll just leave it now finally with the variant with the customized file EULA.txt. We should make it no more complicated than actually required
I think having the RTF option is valuable; many EULAs can be made significantly more readable with just a bit of bold text or such things, which can't be done with TXT. Many pieces of software use rich formatting on the web and in their own installers, and I can't think of any good reason why we would actively remove support for it. I can't see any reason for removing it—if we were wanting to take it down to one type, I'd be for removing the TXT version instead (so highly do I value the formatting).
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
The EULAs will shortly need to be easily machine readable to be able to offer things up at the start of an install/update of multiple apps. This is very difficult with the oddball RTF format. We only have a couple apps that use it anyway. It's bigger than text and more of a hassle. As it is, we have to edit it with WordPad to tweak it for inclusion since neither Microsoft Word nor LibreOffice handle RTF entirely well.
Sometimes, the impossible can become possible, if you're awesome!
I have thought about the possibilty, that I simply expand the content of the file EULA.txt. I paste the necessary information at the beginning of the file EULA.txt. Would that be appropriate?