November 2012 - Pharo-dev - lists.pharo.org

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

by Igor Stasenko

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. > 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.

Nov. 21, 2012

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

by Fernando Olivero

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 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 > >

Nov. 21, 2012

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

by Igor Stasenko

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.

Nov. 21, 2012

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

by Mariano Martinez Peck

>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

Nov. 21, 2012

[Pharo-project] Loading NBOpenGL in pharo 2

by Javier PimÃ¡s

Igor, while loading ConfigurationOfNBOpenGL this things are missing: NBUnsignedLong TTFontReader TTFontDescription TTGlyph are they still needed? -- Lic. Javier PimÃ¡s Ciudad de Buenos Aires

Nov. 21, 2012

Re: [Pharo-project] [update 2.0] #20414

by StÃ©phane Ducasse

> Hi Stef, > > because this method can be called from Form class >> #fromFileNamed: > and can work in case you use native binary Form representation. I would move fromFileNamed: too Stef > Any idea how to solve it in more cleaner way? > > Cheers, > -- Pavel > > > > On Wed, Nov 21, 2012 at 2:50 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Pavel >> >> why not moving this class on the ImageWriter package >> because >> - I do not like this Smalltalk globals at: ifPresent: >> especially when there is no default. >> >> - This method does not make sense without the ImageReadWriter >> >> >> Form classSide>>fromBinaryStream: (in category 'instance creation') -----fromBinaryStream: aBinaryStream >> "Read a Form or ColorForm from given file, using the first byte of the file to guess its format. Currently handles: GIF, uncompressed BMP, and both old and new DisplayObject writeOn: formats, JPEG, and PCX. Return nil if the file could not be read or was of an unrecognized format." >> >> | firstByte | >> aBinaryStream binary. >> firstByte := aBinaryStream next. >> firstByte = 1 ifTrue: [ >> "old Squeakform format" >> ^ self new readFromOldFormat: aBinaryStream]. >> firstByte = 2 ifTrue: [ >> "new Squeak form format" >> ^ self new readFrom: aBinaryStream]. >> >> "Try for JPG, GIF, or PCX..." >> "Note: The following call closes the stream." >> + Smalltalk globals at: #ImageReadWriter ifPresent: [:imageReadWriter | >> + ^ imageReadWriter formFromStream: aBinaryStream] >

Nov. 21, 2012

Re: [Pharo-project] [update 2.0] #20414

by Pavel Krivanek

Hi Stef, because this method can be called from Form class >> #fromFileNamed: and can work in case you use native binary Form representation. Any idea how to solve it in more cleaner way? Cheers, -- Pavel On Wed, Nov 21, 2012 at 2:50 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Pavel > > why not moving this class on the ImageWriter package > because > - I do not like this Smalltalk globals at: ifPresent: > especially when there is no default. > > - This method does not make sense without the ImageReadWriter > > > Form classSide>>fromBinaryStream: (in category 'instance creation') -----fromBinaryStream: aBinaryStream > "Read a Form or ColorForm from given file, using the first byte of the file to guess its format. Currently handles: GIF, uncompressed BMP, and both old and new DisplayObject writeOn: formats, JPEG, and PCX. Return nil if the file could not be read or was of an unrecognized format." > > | firstByte | > aBinaryStream binary. > firstByte := aBinaryStream next. > firstByte = 1 ifTrue: [ > "old Squeakform format" > ^ self new readFromOldFormat: aBinaryStream]. > firstByte = 2 ifTrue: [ > "new Squeak form format" > ^ self new readFrom: aBinaryStream]. > > "Try for JPG, GIF, or PCX..." > "Note: The following call closes the stream." > + Smalltalk globals at: #ImageReadWriter ifPresent: [:imageReadWriter | > + ^ imageReadWriter formFromStream: aBinaryStream]

Nov. 21, 2012

Re: [Pharo-project] Package-pane (or 6-paned) browser for Pharo?

by Ben Coman

Depending on whether you want it as a dependency, you might try Glamour... http://www.themoosebook.org/book/internals/glamour http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/Glamour.pdf cheers, Ben Stephen Travis Pope wrote: > Hello all, > > I'm just moving to pharo, and wanted to port the "package-pane browser" that I > originally wrote for Smalltalk-80 and then ported to Squeak. The squeak code > obviously doesn't run in pharo, and I wanted to ask whether anyone had already > ported it (or something like it). > > Basically, the tool is just like the standard system browser, except that it > parses the class category names into a 2-level hierarchy, making the top-level > list much smaller and more manageable (see the screen shot below). > > Does this already exist? > > ...any reply appreciated... > > stp > > > > -- > > Stephen Travis Pope Santa Barbara, California, USA > http://HeavenEverywhere.com <http://HeavenEverywhere.com/> > > > >

Nov. 21, 2012

[Pharo-project] [update 2.0] #20415

by Marcus Denker

20415 ----- Issue 7017: Code Duplication in UIManager>>#request:regex: and MorphicUIManager>>#request:regex: and http://code.google.com/p/pharo/issues/detail?id=7017 Issue 7020: Named String Interpolation for String>>#format: http://code.google.com/p/pharo/issues/detail?id=7020 Issue 7022: remove defaultImageHandler and defaultGZipHandler http://code.google.com/p/pharo/issues/detail?id=7022 Diff information: http://ss3.gemstone.com/ss/Pharo20/UIManager-MarcusDenker.90.diff http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.747.diff http://ss3.gemstone.com/ss/Pharo20/Regex-Core-MarcusDenker.19.diff http://ss3.gemstone.com/ss/Pharo20/Polymorph-Widgets-MarcusDenker.733.diff http://ss3.gemstone.com/ss/Pharo20/CollectionsTests-MarcusDenker.581.diff http://ss3.gemstone.com/ss/Pharo20/Collections-Strings-MarcusDenker.236.diff -- Marcus Denker -- http://marcusdenker.de

Nov. 21, 2012

Re: [Pharo-project] [update 2.0] #20414

by StÃ©phane Ducasse

Pavel why not moving this class on the ImageWriter package because - I do not like this Smalltalk globals at: ifPresent: especially when there is no default. - This method does not make sense without the ImageReadWriter Form classSide>>fromBinaryStream: (in category 'instance creation') -----fromBinaryStream: aBinaryStream "Read a Form or ColorForm from given file, using the first byte of the file to guess its format. Currently handles: GIF, uncompressed BMP, and both old and new DisplayObject writeOn: formats, JPEG, and PCX. Return nil if the file could not be read or was of an unrecognized format." | firstByte | aBinaryStream binary. firstByte := aBinaryStream next. firstByte = 1 ifTrue: [ "old Squeakform format" ^ self new readFromOldFormat: aBinaryStream]. firstByte = 2 ifTrue: [ "new Squeak form format" ^ self new readFrom: aBinaryStream]. "Try for JPG, GIF, or PCX..." "Note: The following call closes the stream." + Smalltalk globals at: #ImageReadWriter ifPresent: [:imageReadWriter | + ^ imageReadWriter formFromStream: aBinaryStream]

Nov. 21, 2012