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

Re: [Pharo-dev] Cairo vs openGL

by Henrik Johansen

On Jun 12, 2013, at 11:22 AM, StÃ©phane Ducasse wrote: > Hi > > I discuss with an graphics expert and he asked me why we went to use cairo vs opengl > And I could not answer. > > Stef The question needs more context to make sense. Cairo and OpenGL are different tools (2D vs 3D), and the answer of which to use is defined by what you are doing. If what you are doing, is building scalable, flat interfaces, it makes no sense to implement that using OpenGL directly (though making an OpenGL backend to some frontend 2D-library like Athens, in order to have the operations hardware-accellerated on the GPU, is certainly possible). If what you are doing, is building a VR simulation of a meeting room, it makes no sense to implement that in Cairo. Cheers, Henry

June 12, 2013

Re: [Pharo-dev] ZeroConf and write permission

by Camillo Bruni

On 2013-06-12, at 12:49, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 12 June 2013 11:40, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >> On 2013-06-12, at 12:13, Frank Shearar <frank.shearar(a)gmail.com> wrote: >> >>> Or curl http://get.pharo.org/vm | sudo bash. >> >> that was my first guess, but it didn't work under my zsh shell and mac... > > Strange. It works in bash. I have to enter a password for sudo, maybe it's that?

June 12, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by StÃ©phane Ducasse

+ 1 guys a name and an implementation body are two separate entities. > >> #gather: directly applies the stream fusion technique as its >> implementation, so is faster than the current implementation of >> #flatCollect: >> >> Stef's saying "why not move #gather:'s implemenation to #flatCollect:, >> and make the old #gather: call the new #flatCollect:" > > Er, and that would mean moving #flatCollect: out of > CollectionsExtensions into the base image. > >> frank >> >> On 12 June 2013 10:33, Sebastian Tleye <stleye(a)gmail.com> wrote: >>> As far as i know the implementation of gather: is faster than the >>> implementation of flatCollect: >>> >>> >>> 2013/6/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> >>>> Why not the inverse. >>>> They are much more users of flatCollect: then gather: >>>> >>>> and again gather: sucks. It does not convey that this is a mapcan >>>> ie happening the results of each iteration into the >>>> >>>> So flatCollect: is 10 times more explicit and better. >>>> you flatten the results of the collect: >>>> >>>> Stef >>>> >>>> >>>> I think the simplest solution is to keep both and that flatCollect >>>> directly call gather: >>>> >>>> If you agree with that, I will correct the moose extension package >>>> >>>> >>>> 2013/6/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>>> >>>>> gather: sucks as a name. >>>>> flatCollect: is much better so do not remove it. >>>>> >>>>> On Jun 11, 2013, at 4:53 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. >>>>> >>>>> >>>>> 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 >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Guillaume Larcheveque >>>> >>>> >>> >

June 12, 2013

Re: [Pharo-dev] ZeroConf and write permission

by Frank Shearar

On 12 June 2013 11:40, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-06-12, at 12:13, Frank Shearar <frank.shearar(a)gmail.com> wrote: > >> Or curl http://get.pharo.org/vm | sudo bash. > > that was my first guess, but it didn't work under my zsh shell and mac... Strange. It works in bash. frank

June 12, 2013

Re: [Pharo-dev] ZeroConf and write permission

by Camillo Bruni

On 2013-06-12, at 12:13, Frank Shearar <frank.shearar(a)gmail.com> wrote: > Or curl http://get.pharo.org/vm | sudo bash. that was my first guess, but it didn't work under my zsh shell and mac...

June 12, 2013

Re: [Pharo-dev] Cairo vs openGL

by Esteban Lorenzano

Cairo is a 2D SVG library, OpenGL it is not (is 3D, etc.). Of course it can be done with OpenGL (and if I succeed on annoying Igor asking for it enough, it will be there :) ), but OpenGL is about describing small triangles. Cairo, however, is easier... I suppose that's the main reason why is made with it. Esteban On Jun 12, 2013, at 11:22 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > I discuss with an graphics expert and he asked me why we went to use cairo vs opengl > And I could not answer. > > Stef

June 12, 2013

Re: [Pharo-dev] [ANN]: Magritte for Morphic (alpha)

by Edgar J. De Cleene

On 6/11/13 6:18 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > Tired of writing the same UI boilerplate over and over? I mean, basically an > object has fields, which have certain properties relevant to the UI. If we > could just capture that info once in the right place, a basic UI should > almost fall out on its own. Magritte could be the answers to our lazy > utopian dreams. The thing is that the Morphic implementation as fallen > behind what can be done in Seaside... until now. I took a first pass at > bringing Morphic up to date here. It doesn't seem like it will be too hard > to have reasonably useful functionality. > > Here's a short screencast showing the improvements: > http://vimeo.com/68166920 > Magritte is an awesome framework to automate common UI tasks. Describe your > object's field once, get views everywhere. Everywhere most commonly refers > to both the web, via Seaside, and desktop via Morphic. But the Morphic > implementation had fallen behind due to disuse. Now, some steps have been > taken to bring the Morphic functionality up to date with that of Seaside. > > > > ----- > Cheers, > Sean I think is a good solution. You try this url: 'ss3.gemstone.com/ss/MagritteMagic' in Squeak ? Edgar

June 12, 2013

Re: [Pharo-dev] ZeroConf and write permission

by Sven Van Caekenberghe

On 12 Jun 2013, at 12:13, Frank Shearar <frank.shearar(a)gmail.com> wrote: > Or curl http://get.pharo.org/vm | sudo bash. Yes, of course, much better ! > frank > > On 12 June 2013 06:26, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> I think the sudo only takes the first command, curl, not the bash. >> >> Maybe sudo "curl -L get.pharo.org/vm | bash" or something like that ? >> >> Sven >> >> On 12 Jun 2013, at 03:58, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: >> >>> I'm on a Mac w. Mountain Lion and I want to put my vm in /usr/local/bin, but >>> my account is not an administrator. sudo does not help: >>> >>> sudo curl -L get.pharo.org/vm | bash >>> Password: >>> % Total % Received % Xferd Average Speed Time Time Time >>> Current >>> Dload Upload Total Spent Left >>> Speed >>> 100 5272 100 5272 0 0 26464 0 --:--:-- --:--:-- --:--:-- >>> 51686 >>> Downloading the latest pharoVM: >>> http://files.pharo.org/vm/pharo/mac/stable.zip >>> mkdir: pharo-vm: Permission denied >>> >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: http://forum.world.st/ZeroConf-and-write-permission-tp4692903.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> >> >> >

June 12, 2013

Re: [Pharo-dev] ZeroConf and write permission

by Frank Shearar

Or curl http://get.pharo.org/vm | sudo bash. frank On 12 June 2013 06:26, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I think the sudo only takes the first command, curl, not the bash. > > Maybe sudo "curl -L get.pharo.org/vm | bash" or something like that ? > > Sven > > On 12 Jun 2013, at 03:58, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > >> I'm on a Mac w. Mountain Lion and I want to put my vm in /usr/local/bin, but >> my account is not an administrator. sudo does not help: >> >> sudo curl -L get.pharo.org/vm | bash >> Password: >> % Total % Received % Xferd Average Speed Time Time Time >> Current >> Dload Upload Total Spent Left >> Speed >> 100 5272 100 5272 0 0 26464 0 --:--:-- --:--:-- --:--:-- >> 51686 >> Downloading the latest pharoVM: >> http://files.pharo.org/vm/pharo/mac/stable.zip >> mkdir: pharo-vm: Permission denied >> >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/ZeroConf-and-write-permission-tp4692903.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >

June 12, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by Frank Shearar

On 12 June 2013 10:54, Frank Shearar <frank.shearar(a)gmail.com> wrote: > #gather: directly applies the stream fusion technique as its > implementation, so is faster than the current implementation of > #flatCollect: > > Stef's saying "why not move #gather:'s implemenation to #flatCollect:, > and make the old #gather: call the new #flatCollect:" Er, and that would mean moving #flatCollect: out of CollectionsExtensions into the base image. > frank > > On 12 June 2013 10:33, Sebastian Tleye <stleye(a)gmail.com> wrote: >> As far as i know the implementation of gather: is faster than the >> implementation of flatCollect: >> >> >> 2013/6/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> >>> Why not the inverse. >>> They are much more users of flatCollect: then gather: >>> >>> and again gather: sucks. It does not convey that this is a mapcan >>> ie happening the results of each iteration into the >>> >>> So flatCollect: is 10 times more explicit and better. >>> you flatten the results of the collect: >>> >>> Stef >>> >>> >>> I think the simplest solution is to keep both and that flatCollect >>> directly call gather: >>> >>> If you agree with that, I will correct the moose extension package >>> >>> >>> 2013/6/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> >>>> gather: sucks as a name. >>>> flatCollect: is much better so do not remove it. >>>> >>>> On Jun 11, 2013, at 4:53 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. >>>> >>>> >>>> 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 >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Guillaume Larcheveque >>> >>> >>

June 12, 2013