- Pharo-dev - lists.pharo.org

Re: [Pharo-project] I don't agree with DummyXXX

by Sebastian Sastre

be careful with precision vs. intuition conventions each of them have benefits for the long and short term also a price On Nov 21, 2012, at 4:14 PM, Igor Stasenko wrote: > On 21 November 2012 15:11, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 21 November 2012 14:55, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >>> >>> >>> On Wed, Nov 21, 2012 at 4:50 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>> >>>> On 21 November 2012 12:47, Fernando Olivero <fernando.olivero(a)usi.ch> >>>> wrote: >>>>> I totally agree. Dummy does not tell me about the class. >>>>> >>>>> Are there just 3 uses of Dummy in the core? >>>>> >>>>> We should either use Null or use a specific prefix always, so its form >>>>> a >>>>> consisten pattern. >>>>> >>>>> DummyUIManager -> NullUIManager >>>>> >>>> yes, not "Headless" please. >>>> >>> >>> why? >>> >>> It is not a complete NULL UIManager. A NullUIManager would implement all >>> the API and do nothing (or implement nothing but only #doesNotUnderstand: >>> doing nothing or something like that) DummyUIManger DOES stuff, but it >>> makes sures not to end up calling the UI (like progress bar, notifications, >>> confirmations, etc). So, in this particular case, HeadlessUIManager is much >>> more accurate for me than Null. >>> >> then you will need to explain EVERY time to users why they should use >> CommandLineUIManager, or NonInteractiveUIManager for headless mode, >> rather than HeadlessUIManager. >> Good luck with that :) >> > > this is, btw , one of the reasons why i picked NonInteractive name > instead of calling it 'headless'. > Because it is more precise. And Camillo also used 'CommandLine' > instead of 'Headless'. > > In this regard, Dummy/Null is much more precise with describing > behavior of that ui manager class than headless. > > -- > Best regards, > Igor Stasenko. >

Nov. 21, 2012

Re: [Pharo-project] Metacello Why symbolicversion and not simply tagged version:?

by Dale Henrichs

Stef, I'm not sure which context you are talking about ... the symbolic version #stable can be used as an argument anywhere that the linear version '1.1' can be used, so I think that it is true that symbolic versions can be used in a #version: message ... So I guess I need a little more context ... Dale ----- Original Message ----- | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> | To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> | Sent: Friday, November 16, 2012 2:19:02 PM | Subject: [Pharo-project] Metacello Why symbolicversion and not simply tagged version:? | | Dale | | in my goal to reduce the complexity of metacello, I'm wondering why | symbolic versions could not be expressed as version: | | because | | version: #stable | version: #development | | are symbolic versions and there is no clash possible with | | version: '1.1' | | Stef | |

Nov. 21, 2012

Re: [Pharo-project] I don't agree with DummyXXX

by Igor Stasenko

On 21 November 2012 15:11, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 21 November 2012 14:55, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> >> >> On Wed, Nov 21, 2012 at 4:50 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>> On 21 November 2012 12:47, Fernando Olivero <fernando.olivero(a)usi.ch> >>> wrote: >>> > I totally agree. Dummy does not tell me about the class. >>> > >>> > Are there just 3 uses of Dummy in the core? >>> > >>> > We should either use Null or use a specific prefix always, so its form >>> > a >>> > consisten pattern. >>> > >>> > DummyUIManager -> NullUIManager >>> > >>> yes, not "Headless" please. >>> >> >> why? >> >> It is not a complete NULL UIManager. A NullUIManager would implement all >> the API and do nothing (or implement nothing but only #doesNotUnderstand: >> doing nothing or something like that) DummyUIManger DOES stuff, but it >> makes sures not to end up calling the UI (like progress bar, notifications, >> confirmations, etc). So, in this particular case, HeadlessUIManager is much >> more accurate for me than Null. >> > then you will need to explain EVERY time to users why they should use > CommandLineUIManager, or NonInteractiveUIManager for headless mode, > rather than HeadlessUIManager. > Good luck with that :) > this is, btw , one of the reasons why i picked NonInteractive name instead of calling it 'headless'. Because it is more precise. And Camillo also used 'CommandLine' instead of 'Headless'. In this regard, Dummy/Null is much more precise with describing behavior of that ui manager class than headless. -- Best regards, Igor Stasenko.

Nov. 21, 2012

Re: [Pharo-project] when do we go beta?

by Esteban Lorenzano

I was thinking on going beta next week, actually :) On Nov 21, 2012, at 6:32 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > On 21 Nov 2012, at 17:19, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> when do we go beta? > > I have been using 2.0 for months now, it has been very stable (apart from some hiccups). > > It is so much better that it would be immoral to keep this from the world ;-) > > We just have to declare a stabilization period in which we refrain from big/dangerous changes and work more on stability and testing. > > My 2c, > > Sven > > >

Nov. 21, 2012

Re: [Pharo-project] I don't agree with DummyXXX

by Igor Stasenko

On 21 November 2012 14:55, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Wed, Nov 21, 2012 at 4:50 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> On 21 November 2012 12:47, Fernando Olivero <fernando.olivero(a)usi.ch> >> wrote: >> > I totally agree. Dummy does not tell me about the class. >> > >> > Are there just 3 uses of Dummy in the core? >> > >> > We should either use Null or use a specific prefix always, so its form >> > a >> > consisten pattern. >> > >> > DummyUIManager -> NullUIManager >> > >> yes, not "Headless" please. >> > > why? > > It is not a complete NULL UIManager. A NullUIManager would implement all > the API and do nothing (or implement nothing but only #doesNotUnderstand: > doing nothing or something like that) DummyUIManger DOES stuff, but it > makes sures not to end up calling the UI (like progress bar, notifications, > confirmations, etc). So, in this particular case, HeadlessUIManager is much > more accurate for me than Null. > then you will need to explain EVERY time to users why they should use CommandLineUIManager, or NonInteractiveUIManager for headless mode, rather than HeadlessUIManager. Good luck with that :) >> > Fernando >> > >> > On Wed, Nov 21, 2012 at 4:34 PM, Mariano Martinez Peck >> > <marianopeck(a)gmail.com> wrote: >> >> >> >> From what I understand, Dummy means something different. I have using >> >> that >> >> for class names. More accurate names can be found. >> >> I would rename: >> >> >> >> DummyUIManager -> HeadlessUIManager >> >> DummySystemProgressItem -> NullSystemProgressItem >> >> DummySoundSystem -> NullSoundSystem >> >> >> >> what do you think? do you have better names? >> >> >> >> -- >> >> Mariano >> >> http://marianopeck.wordpress.com >> >> >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > Mariano > http://marianopeck.wordpress.com > -- Best regards, Igor Stasenko.

Nov. 21, 2012

Re: [Pharo-project] Loading NBOpenGL in pharo 2

by Igor Stasenko

On 21 November 2012 13:17, Javier PimÃ¡s <elpochodelagente(a)gmail.com> wrote: > ok, I'll update the config. About the fonts, do you know if these clases > were removed from pharo? > apparently they were removed. I don't remember where, but there should be a separate package to load these classes back (so we can add it to config to load them). > > On Wed, Nov 21, 2012 at 12:40 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> On 21 November 2012 12:28, Javier PimÃ¡s <elpochodelagente(a)gmail.com> >> wrote: >> > Igor, while loading ConfigurationOfNBOpenGL this things are missing: >> > >> > NBUnsignedLong >> > >> hmm.. this is because latest version of NativeBoost renamed this class >> to NBUInt32 >> that means we need to update config of opengl, >> and of course update this dependency. >> >> > TTFontReader >> > TTFontDescription >> > TTGlyph >> > >> this needs for demo to work.. but sure , it is not required for opengl >> to function. >> > >> > are they still needed? >> > >> > -- >> > Lic. Javier PimÃ¡s >> > Ciudad de Buenos Aires >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > Lic. Javier PimÃ¡s > Ciudad de Buenos Aires -- Best regards, Igor Stasenko.

Nov. 21, 2012

Re: [Pharo-project] I don't agree with DummyXXX

by Mariano Martinez Peck

On Wed, Nov 21, 2012 at 4:50 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 21 November 2012 12:47, Fernando Olivero <fernando.olivero(a)usi.ch> > wrote: > > I totally agree. Dummy does not tell me about the class. > > > > Are there just 3 uses of Dummy in the core? > > > > We should either use Null or use a specific prefix always, so its form a > > consisten pattern. > > > > DummyUIManager -> NullUIManager > > > yes, not "Headless" please. > > why? It is not a complete NULL UIManager. A NullUIManager would implement all the API and do nothing (or implement nothing but only #doesNotUnderstand: doing nothing or something like that) DummyUIManger DOES stuff, but it makes sures not to end up calling the UI (like progress bar, notifications, confirmations, etc). So, in this particular case, HeadlessUIManager is much more accurate for me than Null. > Fernando > > > > On Wed, Nov 21, 2012 at 4:34 PM, Mariano Martinez Peck > > <marianopeck(a)gmail.com> wrote: > >> > >> From what I understand, Dummy means something different. I have using > that > >> for class names. More accurate names can be found. > >> I would rename: > >> > >> DummyUIManager -> HeadlessUIManager > >> DummySystemProgressItem -> NullSystemProgressItem > >> DummySoundSystem -> NullSoundSystem > >> > >> what do you think? do you have better names? > >> > >> -- > >> Mariano > >> http://marianopeck.wordpress.com > >> > > > > > > -- > Best regards, > Igor Stasenko. > > -- Mariano http://marianopeck.wordpress.com

Nov. 21, 2012

Re: [Pharo-project] when do we go beta?

by Sven Van Caekenberghe

On 21 Nov 2012, at 17:19, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > when do we go beta? I have been using 2.0 for months now, it has been very stable (apart from some hiccups). It is so much better that it would be immoral to keep this from the world ;-) We just have to declare a stabilization period in which we refrain from big/dangerous changes and work more on stability and testing. My 2c, Sven

Nov. 21, 2012

Re: [Pharo-project] when do we go beta?

by Gary Chambers

Who knows... despite the (1.4 to 2.0 transition) we've had to stay on 1.4 for stability/sanity since we have a live product. Will take a while to ascertain the impact. Guess we go once final for us. Sorry not had the time to follow the 2.0 progression in use. Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, November 21, 2012 4:19 PM Subject: [Pharo-project] when do we go beta? > Stef >

Nov. 21, 2012

[Pharo-project] when do we go beta?

by StÃ©phane Ducasse

Stef

Nov. 21, 2012