May 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.1] #11351

by StÃ©phane Ducasse

11351 ----- - HashedCollection: postCopy back for Set before removing it from hashedCollection

May 11, 2010

Re: [Pharo-project] Migrating among different Pharo releases

by Henrik Johansen

On May 11, 2010, at 1:41 53PM, StÃ©phane Ducasse wrote: > http://book.pharo-project.org/book/TipsAndTricks/FixingUnderscores/ Disclaimer: I haven't used it personally, but the code found in .cs in the thread at: http://forum.world.st/Can-i-has-underscores-td1839755i20.html might also be a worthy addition to that page.(Compared to FixUnderscores, it can be used to fix at fileIn-time, rather than on packages already in image) Looking shortly at the code, it might look like you're in for nasty surprises if trying using it to read anything but BOM-marked utf8 or MacRoman files though :) Cheers, Henry

May 11, 2010

Re: [Pharo-project] Fwd: Re: DEVImageCreator >> setDefaultPreferences (alain?)

by Mariano Martinez Peck

http://code.google.com/p/pharo/issues/detail?id=2410 http://code.google.com/p/pharo/issues/detail?id=2014 On Tue, May 11, 2010 at 2:21 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > > >> > >> Do you know when Preferences class will be completely removed? Pharo > 1.2? > > I don't know. Maybe we can let it in the 1.1 in order > > to let maintainers the possibility to port their packages and > > definitively remove it in 1.2. > > The same for TheWorldMenu I guess. > yes this is the idea. > > Stef > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 11, 2010

Re: [Pharo-project] DEVImageCreator >> setDefaultPreferences (alain?)

by Alain Plantec

Le 11/05/2010 15:22, Alain Plantec a Ã©crit : > Le 11/05/2010 14:13, Mariano Martinez Peck a Ã©crit : >> >> >> >> >> But maybe the default value in the "PharoCore" is not the same as >> PharoDev? I mean, suppose these are the default prefrences we used >> in the pharo dev image > ok, there is only one default. > For this need, you should have to create a setting style for pharodev > and load it. I've re-thougth about this and maybe building a style class and let it in the dev image is a bad solution because then, the style class depends on all other packages. This is exactly what we wanted to avoid by introducing the settings. So, maybe the default state for the preferences in the dev should be the one of the core plus the state decided by maintainers for additional packages. Alain

May 11, 2010

Re: [Pharo-project] DEVImageCreator >> setDefaultPreferences (alain?)

by Alain Plantec

Le 11/05/2010 14:13, Mariano Martinez Peck a Ã©crit : > > > On Tue, May 11, 2010 at 1:55 PM, Alain Plantec <alain.plantec(a)free.fr > <mailto:alain.plantec@free.fr>> wrote: > > Hi Mariano, all > Le 11/05/2010 11:43, Mariano Martinez Peck a Ã©crit : > > Hi Alain. DEVImageCreator has to be updated to use the new > preferences. I can do it but it will require much more than > for me than for you ;) > > For preferences it is DEVImageCreator >> setDefaultPreferences > it is using Preferences class for the moment. It should be > updated to use Settings, isn't it ? > > I don't think so. There is no need for such a initialization > anymore since package are defining their own preferences. > If a default value is desired then it should be set by an > initialization method or lazily by the getter. > I find the lazy initialization better because then, the > SettingBrowser can reset the preference to the default by setting > it to nil. > > > But maybe the default value in the "PharoCore" is not the same as > PharoDev? I mean, suppose these are the default prefrences we used in > the pharo dev image ok, there is only one default. For this need, you should have to create a setting style for pharodev and load it. as an example: PharoDevSettingStyle class >>styleName "notice the pragma which allow the setting browser to recognize the class as a style" <settingstyle> ^ 'PharoDev' PharoDevSettingStyle>>load "set your default 1.1 preferences here" CodeHolder showAnnotationPane: false. UITheme currentSettings fastDragging: true. SystemWindow fullScreenMargin: 25. MorphicModel keyboardFocusOnMouseDown: true. UITheme currentAnimationSettings useAnimation: false. "etc ... " PharoDevSettingStyle>>loadStyle self load Then, in order to load the style, evaluate PharoDevSettingStyle new load. Or, if you don't want to search for where are the preferences and how to set them, simply, open a SettingBrowser then set the settings then create a Style named 'PharoDev'. The PharoDevSettingStyle class will be created for you. > > If we used to do this, I guess it was becuase most of the default > preferences of the core image was different. Otherwise, this method > doesn't have sense. of course yes :) Alain >

May 11, 2010

Re: [Pharo-project] [Vm-dev] [ANN] DTrace for Squeak/Pharo

by Mariano Martinez Peck

Hi Adrian, this sounds AMAZING. I am reading the post and trying to make it work, but have a problem trying to lunch start.command I have Mac OS 10.5.8 /Users/mariano/Pharo/VM/pharo-dtrace/start.command ; exit; SQUEAK_ENCODING=UTF-8 SQUEAK_PATHENC=UTF-8 SQUEAK_PLUGINS=/Users/mariano/Pharo/VM/pharo-dtrace/VM/%n + exec /Users/mariano/Pharo/VM/pharo-dtrace/VM/squeakvm PharoCore-1.0.image dyld: unknown required load command 0x80000022 /Users/mariano/Pharo/VM/pharo-dtrace/start.command: line 4: 8676 Trace/BPT trap ./VM/squeak PharoCore-1.0.image logout [Process completed] any hints? Thanks! Mariano On Tue, May 11, 2010 at 9:13 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > Now there's also a DTrace provider for the Squeak VM: > > http://www.adrian-lienhard.ch/blog?dialog=smalltak-meets-dtrace > > DTrace is a powerful, kernel-based dynamic tracing framework. With the new > provider one can analyze the execution of Pharo/Squeak applications. > > My post is an introduction that should get you quickly started. I've > attached a pre-compiled VM for OS X. > > Hope you like it :) > > Cheers, > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > >

May 11, 2010

Re: [Pharo-project] Fwd: Re: DEVImageCreator >> setDefaultPreferences (alain?)

by StÃ©phane Ducasse

> >> >> Do you know when Preferences class will be completely removed? Pharo 1.2? > I don't know. Maybe we can let it in the 1.1 in order > to let maintainers the possibility to port their packages and > definitively remove it in 1.2. > The same for TheWorldMenu I guess. yes this is the idea. Stef

May 11, 2010

Re: [Pharo-project] DEVImageCreator >> setDefaultPreferences (alain?)

by Mariano Martinez Peck

On Tue, May 11, 2010 at 1:55 PM, Alain Plantec <alain.plantec(a)free.fr>wrote: > Hi Mariano, all > Le 11/05/2010 11:43, Mariano Martinez Peck a Ã©crit : > > Hi Alain. DEVImageCreator has to be updated to use the new preferences. I >> can do it but it will require much more than for me than for you ;) >> >> For preferences it is DEVImageCreator >> setDefaultPreferences >> it is using Preferences class for the moment. It should be updated to use >> Settings, isn't it ? >> > I don't think so. There is no need for such a initialization anymore since > package are defining their own preferences. > If a default value is desired then it should be set by an initialization > method or lazily by the getter. > I find the lazy initialization better because then, the SettingBrowser can > reset the preference to the default by setting it to nil. > > But maybe the default value in the "PharoCore" is not the same as PharoDev? I mean, suppose these are the default prefrences we used in the pharo dev images: setDefaultPreferences. Preferences disable: #annotationPanes; disable: #allwaysShowVScrollBar; enable: #alternativeButtonsInScrollBars; disable: #fadedBackgroundWindows; enable: #fastDragWindowForMorphic; disable: #fullScreenLeavesDeskMargins; enable: #generalizedYellowButtonMenu; enable: #mouseClickForKeyboardFocus; enable: #noWindowAnimationForClosing; disable: #scrollBarsNarrow; disable: #scrollBarsWithoutMenuButton; disable: #showSplitterHandles; disable: #syntaxHighlightingAsYouTypeAnsiAssignment; enable: #showTextEditingState; disable: #windowAnimation; setPreference: #GlyphContrast toValue: 55; disable: #roundedWindowCorners; disable: #roundedMenuCorners; enable: #infiniteUndo; enable: #useUndo; enable: #mercuryPanel; disable: #showUpdateOptionInWorldMenu. If we used to do this, I guess it was becuase most of the default preferences of the core image was different. Otherwise, this method doesn't have sense. If I now do what you say, I am changing the default value of the pharo core image also. Is this correct ? or this should be only one flavor (PharoDev) ? Anyway, suppose I want to do the same as above, I should do something like: Preferences infiniteUndoSetting: true; etc.... Similar happens with external packages. Suppose OB developers (Lukas?) doesn't want to have mercury bar enable by default, but us (in PharoDev) we DO want it. Then I need to set such preference. Maybe the name default looks bad for you. It should be "preferences for PharoDev image" > BTW, Preferences is still present in Pharo 1.1 and thus, >> setDefaultPreferences is still working but I guess it should be updated. >> > why ? there is no need for setDefaultPreferences anymore. > > >> Do you know when Preferences class will be completely removed? Pharo 1.2? >> > I don't know. Maybe we can let it in the 1.1 in order > to let maintainers the possibility to port their packages and > definitively remove it in 1.2. > I agree, 1.2. > The same for TheWorldMenu I guess. > ok Cheers Mariano > Cheers > Alain > > >> Thanks! >> >> Mariano >> > >

May 11, 2010

Re: [Pharo-project] [Vm-dev] Re: Freetype plugin archive

by Mariano Martinez Peck

On Tue, May 11, 2010 at 10:57 AM, laurent laffont <laurent.laffont(a)gmail.com > wrote: > > > On Tue, May 11, 2010 at 9:56 AM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> >> >> >>> >>> I think you're right. I will add this description. >>> >>> Indeed, with easy_squeakvm script you have reproducibility (all is >>> automated, explicit svn rev. and ConfigurationOfVMMaker). >>> >>> >> Yes, it is reproduceable. But it is the same, in the Conf version, I need >> the version of easy_squeakvm script as you will commit after. >> > > > ? 1 version of easy_squeakvm uses automatically the right squeakvm revision > and the right version of ConfigurationOfVMMaker. So the reference is > not ConfigurationOfVMMaker nor squeakvm sources, but easy_squeakvm itself. > There as a misunderstood. I know easy_squeakvm is completly reproducible. What I was saying is that someone that DOES NOT use easy_squeakvm should be reproducible too ;) Putting the SVN revision in the Metacello version helps with this. > > >> >> easy_squeakvm is linux specific...so I would put the svn version, not >> easy_squeakvm script ;) >> > > Yes it's true. But I think it's easily portable to MacOSX as it's a Unix > system. > > As there's some work on the Windows VM build to use CMake if I understand, > with cygwin we can have it too. > > And then we can automatically generate the One-Click archive from scratch > ;p > sounds cool. If I have time I will try easy_squeakvm in my Mac... > > I can tag easy_squeakvm 1.0 for Pharo 1.0, easy_squeakvm 1.1 for Pharo 1.1 > and so on. > > > Laurent Laffont. > > >> >> >>> May be we can "translate" easy_squeakvm to Smalltalk so we can have an >>> EasySqueakVM package (or better name) which is cross platform. >>> >> >> hahahah maybe ;) >> >> >>> >>> Cheers, >>> >>> Laurent Laffont >>> >>> http://pharocasts.blogspot.com/ >>> http://magaloma.blogspot.com/ >>> >>> >>> >>> >>>> >>>> Cheers >>>> >>>> Mariano >>>> >>>> >>>> >>>>> Laurent Laffont >>>>> >>>>> http://pharocasts.blogspot.com/ >>>>> http://magaloma.blogspot.com/ >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

May 11, 2010

[Pharo-project] Fwd: Re: DEVImageCreator >> setDefaultPreferences (alain?)

by Alain Plantec

-------- Message original -------- Sujet: Re: DEVImageCreator >> setDefaultPreferences (alain?) Date : Tue, 11 May 2010 13:55:41 +0200 De : Alain Plantec <alain.plantec(a)free.fr> RÃ©pondre Ã : alain.plantec(a)free.fr Pour : Mariano Martinez Peck <marianopeck(a)gmail.com> Hi Mariano, all Le 11/05/2010 11:43, Mariano Martinez Peck a Ã©crit : > Hi Alain. DEVImageCreator has to be updated to use the new > preferences. I can do it but it will require much more than for me > than for you ;) > > For preferences it is DEVImageCreator>> setDefaultPreferences > it is using Preferences class for the moment. It should be updated to > use Settings, isn't it ? I don't think so. There is no need for such a initialization anymore since package are defining their own preferences. If a default value is desired then it should be set by an initialization method or lazily by the getter. I find the lazy initialization better because then, the SettingBrowser can reset the preference to the default by setting it to nil. > BTW, Preferences is still present in Pharo 1.1 and thus, > setDefaultPreferences is still working but I guess it should be updated. why ? there is no need for setDefaultPreferences anymore. > > Do you know when Preferences class will be completely removed? Pharo 1.2? I don't know. Maybe we can let it in the 1.1 in order to let maintainers the possibility to port their packages and definitively remove it in 1.2. The same for TheWorldMenu I guess. Cheers Alain > > Thanks! > > Mariano

May 11, 2010