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

IconicListItem>>text:icon: recently changed with bug

by Damien Cassou

It looks like a bug got introduced recently in the Polymorph package. The following code does not work: text: aText icon: form ^ self new morph: aText asMorph; icon: (AlphaImageMorph new form: form); yourself #form: is not implemented in AlphaImageMorph. It looks like #image: must be sent instead. What do you think? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 11, 2013

Re: [Pharo-dev] [squeak-dev] Re: ModTalk

by Chris Muller

Well, if "doing" includes traveling across the world, getting up on a stage and talking about and promoting it, then I'd say all of them. Besides that, I have no idea what they're doing with their time. On Mon, Jun 10, 2013 at 11:41 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > > On Jun 11, 2013, at 7:58 AM, Chris Muller <asqueaker(a)gmail.com> wrote: > >> They presented it today. What I gathered is that it's a >> extra-curricular project for students to "get their hands dirty" after >> going through his Programming Languages class. One aim is to make a >> small, tiny, file-based Smalltalk project (without use of an image). >> It seemed pretty rough, which is perfect for students to have >> something difficult to wrangle with. >> >> The conference had a fantastic first day. So many well-known >> Smalltalkers are here -- Allen and Rebecca Wirfs Brock, Dave Thomas, >> Dan Ingalls and many more.. > > how many of them are still doing Smalltalk? > Allen is working on JS, no? > I know dan is working at SAP so is he using Smalltalk to build the tera bit VM? Still working on it? > > >> >> On Mon, Jun 10, 2013 at 9:29 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >>> Sounds interesting: http://www.stic.st/conferences/stic13/abstracts/modtalk-experience-report/ >>> >>> John Sarkela and Steve Jarvis talk about Modtalk at STIC13. Anyone knows more? >>> >>> >> > >

June 11, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by Marcus Denker

On Jun 11, 2013, at 4:54 PM, Sebastian Tleye <stleye(a)gmail.com> wrote: > If they are not different so a better way would be replace #flatenCollect: by #gather: > but anyway, moose people should decide and commit the change since i am not a moose developer. > > The moose people should have taken the lead to get the extension integrated a *long* time agoâ¦ nothing happens by itself. Marcus > 2013/6/11 Marcus Denker <marcus.denker(a)inria.fr> > > On Jun 11, 2013, at 4:24 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > > > On 11 June 2013 14:18, Sebastian Tleye <stleye(a)gmail.com> wrote: > >> Hello, > >> > >> Fixing some bugs in Traits we realized that it would be good idea to use > >> CollectionsExtensions package (it has some useful functions), also it would > >> be great to include CollectionsExtensions in Pharo 3.0. > > > > Is this the HPI library? I seem to recall TraitClasses [1] using it. > > CollectionExtension is from Moose. > > the Trait based Stream refactoring was done some years ago but has not been used > or maintained. > > Marcus >

June 11, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by Sebastian Tleye

If they are not different so a better way would be replace #flatenCollect: by #gather: but anyway, moose people should decide and commit the change since i am not a moose developer. 2013/6/11 Marcus Denker <marcus.denker(a)inria.fr> > > On Jun 11, 2013, at 4:24 PM, Frank Shearar <frank.shearar(a)gmail.com> > wrote: > > > On 11 June 2013 14:18, Sebastian Tleye <stleye(a)gmail.com> wrote: > >> Hello, > >> > >> Fixing some bugs in Traits we realized that it would be good idea to use > >> CollectionsExtensions package (it has some useful functions), also it > would > >> be great to include CollectionsExtensions in Pharo 3.0. > > > > Is this the HPI library? I seem to recall TraitClasses [1] using it. > > CollectionExtension is from Moose. > > the Trait based Stream refactoring was done some years ago but has not > been used > or maintained. > > Marcus >

June 11, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by Marcus Denker

On Jun 11, 2013, at 4:24 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 11 June 2013 14:18, Sebastian Tleye <stleye(a)gmail.com> wrote: >> Hello, >> >> Fixing some bugs in Traits we realized that it would be good idea to use >> CollectionsExtensions package (it has some useful functions), also it would >> be great to include CollectionsExtensions in Pharo 3.0. > > Is this the HPI library? I seem to recall TraitClasses [1] using it. CollectionExtension is from Moose. the Trait based Stream refactoring was done some years ago but has not been used or maintained. Marcus

June 11, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by Sebastian Tleye

I don't know, i should see the implementation, i just want to remove the dependency between CollectionsExtensions and Nile and one way to do it is modifying #flatCollect: implementation. if they are the same #flatCollect: could be remove safely replaced. 2013/6/11 Camille Teruel <camille.teruel(a)gmail.com> > > On 11 juin 2013, at 15:18, Sebastian Tleye wrote: > > > Hello, > > > > Fixing some bugs in Traits we realized that it would be good idea to use > CollectionsExtensions package (it has some useful functions), also it would > be great to include CollectionsExtensions in Pharo 3.0. > > > > One "problem" we found is that CollectionsExtensions is depending on a > Nile Package (that's not a desired feature). > > In the method Collection>>flatCollect: there is a line refering to a > nile function "nsWriteStream". > > How this #flatCollect: is different from #gather: anyway? > > > > > If i change "nsWriteStream" for "writeStream" the dependency disapears. > > > > I also run all the tests and they are working, so i was wondering if it > would be possible to commit the change. > > > > Thanks. > > >

June 11, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by Frank Shearar

On 11 June 2013 15:37, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 11 juin 2013, at 15:18, Sebastian Tleye wrote: > >> Hello, >> >> Fixing some bugs in Traits we realized that it would be good idea to use CollectionsExtensions package (it has some useful functions), also it would be great to include CollectionsExtensions in Pharo 3.0. >> >> One "problem" we found is that CollectionsExtensions is depending on a Nile Package (that's not a desired feature). >> In the method Collection>>flatCollect: there is a line refering to a nile function "nsWriteStream". > > How this #flatCollect: is different from #gather: anyway? Functionally, it's no different. frank >> If i change "nsWriteStream" for "writeStream" the dependency disapears. >> >> I also run all the tests and they are working, so i was wondering if it would be possible to commit the change. >> >> Thanks. > >

June 11, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by Camille Teruel

On 11 juin 2013, at 15:18, Sebastian Tleye wrote: > Hello, > > Fixing some bugs in Traits we realized that it would be good idea to use CollectionsExtensions package (it has some useful functions), also it would be great to include CollectionsExtensions in Pharo 3.0. > > One "problem" we found is that CollectionsExtensions is depending on a Nile Package (that's not a desired feature). > In the method Collection>>flatCollect: there is a line refering to a nile function "nsWriteStream". How this #flatCollect: is different from #gather: anyway? > > If i change "nsWriteStream" for "writeStream" the dependency disapears. > > I also run all the tests and they are working, so i was wondering if it would be possible to commit the change. > > Thanks.

June 11, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by Frank Shearar

On 11 June 2013 14:18, Sebastian Tleye <stleye(a)gmail.com> wrote: > Hello, > > Fixing some bugs in Traits we realized that it would be good idea to use > CollectionsExtensions package (it has some useful functions), also it would > be great to include CollectionsExtensions in Pharo 3.0. Is this the HPI library? I seem to recall TraitClasses [1] using it. frank [1] https://github.com/lauritzthamsen/TraitClasses > One "problem" we found is that CollectionsExtensions is depending on a Nile > Package (that's not a desired feature). > In the method Collection>>flatCollect: there is a line refering to a nile > function "nsWriteStream". > > If i change "nsWriteStream" for "writeStream" the dependency disapears. > > I also run all the tests and they are working, so i was wondering if it > would be possible to commit the change. > > Thanks.

June 11, 2013

[update 3.0] #30194

by Marcus Denker

30194 ----- 10546 Matrix class comment refers to Array2D which does not exist anymore https://pharo.fogbugz.com/f/cases/10546 10875 CleanUp in PolyMorph https://pharo.fogbugz.com/f/cases/10875 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Unordered-MarcusD…

June 11, 2013