I would say this forum is still the right place for sharing one's experiences with JauntePE, so why not built up a knowledge base by posting in this thread?
Yup, i hope it would be just like that, especially for the names that redllar mentioned in "Contributions". Hope they continue their contributions in the forum.
Andrew Lee wrote:
That's really cool! For a start, I have created a new forum for sharing ready-made JPE wrappers.
I will also share a few wrappers that I have been using on a daily basis. I was thinking once a shared wrapper gets enough usage and has all the kinks ironed out, then we can promote it to the main index and get it to replace the existing NSIS/AutoIt-based ones.
BTW, is "wrapper" a good term to use for JauntePE-generated EXEs, or is there a better term for it?
Thanks Andrew, your contributions means a lot to JauntePE development. Only in TPFC i could found a lot of people who has interest in JauntePE.
The term "wrapper" is really simple and good in expressing its purpose. i start with my point of view:
NSIS/AutoIt portable launcher: They "set up" the settings of an application to fit into current host environment. The "set up" could be pass parameter, temporarily add&move registry or temporarily add&move files/folder. In order to work in limited environment, this type of launcher has to decline application that use HKLM or/and HKCR
While JauntePE works different way than NSIS/AutoIt portable launcher. This is my own view (currently collecting evidence to make a new topic): JauntePE injection "things" made the application to have its own "virtual registry" and "virtual file system". Any changes will be directed to those virtual. The "host registry" & "host file system" will not be touch at all. It is possible to portable the application that use HKLM or/and HKCR using JauntePE
The main point is, there is a HUGE different between how to portablized app using NSIS/AutoIt portable launcher and JauntePE.
"Wrapper" is already widely use to represent a portable launcher based on NSIS/AutoIt. Using "wrapper" with JauntePE could possibly lead misunderstanding to the people. Maybe we could use the same term that redllar use in Readme?
Here's the few list i could found in the Readme
* generic portable launcher (in Introduction)
* standalone portable launcher (in JPE Builder)
* portable launcher (in The Examples )
* application-specific standalone portablization packages (in License)
* JauntePE standalone launcher (in Getting Started)
* 030 launcher exe (in Getting Started)
* JauntePE-built app launcher (in FreeCell Example)
* JauntePE portable launcher (Explorer Example)
We could conclude that redllar preferrably use "launcher" instead of "wrapper". So I propose to use this term just to be uniform with the guideline.
(1) JauntePE Application Launcher
(2) JauntePE Portable Launcher
(3) JauntePE App-specific Launcher
JauntePE the portable maker: <<JauntePE Google Site