- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Improving generate accessors for refactoring browser

by Lukas Renggli

How you derive the type? >From the method name? I think only very few accessors/inst-vars are named after the type. Also note that you can edit the type directly in the changes browser before you install it, that's what I typically do. Lukas 2010/9/13 Mariano Martinez Peck <marianopeck(a)gmail.com>: > i would like that too > > On Sep 12, 2010 7:27 PM, "Bart Gauquie" <bart.gauquie(a)gmail.com> wrote: > > Dear list, > > I've noticed that when I'm using the generate accessors refactoring, I'm > always adapting the generated code for the mutator: > number: anObject > Â Â number := anObject > to: > number: aNumber > Â Â number := aNumber > So I've adapted the refactoring code a bit so that it automatically > generates this correctly. Anybody also thinks this is useful? If so, I will > create a bug/improvement and a slice for it. > Kind regards, > > Bart > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

Sept. 13, 2010

Re: [Pharo-project] Compiler throws error in Gemstone, not in Pharo

by StÃ©phane Ducasse

Yes but what is wrong on gemstone. Stef > Dear list, > > while testing between Pharo and Gemstone I've noticed that Pharo allows following code, while Gemstone does not. > > renderSelectorAndReturnBrushForSelector: aSelector. > ^canvas textInput > id: (self idForSelector: aSelector); > value: (self inputValueForSelector: aSelector); > script: (canvas jQuery new datepicker); > yourself > > The error is that in the message definition: renderSelectorAndReturnBrushForSelector: aSelector. there is a dot on the end. > > This seems like an error in the Pharo compiler ? or not? > > Kind Regards, > > Bart > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 13, 2010

Re: [Pharo-project] Improving generate accessors for refactoring browser

by Mariano Martinez Peck

i would like that too On Sep 12, 2010 7:27 PM, "Bart Gauquie" <bart.gauquie(a)gmail.com> wrote: Dear list, I've noticed that when I'm using the generate accessors refactoring, I'm always adapting the generated code for the mutator: number: anObject number := anObject to: number: aNumber number := aNumber So I've adapted the refactoring code a bit so that it automatically generates this correctly. Anybody also thinks this is useful? If so, I will create a bug/improvement and a slice for it. Kind regards, Bart _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 13, 2010

Re: [Pharo-project] Compiler throws error in Gemstone, not in Pharo

by Damien Pollet

2010/9/13 Bart Gauquie <bart.gauquie(a)gmail.com>: > The error is that in the message definition: > renderSelectorAndReturnBrushForSelector: aSelector. there is a dot on the > end. > > This seems like an error in the Pharo compiler ? or not? Actually Johan Brichau just mentioned this during his talk this morning. Gemstone's compiler is stricter than Pharo's. It's not really a bug that the parser in Pharo is more persmissive, but it's an inconvenience indeed. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Sept. 13, 2010

[Pharo-project] Compiler throws error in Gemstone, not in Pharo

by Bart Gauquie

Dear list, while testing between Pharo and Gemstone I've noticed that Pharo allows following code, while Gemstone does not. renderSelectorAndReturnBrushForSelector: aSelector. ^canvas textInput id: (self idForSelector: aSelector); value: (self inputValueForSelector: aSelector); script: (canvas jQuery new datepicker); yourself The error is that in the message definition: renderSelectorAndReturnBrushForSelector: aSelector. there is a dot on the end. This seems like an error in the Pharo compiler ? or not? Kind Regards, Bart

Sept. 13, 2010

Re: [Pharo-project] Settings for Shout syntax highlighting

by Schwab,Wilhelm K

Dumb question/request: background colors? I like to choose something other than white to reduce contrast. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Simon Denier [Simon.Denier(a)inria.fr] Sent: Monday, September 13, 2010 5:00 AM To: Pharo Development Cc: Simon Denier Subject: [Pharo-project] Settings for Shout syntax highlighting Hi A new package Settings-Shout in the Pharo Inbox for issue 1611<http://code.google.com/p/pharo/issues/detail?id=1611> SLICE-Issue-1611-ShoutSettings-simon_denier.1 You can now set how (for example), instance variables, selector patterns, class references appears in the Shout pane. One point is that Shout comes with a list of hundred token types which can be individually customized, some of which I have no idea what they represent (externalCallTypePointerIndicator?). To keep things manageable, I defined some groups of logically related token types (like the gorup 'selector patterns' for token types patternKeyword, patternBinary, patternUnary). "Class SHGroupStyle manages settings for the Shout syntax highlighting. Token types are organized in logical groups which will share the same style. Currently, only color and emphasis can be edited through Shout settings. Text font and size are managed through the more general appearance setting. Changing a style setting on a SHGroupStyle automatically applies the style. Groups are defined in the class-side method initializeGroups. Alternatively, one can set its own style table using Shout tokens by calling #customStyleTable (see SHTextStylerST80 class>>defaultStyleTable for the format)." Help needed: 1) code review 2) review group definition, because I made some groups based partly on my intuition, partly on styling difference in the current difference: there may be a better partition of token types. 3) review description for group, setting organization... Thanks to Alain for helping with settings and especially polymorph widgets. -- Simon

Sept. 13, 2010

Re: [Pharo-project] Cecinestpasunepomme best squeaksource package name!

by Bart Gauquie

:-) thx 2010/9/13 Peter Hugosson-Miller <oldmanlink(a)gmail.com> > LOL! Nice with a little Magritte humour ;-) > > > On Mon, Sep 13, 2010 at 11:18 AM, stephane ducasse < > stephane.ducasse(a)free.fr> wrote: > >> Hi >> >> Cecinestpasunepomme best squeaksource package name! >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- imagination is more important than knowledge - Albert Einstein Logic will get you from A to B. Imagination will take you everywhere - Albert Einstein Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Albert Einstein The true sign of intelligence is not knowledge but imagination. - Albert Einstein However beautiful the strategy, you should occasionally look at the results. - Sir Winston Churchill It's not enough that we do our best; sometimes we have to do what's required. - Sir Winston Churchill

Sept. 13, 2010

[Pharo-project] Fwd: [Esug-list] Live Streaming ESUG 2010

by Noury Bouraqadi

Begin forwarded message: > From: Marcus Denker <marcus.denker(a)inria.fr> > Date: 13 septembre 2010 10:45:02 HAEC > To: ESUG Mailing list <esug-list(a)lists.esug.org> > Subject: [Esug-list] Live Streaming ESUG 2019 > > Hi, > > ESUG 2010 is streamed live: > > http://eventv.projectescitilab.eu > > Second room: http://eventv.projectescitilab.eu/page3/page3.html > > Start of talks is announced on Twitter: http://twitter.com/esugsmalltalk > > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org Noury @ ESUG 2010 - Barcelona :-) --- 18th International Smalltalk Joint Conference, September 13 -17 2010 Barcelona, Spain. http://www.esug.org/Conferences/2010

Sept. 13, 2010

Re: [Pharo-project] Settings for Shout syntax highlighting

by Lukas Renggli

Excellent, I merged the changes into the Shout package and the existing preferences it already defined (package and setting wise). http://source.lukas-renggli.ch/unsorted Name: Shout-lr.88 Author: lr Time: 13 September 2010, 11:24:32 am UUID: 0646e300-30df-4c6f-8b5b-bd9437569194 Ancestors: Shout-lr.86 - merged the changes of simon and alain Lukas On 13 September 2010 11:02, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks! > > Stef > > On Sep 13, 2010, at 11:00 AM, Simon Denier wrote: > >> Hi >> >> A new package Settings-Shout in the Pharo Inbox for issue 1611 >> >> SLICE-Issue-1611-ShoutSettings-simon_denier.1 >> >> You can now set how (for example), instance variables, selector patterns, class references appears in the Shout pane. >> One point is that Shout comes with a list of hundred token types which can be individually customized, some of which I have no idea what they represent (externalCallTypePointerIndicator?). To keep things manageable, I defined some groups of logically related token types (like the gorup 'selector patterns' for token types patternKeyword, patternBinary, patternUnary). >> >> "Class SHGroupStyle manages settings for the Shout syntax highlighting. Token types are organized in logical groups which will share the same style. Currently, only color and emphasis can be edited through Shout settings. Text font and size are managed through the more general appearance setting. Changing a style setting on a SHGroupStyle automatically applies the style. >> >> Groups are defined in the class-side method initializeGroups. Alternatively, one can set its own style table using Shout tokens by calling #customStyleTable (see SHTextStylerST80 class>>defaultStyleTable for the format)." >> >> >> Help needed: >> 1) code review >> 2) review group definition, because I made some groups based partly on my intuition, partly on styling difference in the current difference: there may be a better partition of token types. >> 3) review description for group, setting organization... >> >> >> Thanks to Alain for helping with settings and especially polymorph widgets. >> >> -- >> Â Simon >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

Sept. 13, 2010

Re: [Pharo-project] Cecinestpasunepomme best squeaksource package name!

by Peter Hugosson-Miller

LOL! Nice with a little Magritte humour ;-) On Mon, Sep 13, 2010 at 11:18 AM, stephane ducasse <stephane.ducasse(a)free.fr > wrote: > Hi > > Cecinestpasunepomme best squeaksource package name! > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 13, 2010