October 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] CodeGenerator, your opinions?

by Peter Uhnak

On Tue, Oct 18, 2016 at 02:24:28AM -0300, HernÃ¡n Morales Durand wrote: > - A Spec UI generator. Oh, and Stephan did CRUD(e) Spec generator http://forum.world.st/ANN-SpecGenerator-easy-CRUD-applications-with-Spec-td… Peter

Oct. 18, 2016

Re: [Pharo-users] CodeGenerator, your opinions?

by Peter Uhnak

Hi Hernan, I wrote some time ago two basic code generators (both in Pharo) from UML-ified FAMIX for a particular user (so there are some domain-specific patterns), one for Pharo syntax ( https://github.com/OpenPonk/class-editor/blob/master/docs/code-generation/u… ) and one for VW syntax ( https://github.com/OpenPonk/class-editor/blob/master/docs/vw-code-generatio… ) (the code is here https://github.com/OpenPonk/class-editor/tree/master/repository/DynaCASE-Ge… and here https://github.com/OpenPonk/class-editor/tree/master/repository/UML-CodeGen… ) The most pain I had was with expressing templateable code to which I could just plug specific data, I wanted to look at QVT but didn't have the time yet. But it would be interesting to see if your generator could address such issues; plus soon I want to iterate on my generators to have more live interaction (so the code is generated on the fly as the model is created, although I am using Pharo Refactoring engine for now, which is also quite powerful.) Addionally, Lionel (in cc) is working on some meta system generating classes with magritte descriptions. So it would be cool if we could have some really cool generator that could do many cool things. :) Peter On Tue, Oct 18, 2016 at 02:24:28AM -0300, HernÃ¡n Morales Durand wrote: > Hi guys, > > I am writing a code generator, doing a few iterations right now. > I want your opinion, which most useful thing would you like to be generated > automatically? It could be a pattern, an idiom, another language... > > For example my own wish (roadmap) list: > > - A "settings framework" settings class generator. > - A state machine generator (based in the excellent paper of Trevor P. > Hopkins) > - A Spec UI generator. > > Let me know your thoughts. > > Cheers, > > HernÃ¡n

Oct. 18, 2016

Re: Spec: scaling imageModels

by matteob8

Hi Stef, I think that an automatic scaled behaviour is very useful for ImageModel, especially if you need to generate list of images, that automatically adapts to their container (i.e. Thumbnails). Playing with AlpahImageMorph I found that the desired behaviour can be obtained setting the "layout" state to the "#scaledAspect" symbol. So I've added the "ImageModel>>switchScaledLayout" method, that will simply call its MorphicAdapter, through the command "self changed: #switchScaledLayout with: {}". Then I've created the "MorphicImageAdapter>>switchScaledLayout" method, that switchs among the "#center" and "#scaledAspect" morph layouts (note: "#center" is the default for the Spec's "MorpdicImageAdapter"). Below the code the code I used: MorphicImageAdapter>>switchScaledLayout "Switch between scaled and fixed representation" self widgetDo: [ :w | | oldLayout | oldLayout := w layout. oldLayout = #scaledAspect ifTrue: [ w layout: #center ] ifFalse: [ w layout: #scaledAspect ] ]. Please let me know if you have any advice, Thanks, Matteo -- View this message in context: http://forum.world.st/Spec-scaling-imageModels-tp4918440p4919199.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Oct. 18, 2016

Nao robot with Pharo and LRP

by Miguel Campusano

Hello, I've been working on an API for the Nao Robot [1] in Pharo. You can find an early demo of how it works in Pharo: https://www.youtube.com/watch?v=z8jopUfLWtQ Moreover, I built a communication bridge between the Nao and LRP [2]. LRP is a live programming language for robotic behaviors. You can see a working demo of the nao moving via LRP here: https://www.youtube.com/watch?v=q1jGDtaW41U I want to emphasize how easy and fun can be to program a robot with a live environment. Looking at the robot and see how immediately changes its behavior whenever you send a command, that is cool! You can find the API here (I have to write the documentation on how to use it): http://www.smalltalkhub.com/#!/~mcamp/NaoSocket This is a work in progress. The Nao has several features that I'm planning to incorporate in the API when they are needed. To make this work I use TCP sockets to communicate with the robot. For the Nao, there is a documentation on how the robot communicates via binary packages, but the documentation lacks a lot of information that I managed to figure it out by reading the binary information (thanks gtInspector for that) and understanding how the robot works. [1] https://www.ald.softbankrobotics.com/en/cool-robots/nao [2] pleiad.cl/lrp

Oct. 18, 2016

Re: [Pharo-users] [Seaside] Seaside can not be used with Pharo 60261

by Johan Brichau

I only received a config for Grease :) In my haste, I did not check you need Seaside :) Right now, Iâm a bit too busy so until someone can provide a working config, it will have to wait. cheers Johan > On 18 Oct 2016, at 10:19, Norbert Hartl <norbert(a)hartl.name> wrote: > > You uploaded ConfigurationOfGrease but not Seaside. Mistake? > > Norbert > >> Am 18.10.2016 um 10:11 schrieb Johan Brichau <johan(a)inceptive.be>: >> >> I uploaded the changes by Christophe. If it does not work, let me know. I did not try. >> >> cheers >> Johan >> >> ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5 >> >>> On 18 Oct 2016, at 10:00, Johan Brichau <johan(a)inceptive.be> wrote: >>> >>> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6. >>> >>> I will upload them as soon as I receive them >>> >>> Johan >>> >>>> On 17 Oct 2016, at 21:04, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> this is a question more appropriate for Seaside list :) >>>> >>>>> On 17 Oct 2016, at 20:07, Pierre CHANSON <chans.pierre(a)gmail.com> wrote: >>>>> >>>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.xâ have been removed and Seaside does not have configuration for pharo6. >>>>> >>>>> Is there a plan to update the configuration of Seaside ? >>>>> >>>>> Thanks ! >>>>> >>>>> Pierre and Norbert >>>> >>>> _______________________________________________ >>>> seaside mailing list >>>> seaside(a)lists.squeakfoundation.org >>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >> >> > >

Oct. 18, 2016

Re: [Pharo-users] CodeGenerator, your opinions?

by Thierry Goubier

Hi Otto, for things like that, I would consider looking into the SmaCC visitor automatic generation. From an grammar, SmaCC creates the class, respecting an eventual inheritance constraint you specify, adds the instance variables, and generates the visitor (and an equality test too). Regarding state machines generation, what class of automatons are you looking at? Because I'm looking at automatons generation by reusing SmaCC (for a tentative hardware architecture subject). Regards, Thierry Le 18/10/2016 Ã 10:01, Otto Behrens a Ã©crit : > +1 for the visitor. What would be nice is to generate methods in the > form #visit<Class Name>: for all classes in a given hierarchy (eg > Magritte's MAVisitor). The default implementation of such a method > would be to call #visit<My Super Class name>: > > We have been using state machines for a long time and have built > generators for it (on a previous project, for which I do not have the > code). I still think that is a useful idea. It is difficult for the > code generator to maintain changes in the generated code with changes > in the "spec". Will you then define a DSL for the state machine? > > On Tue, Oct 18, 2016 at 9:29 AM, Julien Delplanque <julien(a)tamere.eu> wrote: >> Hello, >> >> A generator for the visitor design pattern: >> - Generate methods in visited objects: VisitedObject>>#accept: (with the >> selector name configurable) >> - Generate empty methods (or methods with a "self subclassResponsability" if >> an abstract visitor is generated) >> called in #accept: methods of VisitedObjects in the Visitor i.e >> Visitor>>#acceptVisitedObject: (with the selector >> name configurable again). >> >> Each time this design pattern has to be used, it is annoying to write by >> hand all these methods. >> >> Regards, >> >> Julien >> >> >> On 18/10/16 07:24, HernÃ¡n Morales Durand wrote: >>> >>> Hi guys, >>> >>> I am writing a code generator, doing a few iterations right now. >>> I want your opinion, which most useful thing would you like to be >>> generated >>> automatically? It could be a pattern, an idiom, another language... >>> >>> For example my own wish (roadmap) list: >>> >>> - A "settings framework" settings class generator. >>> - A state machine generator (based in the excellent paper of Trevor P. >>> Hopkins) >>> - A Spec UI generator. >>> >>> Let me know your thoughts. >>> >>> Cheers, >>> >>> HernÃ¡n >>> >> >> > >

Oct. 18, 2016

Re: [Pharo-users] [Seaside] Seaside can not be used with Pharo 60261

by Norbert Hartl

You uploaded ConfigurationOfGrease but not Seaside. Mistake? Norbert > Am 18.10.2016 um 10:11 schrieb Johan Brichau <johan(a)inceptive.be>: > > I uploaded the changes by Christophe. If it does not work, let me know. I did not try. > > cheers > Johan > > ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5 > >> On 18 Oct 2016, at 10:00, Johan Brichau <johan(a)inceptive.be> wrote: >> >> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6. >> >> I will upload them as soon as I receive them >> >> Johan >> >>> On 17 Oct 2016, at 21:04, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> this is a question more appropriate for Seaside list :) >>> >>>> On 17 Oct 2016, at 20:07, Pierre CHANSON <chans.pierre(a)gmail.com> wrote: >>>> >>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.xâ have been removed and Seaside does not have configuration for pharo6. >>>> >>>> Is there a plan to update the configuration of Seaside ? >>>> >>>> Thanks ! >>>> >>>> Pierre and Norbert >>> >>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > >

Oct. 18, 2016

Re: [Pharo-users] [Seaside] Seaside can not be used with Pharo 60261

by Norbert Hartl

> Am 18.10.2016 um 10:11 schrieb Johan Brichau <johan(a)inceptive.be>: > > I uploaded the changes by Christophe. If it does not work, let me know. I did not try. > > cheers > Johan > > ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5 It worked until 60260 pretty fine. So this seems to be the right move until we need a diversion. thanks, Norbert > >> On 18 Oct 2016, at 10:00, Johan Brichau <johan(a)inceptive.be> wrote: >> >> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6. >> >> I will upload them as soon as I receive them >> >> Johan >> >>> On 17 Oct 2016, at 21:04, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> this is a question more appropriate for Seaside list :) >>> >>>> On 17 Oct 2016, at 20:07, Pierre CHANSON <chans.pierre(a)gmail.com> wrote: >>>> >>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.xâ have been removed and Seaside does not have configuration for pharo6. >>>> >>>> Is there a plan to update the configuration of Seaside ? >>>> >>>> Thanks ! >>>> >>>> Pierre and Norbert >>> >>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > >

Oct. 18, 2016

Re: [Pharo-users] [Seaside] Seaside can not be used with Pharo 60261

by Johan Brichau

I uploaded the changes by Christophe. If it does not work, let me know. I did not try. cheers Johan ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5 > On 18 Oct 2016, at 10:00, Johan Brichau <johan(a)inceptive.be> wrote: > > Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6. > > I will upload them as soon as I receive them > > Johan > >> On 17 Oct 2016, at 21:04, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> this is a question more appropriate for Seaside list :) >> >>> On 17 Oct 2016, at 20:07, Pierre CHANSON <chans.pierre(a)gmail.com> wrote: >>> >>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.xâ have been removed and Seaside does not have configuration for pharo6. >>> >>> Is there a plan to update the configuration of Seaside ? >>> >>> Thanks ! >>> >>> Pierre and Norbert >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

Oct. 18, 2016

Re: [Pharo-users] CodeGenerator, your opinions?

by Otto Behrens

+1 for the visitor. What would be nice is to generate methods in the form #visit<Class Name>: for all classes in a given hierarchy (eg Magritte's MAVisitor). The default implementation of such a method would be to call #visit<My Super Class name>: We have been using state machines for a long time and have built generators for it (on a previous project, for which I do not have the code). I still think that is a useful idea. It is difficult for the code generator to maintain changes in the generated code with changes in the "spec". Will you then define a DSL for the state machine? On Tue, Oct 18, 2016 at 9:29 AM, Julien Delplanque <julien(a)tamere.eu> wrote: > Hello, > > A generator for the visitor design pattern: > - Generate methods in visited objects: VisitedObject>>#accept: (with the > selector name configurable) > - Generate empty methods (or methods with a "self subclassResponsability" if > an abstract visitor is generated) > called in #accept: methods of VisitedObjects in the Visitor i.e > Visitor>>#acceptVisitedObject: (with the selector > name configurable again). > > Each time this design pattern has to be used, it is annoying to write by > hand all these methods. > > Regards, > > Julien > > > On 18/10/16 07:24, HernÃ¡n Morales Durand wrote: >> >> Hi guys, >> >> I am writing a code generator, doing a few iterations right now. >> I want your opinion, which most useful thing would you like to be >> generated >> automatically? It could be a pattern, an idiom, another language... >> >> For example my own wish (roadmap) list: >> >> - A "settings framework" settings class generator. >> - A state machine generator (based in the excellent paper of Trevor P. >> Hopkins) >> - A Spec UI generator. >> >> Let me know your thoughts. >> >> Cheers, >> >> HernÃ¡n >> > >

Oct. 18, 2016