June 2009 - Pharo-dev - lists.pharo.org

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

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

by Oscar Nierstrasz

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

June 10, 2009

Re: [Pharo-project] New Extensible Inspector for Pharo-Core

by StÃ©phane Ducasse

yeap! seems the same for me but I did not try your new version On Jun 10, 2009, at 12:17 PM, Antoine Marot wrote: > I would like to have a collection of the children to see them quickly. > > I think unfolding is only interesting to inspect a particular > children. When I click on Methods or Implementors, I expect to see > them rather than the object from which they are derived. > > > Le 10-juin-09 Ã 12:09, Frederic Pluquet a Ã©crit : > >> Yes because I wanted that :-) What do you propose to describe ? >> Always the children ? >> >> FrÃ©d >> ---- >> FrÃ©dÃ©ric Pluquet >> UniversitÃ© Libre de Bruxelles (ULB) >> Assistant >> http://www.ulb.ac.be/di/fpluquet >> >> >> 2009/6/10 Antoine Marot <amarot(a)ulb.ac.be> >> It happens as well for Implementors, Elements, ... >> >> >> Le 10-juin-09 Ã 11:59, Antoine Marot a Ã©crit : >> >>> When I click on "Methods", the item displayed on the right is not >>> the method dictionary but the parent object. >>> >>> Could you check that ? >>> >>> >>> Antoine >>> >>> Le 10-juin-09 Ã 10:49, Frederic Pluquet a Ã©crit : >>> >>>> I commited a new version of NewInspector, with new feartures : >>>> >>>> - add progress bar indicator when long collections are inspected >>>> (no freeze feeling) >>>> - limit the description string of collections to 5000 >>>> characters(speed) >>>> - add inst vars as direct children of an object (accessibility >>>> and speed) >>>> - children of first inspected object opened by default >>>> (accessibility and speed) >>>> >>>> Thanks for your feedback ! >>>> >>>> FrÃ©d >>>> ---- >>>> FrÃ©dÃ©ric Pluquet >>>> UniversitÃ© Libre de Bruxelles (ULB) >>>> Assistant >>>> http://www.ulb.ac.be/di/fpluquet >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> >> _______________________________________________ >> 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 > > _______________________________________________ > 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] New Extensible Inspector for Pharo-Core

by Antoine Marot

I would like to have a collection of the children to see them quickly. I think unfolding is only interesting to inspect a particular children. When I click on Methods or Implementors, I expect to see them rather than the object from which they are derived. Le 10-juin-09 Ã 12:09, Frederic Pluquet a Ã©crit : > Yes because I wanted that :-) What do you propose to describe ? > Always the children ? > > FrÃ©d > ---- > FrÃ©dÃ©ric Pluquet > UniversitÃ© Libre de Bruxelles (ULB) > Assistant > http://www.ulb.ac.be/di/fpluquet > > > 2009/6/10 Antoine Marot <amarot(a)ulb.ac.be> > It happens as well for Implementors, Elements, ... > > > Le 10-juin-09 Ã 11:59, Antoine Marot a Ã©crit : > >> When I click on "Methods", the item displayed on the right is not >> the method dictionary but the parent object. >> >> Could you check that ? >> >> >> Antoine >> >> Le 10-juin-09 Ã 10:49, Frederic Pluquet a Ã©crit : >> >>> I commited a new version of NewInspector, with new feartures : >>> >>> - add progress bar indicator when long collections are inspected >>> (no freeze feeling) >>> - limit the description string of collections to 5000 >>> characters(speed) >>> - add inst vars as direct children of an object (accessibility and >>> speed) >>> - children of first inspected object opened by default >>> (accessibility and speed) >>> >>> Thanks for your feedback ! >>> >>> FrÃ©d >>> ---- >>> FrÃ©dÃ©ric Pluquet >>> UniversitÃ© Libre de Bruxelles (ULB) >>> Assistant >>> http://www.ulb.ac.be/di/fpluquet >>> >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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] New Extensible Inspector for Pharo-Core

by Frederic Pluquet

Yes because I wanted that :-) What do you propose to describe ? Always the children ? FrÃ©d ---- FrÃ©dÃ©ric Pluquet UniversitÃ© Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet 2009/6/10 Antoine Marot <amarot(a)ulb.ac.be> > It happens as well for Implementors, Elements, ... > > Le 10-juin-09 Ã 11:59, Antoine Marot a Ã©crit : > > When I click on "Methods", the item displayed on the right is not the > method dictionary but the parent object. > Could you check that ? > > > Antoine > > Le 10-juin-09 Ã 10:49, Frederic Pluquet a Ã©crit : > > I commited a new version of NewInspector, with new feartures : > - add progress bar indicator when long collections are inspected (no freeze > feeling) > - limit the description string of collections to 5000 characters(speed) > - add inst vars as direct children of an object (accessibility and speed) > - children of first inspected object opened by default (accessibility and > speed) > > Thanks for your feedback ! > > FrÃ©d > ---- > FrÃ©dÃ©ric Pluquet > UniversitÃ© Libre de Bruxelles (ULB) > Assistant > http://www.ulb.ac.be/di/fpluquet > > > _______________________________________________ > 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 > > > > _______________________________________________ > 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