On Fri, Aug 28, 2015 at 7:24 PM, Stephan Eggermont <[email protected]> wrote: > On 28-08-15 11:00, Marcus Denker wrote: > >>> 3. For a "portable" app (e.g. on USB stick) push the app down one >>> folder, so rather than putting the Win/Lin executables inside the OSX >>> app, the top level folder contains folders Windows, Linux, Common, and >>> the app. >> >> >> No, I would retire that concept. (I know some people love it, but I think >> it does >> not fit into days world where the OS installs Apps). > > > I strongly disagree. It is very useful to be able to carry a complete > environment with me that is useable wherever I am. We will run into a lot > less problems with it once we move to 64 bit. >
Two cases benefit from a portable app: 1. In a corporate environment environment where systems are locked down preventing any software from being installed, PortableApps [1] are a lifesaver (even if in this case only portable across Windows machines). I use them *all* the time. Our IT support guys who are the only ones with permissions to install app are busy and I need tools as they arise, not in three days time. In our case, this is the difference between someone doing a taste-testing Pharo immediately when their interest is aroused, or not, because having to do forms and justify *why* they need it is too much friction, especially when the *why* is "I only want to *play* with it for a couple of hours, when I should be doing something else". It adds one small barrier [1] to adoption by a large market of potential *paying* customers. Actually PBE & UPBE describe how Pharo doesn't need to install into system areas - and I think that is beneficial to keep. An alternative could that the Pharo installer gives the option to install into either System or User area, much like Google Chrome does.. http://googlesystem.blogspot.com.au/2013/10/chromes-system-level-installer-now.html 2. I think there was a lot of value in PBE having a portable zip to download locked to match the paper document. UPBE installation instructions currently refers to http://pharo.org/download -- but that will shift over time to Pharo 5. As much as the intent would be for UPBE to track Pharo releases, the reality of limited resources is that updating might be delayed, so it would be good for the installation instructions to point to a consistent image. Alternatively, the current download page might be copied to http://pharo.org/pharo4-pbe and remain untouched when Pharo 5 is released. Then the documentation just refers to that location for download and installation instructions. [1] http://portableapps.com/ Actually we could get some additional exposure by slotting Pharo in there. I know I tend to browse these available apps to "try them" and I assume others would do the same. [2] http://www.joelonsoftware.com/articles/fog0000000052.html cheers -ben
