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

[Pharo-project] [update 2.0] #20080

by StÃ©phane Ducasse

20080 ----- - Issue 5912: [ENH]: IntegerTests for Dummies. Thanks Sean De Nigris. http://code.google.com/p/pharo/issues/detail?id=5912 - Issue 5756: Failing tests: MC loading/ unloading. First test. http://code.google.com/p/pharo/issues/detail?id=5756 - Issue 5909: [ENH]: Easy TimeZone instances. Thanks Sean De Nigris. http://code.google.com/p/pharo/issues/detail?id=5909 - Issue 5897: [ENH]: Clean SystemProgressMorph and friends. Thanks Sean De Nigris. http://code.google.com/p/pharo/issues/detail?id=5897

May 20, 2012

[Pharo-project] SciSmalltalk on twitter !

by Serge Stinckwich

Dear all, Daniel Uber who is working on SciSmalltalk for #gsoc publish his progress on twitter: https://twitter.com/DanielUber We have also an official twitter account: https://twitter.com/SciSmalltalk More information about SciSmalltalk here: https://github.com/SergeStinckwich/SciSmalltalk I invite all the students that are working on Smalltalk #gsoc to publish progress of their work on twitter also. My twitter account if you want to follow some Smalltalk news around the world: https://twitter.com/SergeStinckwich Best regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

May 20, 2012

Re: [Pharo-project] Inspecting keys in Dictionaries

by Serge Stinckwich

Great work ! You should add Glamouroust to MetaRepoForPharo14 in order to be able to load it easily with the ConfigurationBrowser. Regards, On Sun, May 20, 2012 at 9:28 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > The GTInspector offers (among others) the possibility of inspecting the > association of a dictionary. I attached here a screenshot with inspecting > the BitBlt entry from the "Smalltalk globals" dictionary. > > The GTInspector can be loaded in Pharo 1.4 by: > > Gofer new > squeaksource: 'glamoroust'; > package: 'ConfigurationOfGlamoroust'; > load. > (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. > (Smalltalk at: #GTInspector) registerToolsOn: Smalltalk tools. > > Cheers, > Doru > > > On 20 May 2012, at 14:19, Davide Varvello wrote: > > Thanks Herby, > But if I run an inspector on keys I lose the possibility to see the name of > any single key because when you inspect an array you see only a numeric > list > on the left side of the inspector. Is there a way to avoid it? > > Davide > > > > Herby VojÄÃk wrote > > > Writing "nameOfTheDictionary keys" in the inspect window, selecting it > > and inspecting it? > > > Herby > > > Davide Varvello wrote: > > Hi, > > I'd like to inspect keys of a Dictionary but if I open an inspector on > > the > > dictionary and inspect a key, the inspector shows its value, instead I'd > > like it shows the key object. Is there an easy way to do it? > > > Cheers > > Davide > > > -- > > View this message in context: > > http://forum.world.st/Inspecting-keys-in-Dictionaries-tp4630944.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > -- > View this message in context: > http://forum.world.st/Inspecting-keys-in-Dictionaries-tp4630944p4630961.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > -- > www.tudorgirba.com > > "We are all great at making mistakes." > > > > > > > > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

May 20, 2012

Re: [Pharo-project] DateAndTime>>asDosTime

by Camillo Bruni

yep I would say so too... the major user is zip compression hence no one will ever notice the possibly flawed implementation :P On 2012-05-18, at 17:40, Sean P. DeNigris wrote: > asDosTime > "answer number of seconds since Dos epoch (midnight Jan 1, 1980, UTC)" > ^((self offset: Duration zero) - self class dosEpoch) asSeconds > > Everything I found online says that DOS date/times are bit masked: > http://blogs.msdn.com/b/oldnewthing/archive/2003/09/05/54806.aspx > http://mindprod.com/jgloss/zip.html > http://mail.python.org/pipermail/python-list/1999-December/614399.html > > 32 bits: > |Y|Y|Y|Y|Y|Y|Y|M| |M|M|M|D|D|D|D|D| |h|h|h|h|h|m|m|m| |m|m|m|s|s|s|s|s| > > Am I missing something, or is this a bug? > > Sean > > -- > View this message in context: http://forum.world.st/DateAndTime-asDosTime-tp4630789.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

May 20, 2012

Re: [Pharo-project] Inspecting keys in Dictionaries

by Camillo Bruni

This is standard question: re/post and answer on stackoverflow please! On 2012-05-20, at 14:19, Davide Varvello wrote: > Thanks Herby, > But if I run an inspector on keys I lose the possibility to see the name of > any single key because when you inspect an array you see only a numeric list > on the left side of the inspector. Is there a way to avoid it? > > Davide > > > > Herby VojÄÃk wrote >> >> Writing "nameOfTheDictionary keys" in the inspect window, selecting it >> and inspecting it? >> >> Herby >> >> Davide Varvello wrote: >>> Hi, >>> I'd like to inspect keys of a Dictionary but if I open an inspector on >>> the >>> dictionary and inspect a key, the inspector shows its value, instead I'd >>> like it shows the key object. Is there an easy way to do it? >>> >>> Cheers >>> Davide >>> >>> -- >>> View this message in context: >>> http://forum.world.st/Inspecting-keys-in-Dictionaries-tp4630944.html >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >> > > > -- > View this message in context: http://forum.world.st/Inspecting-keys-in-Dictionaries-tp4630944p4630961.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

May 20, 2012

Re: [Pharo-project] Inspecting keys in Dictionaries

by Tudor Girba

Hi, The GTInspector offers (among others) the possibility of inspecting the association of a dictionary. I attached here a screenshot with inspecting the BitBlt entry from the "Smalltalk globals" dictionary. The GTInspector can be loaded in Pharo 1.4 by: Gofer new squeaksource: 'glamoroust'; package: 'ConfigurationOfGlamoroust'; load. (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. (Smalltalk at: #GTInspector) registerToolsOn: Smalltalk tools. Cheers, Doru On 20 May 2012, at 14:19, Davide Varvello wrote: > Thanks Herby, > But if I run an inspector on keys I lose the possibility to see the name of > any single key because when you inspect an array you see only a numeric list > on the left side of the inspector. Is there a way to avoid it? > > Davide > > > > Herby VojÄÃk wrote >> >> Writing "nameOfTheDictionary keys" in the inspect window, selecting it >> and inspecting it? >> >> Herby >> >> Davide Varvello wrote: >>> Hi, >>> I'd like to inspect keys of a Dictionary but if I open an inspector on >>> the >>> dictionary and inspect a key, the inspector shows its value, instead I'd >>> like it shows the key object. Is there an easy way to do it? >>> >>> Cheers >>> Davide >>> >>> -- >>> View this message in context: >>> http://forum.world.st/Inspecting-keys-in-Dictionaries-tp4630944.html >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >> > > > -- > View this message in context: http://forum.world.st/Inspecting-keys-in-Dictionaries-tp4630944p4630961.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- www.tudorgirba.com "We are all great at making mistakes."

May 20, 2012

[Pharo-project] morphic help: how to handle grip morphs

by Tudor Girba

Hi, I want to get a window like behavior, but without having the window appear in the taskbar. Essentially, what I need is a BorderedMorph with some resizing abilities. I am trying to get a subclass of BorderedMorph to work with grips, but I have difficulties in setting the corners in the right places. What I do is essentially something like this: BorderedMorph new addCornerGrips; openInWorld Ignoring the fact that BorderedMorph does not understand fastFramingOn, the problem is that the corners appear somewhere in the middle of the morph. Could anyone tell me how to position them in the corners? Cheers, Doru -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar."

May 20, 2012

Re: [Pharo-project] [Pharo-consortium] We need your Pharo successes

by StÃ©phane Ducasse

Hi guys yes this is again us with other success stories :). https://gforge.inria.fr/frs/download.php/30804/vbridge.pdf https://gforge.inria.fr/frs/download.php/30805/SiROP-mindclue-Pharo-3Slides… https://gforge.inria.fr/frs/download.php/30802/emcee.pdf Of course we are still waiting for yours :) Stef I love the business oriented aspect that we are creating.

May 20, 2012

Re: [Pharo-project] Order of sending class side #initialize

by Mariano Martinez Peck

On Sun, May 20, 2012 at 1:51 PM, Edgar J. De Cleene <edgardec2005(a)gmail.com>wrote: > > > > On 5/19/12 6:20 PM, "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: > > because when exporting I am not using any order at all. > > > > Hey Mariano: > > IMHO you SHOULD use a exporting order and this could be the same when you > export a plain .cs. > > All you working on Fuel and Injectorare doing a great job !!! > > Hi. Answering to both you and Stef. What I found that works (at least with Seaside/Pier/Magritte) is to LOAD ALL packages first, and then send #initialize to classes, ordered by package. Example, Metacello told me the order of packages to load/initialize are PackageA, PackageC, PackageB. So, when I import I do: load PackageA load PackageC load PackageB send #initialize to classes of PackageA. send #initialize to classes of PackageC. send #initialize to classes of PackageB. If I do, instead, load PackageA send #initialize to classes of PackageA. load PackageC send #initialize to classes of PackageC. load PackageB send #initialize to classes of PackageB. it does not work. I guess this is because of what Dale said. Cheers -- Mariano http://marianopeck.wordpress.com

May 20, 2012

[Pharo-project] [update 2.0] #20079

by Marcus Denker

20079 ----- Issue 5924: SmallInteger>>digitAt: Test http://code.google.com/p/pharo/issues/detail?id=5924 Issue 5859: Do we remove SmartRefStream? http://code.google.com/p/pharo/issues/detail?id=5859 -- Marcus Denker -- http://marcusdenker.de

May 20, 2012