May 2011 - Pharo-users - lists.pharo.org

some news about the consortium

by StÃ©phane Ducasse

Hi pharoers yesterday we got a meeting with INRIA people and we discussed the creation of an INRIA consortium. We will follow the INRIA process and propose officially the creation. For that we will have to present a proposal by end of June so we will do it. I would like to see the consortium taking life by end of the year and there are still some work to be done there. Stef

May 25, 2011

Re: [Pharo-users] [COTDC] 68 - MultiNewParagraph

by Igor Stasenko

On 24 May 2011 22:31, laurent laffont <laurent.laffont(a)gmail.com> wrote: > Today:Â MultiNewParagraph > Alain Plantec could say more, since more of the methods in this class marked under his authorship. > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results:Â http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > Laurent -- Best regards, Igor Stasenko AKA sig.

May 24, 2011

Re: [Pharo-users] [Pharo-project] [COTDC] 67#2 - MultiDisplayScanner

by Igor Stasenko

I think this class is to reflect changes introduced to MultiParagraph or MultiNewParagraph whatever. As for the rest , its role in system is same as for DisplayScanner This part requires cleanup. We don't need two classes implementing behavior for displaying text on the screen, as long as text (i.e. Text class) are unchanged. On 24 May 2011 22:28, laurent laffont <laurent.laffont(a)gmail.com> wrote: > > On Mon, May 23, 2011 at 10:51 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> I'm a class related to the computation of characters counting for text >> flow. >> >> I'm probably wrong but this is what I think I remember from what I guessed >> :) > > > COTDC new guessCommentOf:Â MultiDisplayScanner. Â :) > Laurent. > >> >> Stef >> >> >> On May 23, 2011, at 9:40 PM, laurent laffont wrote: >> >> > Today: MultiDisplayScanner >> > >> > >> > Comment Of The Day Contest - One Day One Comment >> > Rules: >> > #1: Each day a not commented class is elected. Each day the best comment >> > will be integrated with name of the author(s). >> > #2: If you cannot comment it, deprecate it. >> > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >> > >> > Laurent >> > >> >> > > -- Best regards, Igor Stasenko AKA sig.

May 24, 2011

Re: [Pharo-users] ESUG SummerTalk - Fuel, binary object serializer

by Benjamin

I definitively want it in Hazel ^^ Ben On May 24, 2011, at 10:39 PM, Martin Dias wrote: > Hi folks. I am really happy to announce that ESUG is sponsoring me for Fuel development through the ESUG SummerTalk. I am Martin Dias, a student at Buenos Aires, Argentina. The idea behind this SummerTalk is to implement Fuel, a binary, fast and general-purpose object graph serializer in Pharo. It is based on VisualWorks' Parcels ideas. > > Actually, the project has already started since several months. Tristan Bourgois and I started with the project while doing an internship with RMoD, INRIA. Since a couple of months, Mariano Martinez Peck joined the team, and now he is the official mentor in the SummerTalk. > > ESUG website for SummertTalk: http://www.esug.org/wiki/pier/Promotion/SummerTalk/SummerTalk2011 > > The website with all the necessary information is here: http://rmod.lille.inria.fr/web/pier/software/Fuel > It even includes slides explaining the algorithm. In addition, a paper is in progress. > > For the moment, Fuel already provides the following features: > > - Fast pickle format. It is much faster to materialize than to serialize. > - Correctly support class reshape (when the class of serialized objects has changed). > - Serialize ANY kind of object. For the moment there is no object to our knowledge that we cannot serialize and materialize. > - Be able to completely serialize classes and traits (not just a global name). > - Support cycles and avoid duplicates in the graph. > - Integration to Moose with an extension to export and import their models. > - Detection of globals: for example if you serialize Transcript, it is not duplicated and instead managed as a global reference. > - Solve common problems like Set rehash. > - Buffered writing: we use a buffered write stream for the serialization part (thanks Sven!). > - No need of special support from the VM. > - Try to have a good object oriented design. > - Well tested (about 120 tests, for the moment). > - Large set of benchmarks (even benchmarks for Moose extension). > > And of course, there are a lot features for the future. You can see some of them in the website and some in the issue tracker: http://code.google.com/p/fuel/issues/list > > We really appreciate all kind of feedback and comments. If you want to try it, check in the website how to do it. It is extremely easy. > > Once again, I want to thank a lot to ESUG for sponsoring the project. I plan to create a "news" section in the website with some RSS. I will keep you informed. > > Best regards, > Martin >

May 24, 2011

ESUG SummerTalk - Fuel, binary object serializer

by Martin Dias

Hi folks. I am really happy to announce that ESUG is sponsoring me for Fuel development through the ESUG SummerTalk. I am Martin Dias, a student at Buenos Aires, Argentina. The idea behind this SummerTalk is to implement Fuel, a binary, fast and general-purpose object graph serializer in Pharo<http://www.pharo-project.org/>. It is based on VisualWorks' Parcels ideas. Actually, the project has already started since several months. Tristan Bourgois and I started with the project while doing an internship with RMoD, INRIA <http://rmod.lille.inria.fr/web/pier>. Since a couple of months, Mariano Martinez Peck <http://marianopeck.wordpress.com/> joined the team, and now he is the official mentor in the SummerTalk. ESUG website for SummertTalk: http://www.esug.org/wiki/pier/Promotion/SummerTalk/SummerTalk2011 The website with all the necessary information is here: http://rmod.lille.inria.fr/web/pier/software/Fuel It even includes slides explaining the algorithm. In addition, a paper is in progress. For the moment, Fuel already provides the following features: - Fast pickle format. It is much faster to materialize than to serialize. - Correctly support class reshape (when the class of serialized objects has changed). - Serialize ANY kind of object. For the moment there is no object to our knowledge that we cannot serialize and materialize. - Be able to completely serialize classes and traits (not just a global name). - Support cycles and avoid duplicates in the graph. - Integration to Moose <http://www.moosetechnology.org/> with an extension to export and import their models. - Detection of globals: for example if you serialize Transcript, it is not duplicated and instead managed as a global reference. - Solve common problems like Set rehash. - Buffered writing: we use a buffered write stream for the serialization part (thanks Sven!). - No need of special support from the VM. - Try to have a good object oriented design. - Well tested (about 120 tests, for the moment). - Large set of benchmarks (even benchmarks for Moose extension). And of course, there are a lot features for the future. You can see some of them in the website and some in the issue tracker: http://code.google.com/p/fuel/issues/list We really appreciate all kind of feedback and comments. If you want to try it, check in the website how to do it. It is extremely easy. Once again, I want to thank a lot to ESUG for sponsoring the project. I plan to create a "news" section in the website with some RSS. I will keep you informed. Best regards, Martin

May 24, 2011

[COTDC] 68 - MultiNewParagraph

by laurent laffont

Today: MultiNewParagraph Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

May 24, 2011

Re: [Pharo-users] [Pharo-project] [COTDC] 67#2 - MultiDisplayScanner

by laurent laffont

On Mon, May 23, 2011 at 10:51 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > I'm a class related to the computation of characters counting for text > flow. > > I'm probably wrong but this is what I think I remember from what I guessed > :) > COTDC new guessCommentOf: MultiDisplayScanner. :) Laurent. > Stef > > > On May 23, 2011, at 9:40 PM, laurent laffont wrote: > > > Today: MultiDisplayScanner > > > > > > Comment Of The Day Contest - One Day One Comment > > Rules: > > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > > #2: If you cannot comment it, deprecate it. > > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > > > Laurent > > > > >

May 24, 2011

Re: [Pharo-users] Wiki-gardening on the Pharo online book

by StÃ©phane Ducasse

tx simon! This would be so great. Stef On May 24, 2011, at 2:48 PM, Simon Denier wrote: > > On 24 mai 2011, at 14:23, Mariano Martinez Peck wrote: > >> Yes, +99999 >> That would be great. >> Could you take care? at least a first pass? > > sure, I will try to take a look > >> >> On Tue, May 24, 2011 at 2:00 PM, Simon Denier <simon.denier(a)gmail.com> wrote: >> Looking at the TOC of the Pharo online book, there are lots of new things, including duplicated/empty chapters especially in the Pharo tools section. What about a bit of wiki gardening in the next days? >> >> http://book.pharo-project.org/book/table-of-contents >> >> -- >> Simon Denier >> >> >> >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- > Simon Denier > > >

May 24, 2011

Re: [Pharo-users] Wiki-gardening on the Pharo online book

by Simon Denier

On 24 mai 2011, at 14:23, Mariano Martinez Peck wrote: > Yes, +99999 > That would be great. > Could you take care? at least a first pass? sure, I will try to take a look > > On Tue, May 24, 2011 at 2:00 PM, Simon Denier <simon.denier(a)gmail.com> wrote: > Looking at the TOC of the Pharo online book, there are lots of new things, including duplicated/empty chapters especially in the Pharo tools section. What about a bit of wiki gardening in the next days? > > http://book.pharo-project.org/book/table-of-contents > > -- > Simon Denier > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > -- Simon Denier

May 24, 2011

Re: [Pharo-users] Pharo using old release of Announcements?

by StÃ©phane Ducasse

+ 1 We should improve the base system. So if you have suggestion or needs please let us know. > > implements Object>>announce: , meaning that classes that want to >> âannounceâ , can simply reimplement #subscriptionRegistryOrNil , while >> in Pharo you need to inherit from Annoucer or reimplement all its >> methods. >> >> Does anyone know why there are differences between the two dialects? >> Is Pharo not keept up to date in this area? >> > > It was a conscious choice. Initially, announcements which were added > to pharo has very > compact implementation, with minimal features available. > It was inspired by Announcements from VisualWorks, but implemented from scratch > based only on publicly available description. > I guess it was done specifically to avoid potential problems with licensing. > Lukas could say more about it, since it is he, who did an initial > implementation , if i'm not mistaken. > > If you think there is a missing functionality, which could be useful > for general use, feel free to > propose the changes (but please do that in pharo-dev list), so we will > discuss it and consider for > inclusion in next Pharo release. > >> Kind regards >> Runar >> >> > > -- > Best regards, > Igor Stasenko AKA sig. >

May 24, 2011