> > « Program » folder is the default location where to install apps on > Windows. > If a user does not have admin rights, he can simply install it under its > home directory. > > Also there is the UAC Virtualization fiasco that complicates installing > upgrades. > http://lists.pharo.org/pipermail/pharo-dev_lists. > pharo.org/2014-January/091645.html > > > > Could we *please* install Windows PharoLauncher into user folders? > > > > Users can choose to install Pharo Launcher where they wish. > We could choose another default location but not sure it is best option. >
Nope, I don’t have any option of changing Pharo launcher installation. I double click the exe and receive a message telling me I need administrative rights. Can this be changed? It’s a deal breaker for those using Windows. On Mon, Oct 9, 2017 at 10:56 AM, Peter Uhnák <i.uh...@gmail.com> wrote: > why a step backwards? >> Pharo images are not *data* in the sense is intended for XDG_DATA_HOME. >> In practice, an image is more like a document Pharo can read… data files >> are configurations, etc. an app needs to work properly in the local >> environment. >> Pharo images instead, are modifiable/editable/whatever euphemism you want >> … that’s why we considered more like VMWare considers their Virtual >> Machines, then they belong to some place in the home directory that is of >> easy access. >> > > I guess I hate when applications are throwing their garbage into my $HOME > (this also goes for VirtualBox, Eclipse, and everyone else). > If I am not accessing the files directly, but they are pretty much always > managed by some other applications, then for me they are polluting $HOME. > (And yes, I sometimes do launch to image by hand, or manipulate VirtualBox > by hand, but that doesn't change the fact that it is not the primary way to > work with it.) > > But no worries, I rest my case and I patch it for myself. (So no need to > add configuration for this either.) > > Peter >
