- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: First try of Pharo

by StÃ©phane Ducasse

Begin forwarded message: > From: andres(a)lifia.info.unlp.edu.ar > Date: June 10, 2009 2:06:20 PM CEDT > To: stephane.ducasse(a)inria.fr > Subject: First try of Pharo > > Hi Stef, > after wanting to try pharo for a while I finally manage to get some > time to do it. I hope is ok to send you this mail, I really don't > want to suscribe to another mailing list :P. > Ok, so I downloaded pharo0.1-10324web09.06.1 and the win vm (I > generally run on a linux box but today I happen to be on a win xp 32- > bit one -HP 530 notebook, 2GB ram 1.6 processor-). After extracting > the files and associating .image with Squeak.exe I tried a first > run. Starting the image would give the error attached in the > screenshot. I tried moving the image to be in the same folder as the > VM with no luck. > The second I thing I noticed is that the image is extremly slow; > open up a bowser takes about 6 seconds, a workspace around 3. > Evaluating 2+2 in the workspace takes about 2 seconds, although > doing a Time millisecondsToRun: [2+2] yields 0 (yet that expression > also takes about 2 seconds). Browsing classes is yet a harder task > since each change in the browser (package, class, category, etc) > takes between 2 and 5 seconds. > If there is anything I can do to give you more information just let > me know. > > HTH, > AndrÃ©s > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. >

June 10, 2009

Re: [Pharo-project] ScriptLoader policies

by Mariano Martinez Peck

On Wed, Jun 10, 2009 at 6:53 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > On Wed, Jun 10, 2009 at 9:53 AM, Damien Cassou<damien.cassou(a)gmail.com> > wrote: > > What about using Installer which is present in all Pharo. For example: > > > > instClass ss > > project: 'OCompletion'; > > install: 'OCLoader'. > > instClass being Installer, sorry. Yes yes. I do this: "GlorpPharoLoader loadGlorp". But loadGlorp, inside, uses installer as you said :) Thanks! Mariano > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2009

[Pharo-project] mapping of initials to committers?

by Oscar Nierstrasz

Is there a list somewhere mapping initials to full names of people who have committed code to Pharo? http://code.google.com/p/pharo/wiki/ListOfOkCommitters This list does not include initials. - on

June 10, 2009

[Pharo-project] [FIX] Issue 871: FreeType is sensible to new image locations

by Damien Cassou

Please apply this patch from Andrew Tween: http://code.google.com/p/pharo/issues/detail?id=871 Without it, I can't build good looking Pharo images anymore. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 10, 2009

Re: [Pharo-project] a plea for "save and quit"

by Oscar Nierstrasz

Nope. If I uncomment it, it works exactly as I want, which is to save and quit without any further prompting. - on On Jun 10, 2009, at 13:46, Henrik Johansen wrote: > IIRC, you get the option to save whenever you try to quit. > So save and quit didn't really make sense, as it'd save, then ask > you if > you wanted to save again before actually quitting... > > Cheers, > Henry > > Oscar Nierstrasz skrev: >> Hi Folks, >> >> Is there any reason why "save and quit" is commented out of the world >> menu? It is what I want to do 90% of the time. >> >> Would be nice to have it back by default. >> >> - on >> >> TheWorldMenu>>buildWorldMenu >> "Build the menu that is put up when the screen-desktop is clicked >> on" >> | menu | >> ... >> self fillIn: menu from: { >> nil. >> ... >> "{'save and quit'. {self. #saveAndQuit}. 'save the current image on >> disk, and quit out of Squeak.'}." >> {'quit'. {self. #quitSession}. 'quit out of Squeak.'} >> }. >> ^ menu >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 10, 2009

Re: [Pharo-project] a plea for "save and quit"

by StÃ©phane Ducasse

this is why it was removed. in fact there is no quit On Jun 10, 2009, at 1:46 PM, Henrik Johansen wrote: > IIRC, you get the option to save whenever you try to quit. > So save and quit didn't really make sense, as it'd save, then ask > you if > you wanted to save again before actually quitting... > > Cheers, > Henry > > Oscar Nierstrasz skrev: >> Hi Folks, >> >> Is there any reason why "save and quit" is commented out of the world >> menu? It is what I want to do 90% of the time. >> >> Would be nice to have it back by default. >> >> - on >> >> TheWorldMenu>>buildWorldMenu >> "Build the menu that is put up when the screen-desktop is clicked >> on" >> | menu | >> ... >> self fillIn: menu from: { >> nil. >> ... >> "{'save and quit'. {self. #saveAndQuit}. 'save the current image on >> disk, and quit out of Squeak.'}." >> {'quit'. {self. #quitSession}. 'quit out of Squeak.'} >> }. >> ^ menu >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2009

Re: [Pharo-project] a plea for "save and quit"

by Henrik Johansen

IIRC, you get the option to save whenever you try to quit. So save and quit didn't really make sense, as it'd save, then ask you if you wanted to save again before actually quitting... Cheers, Henry Oscar Nierstrasz skrev: > Hi Folks, > > Is there any reason why "save and quit" is commented out of the world > menu? It is what I want to do 90% of the time. > > Would be nice to have it back by default. > > - on > > TheWorldMenu>>buildWorldMenu > "Build the menu that is put up when the screen-desktop is clicked on" > | menu | > ... > self fillIn: menu from: { > nil. > ... > "{'save and quit'. {self. #saveAndQuit}. 'save the current image on > disk, and quit out of Squeak.'}." > {'quit'. {self. #quitSession}. 'quit out of Squeak.'} > }. > ^ menu > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > >

June 10, 2009

[Pharo-project] Pharo platform dependency (or Seaside one click)

by Torsten Bergmann

Stephane wrote: >Now do you have a fix? 1) Tried to reproduce it without success. My fault, looks like I stopped in the middle of the startup process since the font update took to long and the startup logic in Clipboard (who resets the class variable) is processed after that. So it was still pointing to the mac clipboard in this case - so it's not a problem of the one click image or Pharo by default. But it would be good if the Clipboard startup is processed much earlier (before such annoying "long runners"). The font update at image startup is now disabled by default in newer Pharo images but can be enabled again. So I've added the Clipboard to the end of the first processed startup elements so it gets called earlier. The change is in "System-Support-torsten_bergmann.33.mcz" (based on 32) one has to call "SystemDictionary initialize" after that. 2) Regarding the Mac host windows menu. First question is if it should really be part of the standard image or a loadable package for Mac? Whats the status of the windows port, if any? However - the test is currently red on Windows: a) Yes - there is code in each test method to return if not on mac, but it will already crash in #setUp on a non Mac platform like Windows b) If this check is also added to #setUp to return early it will still be red since a few more test methods like #testMenuHandles are not guarded c) testCharacterChanging sends the unknown method #calculateShouldBeFrom:using: Maybe we should move HostSystemMenusTest>>isMacintosh to the class side and implement HostSystemMenusTest class>>isAbstract like this: isAbstract ^self isMacintosh not This makes the unit test an abstract one on non-mac platforms (and therefore green ;), we can remove all the checks in the test methods and someone with a mac (John?) could fix the test code on the intended platform... Bye Torsten -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

June 10, 2009

Re: [Pharo-project] a plea for "save and quit"

by Michael Rueger

Oscar Nierstrasz wrote: > Hi Folks, > > Is there any reason why "save and quit" is commented out of the world > menu? It is what I want to do 90% of the time. > > Would be nice to have it back by default. +10

June 10, 2009

Re: [Pharo-project] Pharo platform dependency (or Seaside one click)

by Michael Rueger

Torsten Bergmann wrote: > Trying to copy a text from the new Seaside one click > image 2.8.4 using Pharo 10318 will bring up the debugger > on Windows since the default clipboard is pointing to an > instance of MacOSClipboard. The new Pharo core doesn't have that problem, works fine out of the box. Could it be a problem with Seaside (or changes coming in with Seaside) interfering with the startup initialization of OSPlatform/Clipboard? Michael

June 10, 2009