Damien Cassou wrote:
Hi,
I've just made an executable file for installing Pharo on Windows (in
program files, with a shortcut in the Start menu...). Please try
it and report problems:
https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Win-Package/lastSuccessfulBuild/artifact/pharo-ci/pharo_installer.exe
Thats great Damien. I installed and ran it without a hitch. I installed
as a "Standard User" "Ben" which UAC then asked for to upgrade
credentials to my admin account "BenAdmin" to perform the install.
It picked up my existing images using Pharo. I updated the templates,
created and launched a new image. It even kept my the template list
between restarts of Pharo Launcher with the preference "Templates
cleared at startup" disabled - which is very cool.
Now from the Start menu > All Programs > Pharo folder
I felt a bit awkward clicking on Pharo when I knew it was actually
PharoLauncher. I think it would be good to keep the distinction between
Pharo the programming environment and PharoLauncher the application.
People should not be developing their own applications inside Pharo
Launcher, but should be developing inside Pharo images started from
Pharo Launcher.
The folder and file security settings look good and tight - for the
image and changes files the Users group has Read & Execute only with no
Write permissions. However I'm mildly concerned that changes in the
image (such as setting the debug flag and opening tools) persist - and
also mildly annoyed with myself that I can't work out how its happening.
Attila Magyar wrote:
Tried it and worked fine on Windows 7. Though, I had few issues with the
launcher.
When I right click on an empty area of the Existing Images panel (and there
is no image selected or the pane is empty), I got a MessageNotUnderstood:
receiver of buildWithSpec is nil.
A fix is to change TreeModel>>menu:shifted:
from...
(self allowMenuOnNoItem not and: [ self selectedItems isEmpty ])
ifTrue: [ ^ nil ].
to...
(self allowMenuOnNoItem not and: [ self selectedItems isEmpty ])
ifTrue: [ ^ MenuModel new ].
but I am not sure of the wider implications, or if a bug should be
logged for Launcher or Spec.
gotta run now, so other people can sleep.
cheers -ben
After I renamed an image, I got a DirectoryDoesNotExist with a path pointing
to the old directory. But I can't reproduce it anymore.
