On Wed, Apr 1, 2015 at 12:34 AM, Damien Cassou <damien.cassou@gmail.com> wrote:

Cyril Ferlicot <cyril.ferlicot@gmail.com> writes:

> On 31 March 2015 at 17:22, Damien Cassou <damien.cassou@gmail.com> wrote:
>
>> Ben Coman <btc@openinworld.com> writes:
>>
>> > Regarding Windows... Last that I looked, the PharoLauncher image is
>> > installed into the "Program Files" System Folder.�� This causes a problem
>> > since when a PharoLauncher Image is saved by a Standard User, they cannot
>> > write to the System Folder so Windows *fakes* it and actually writes to a
>> > User Fodler, but makes it look like the file is in the System Folder.
>> That
>> > is, the Standard User is looking at a Fake System Folder!!
>>
>> that's very strange. Can someone please evaluate this expression on your
>> Windows box and give us the result?
>>
>>�� PlatformResolver forCurrentPlatform cache

> File @ C:\Users\Cyril\AddData\Roaming

looks good to me. So, I don't understand Ben's problem.

>> > This confused me for quite a while - even as an IT Administrator of 15
>> > years.�� Its likely to cause chaos and pain for others down the track. So
>> I
>> > recommend that the installer be changed so that the PharoLauncher Image
>> is
>> > installed into a User Folder - at least by default, and maybe as the only
>> > option.
>>
>>
>> I disagree. The launcher should be installed with other applications.
>> But the data is per-user. On Ubuntu, the launcher is happily installed
>> under /usr/share/pharo-launcher and images are download to
>> ~/.cache/Pharo/images.

The location of the downloaded images is fine.�� It is the location of PharoLauncher's own image that is the problem on windows if the user happens to save the Image.�� Try the following on Windows 7+...

1. Install pharo_installer-0.x.x.exe as administrator.

2. Run Pharolauncher as a standard user.

3. Change to development mode, open Playground and type a note to yourself like "This should not show after a reinstall".�� Quit Pharolauncher and restart to check it still appears, and quit again.

4. Re-install pharo_installer-0.x.x.exe as administrator (like you might when a newer version is available)

5. Run Pharolauncher as a standard user.
You would expect a fresh image - one that doesn't show the note to yourself, ��but I had found (a while ago) that the note still shows, indicating the upgrade effectively failed. ��

That is a "typical" workflow in a corporate environment, which I expect Pharo would like to target.��

So when you:��

�� * run PharoLauncher as administrator and get the new Pharolauncher, but

�� * run PharoLauncher as a standard user and get the old Pharolauncher

you may rightfully ask wtf ?!?�� What do you observe?��

cheers -ben

>>
>> > I had meant to fix this in PharoLauncher myself, and also would offer to
>> > test it - but unfortunately I currently don't have access to a Windows
>> > machine.
>>
>> I hope someone else will try
>>
>> --
>> Damien Cassou
>> http://damiencassou.seasidehosting.st
>>
>> "Success is the ability to go from one failure to another without
>> losing enthusiasm." --Winston Churchill
>>
>>

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill