- Pharo-users - lists.pharo.org

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

by Norbert Hartl

Thanks, that worked. Feels really strange encountering this. So one cannot use the commandline handler for loading a configuration anymore. Sad! The same way sad as you cannot use versionner anymore when you start to use BaselineOf instead of ConfigurationOf. This is not a complaint because I can understand why this happens. It is just that we need more energy to solve all this than we have. Sad! Norbert > Am 18.10.2016 um 17:20 schrieb Johan Brichau <johan(a)inceptive.be>: > > >> On 18 Oct 2016, at 16:36, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >> >> (ConfigurationOfAster project version: #development) load > > There are issues with this âoldâ way of Metacello loading. Can you try: > > Metacello new > configuration:âAsterâ; > version: #development; > load. > > (Maybe you need to add the repo to, donât know). > > Cheers > Johan

Oct. 18, 2016

Re: [Pharo-users] Nao robot with Pharo and LRP

by Johan Fabry

Excellent work ! :-) -- Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org <http://emailcharter.org/> . Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > On 18 Oct 2016, at 06:09, Miguel Campusano <mcampusa(a)dcc.uchile.cl> wrote: > > 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 <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 <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 <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 <https://www.ald.softbankrobotics.com/en/cool-robots/nao> > [2] pleiad.cl/lrp <http://pleiad.cl/lrp>

Oct. 18, 2016

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

by Johan Brichau

> On 18 Oct 2016, at 16:36, Norbert Hartl <norbert(a)hartl.name> wrote: > > (ConfigurationOfAster project version: #development) load There are issues with this âoldâ way of Metacello loading. Can you try: Metacello new configuration:âAsterâ; version: #development; load. (Maybe you need to add the repo to, donât know). Cheers Johan

Oct. 18, 2016

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

by HernÃ¡n Morales Durand

Hi Dimitris, That would be certainly nice. C++ is hard, but if one start with a basic instantiation template it could be easier to move forward to more complex tasks like mapping data structures to STL, their containers and iterators. And I think it would attract C++ developers to Smalltalk. Cheers, HernÃ¡n 2016-10-18 4:54 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > There is the CCodeGenerator , which is basically Slang, Smalltalk that is > turned into basic C. I would like to expand it to generate C++ at some > point for converting pharo code to C++ code that I will be able to add to > Unreal. Though its a very low priority project for me. > > http://smalltalkhub.com/#!/~PavelKrivanek/CCodeGenerator > > Personally I am against generalized solutions because they tend to be bad > for specialized cases , on the other hand I welcome any code that I can use > as inspiration for my own code generator. > > On Tue, Oct 18, 2016 at 8:25 AM HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> 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

I have a ConfigurationOfAster with a baseline baseline01: spec <version: '0.1-baseline'> spec for: #'common' do: [ spec blessing: #'baseline'. spec repository: 'filetree://repository/'. spec project: 'RFB' with: [ spec className: #ConfigurationOfRFB; versionString: '0.64'; repository: 'http://smalltalkhub.com/mc/PharoExtras/RFB/main/' ]; project: 'Seaside3' with: [ spec className: #ConfigurationOfSeaside3; versionString: #'release3.2'; repository: 'filetree://repository/' ]. spec package: #'Aster-Core'; package: #'Aster-Seaside' with: [ spec requires: #(#'Aster-Core' 'Seaside3' 'RFB' ). ]. ]. and I load (ConfigurationOfAster project version: #development) load Norbert > Am 18.10.2016 um 16:32 schrieb Johan Brichau <johan(a)inceptive.be>: > > Can you post the snippet how you load it? > >> On 18 Oct 2016, at 16:21, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> I tried to but I failed. It is very strange indeed. I added the platform attribute #'pharo6.x' to every location where there is a #'pharo5.x' attribute (see attached configuration). >> When loading metacello looks into older versions as well (in this case version 3.1.6). There the platform attribute does not exist and it seems to fallback on a configuration for #pharo where a package Seaside-Pharo-Development is referenced. While trying to find the definition of that package it fails. >> >> Does somebody know why it behaves that weird? Or even better know a solution :) >> >> thanks, >> >> Norbert >> >> <ConfigurationOfSeaside3-NorbertHartl.321.mcz> >> >>> Am 18.10.2016 um 10:37 schrieb Johan Brichau <johan(a)inceptive.be>: >>> >>> 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] [Seaside] Seaside can not be used with Pharo 60261

by Johan Brichau

Can you post the snippet how you load it? > On 18 Oct 2016, at 16:21, Norbert Hartl <norbert(a)hartl.name> wrote: > > I tried to but I failed. It is very strange indeed. I added the platform attribute #'pharo6.x' to every location where there is a #'pharo5.x' attribute (see attached configuration). > When loading metacello looks into older versions as well (in this case version 3.1.6). There the platform attribute does not exist and it seems to fallback on a configuration for #pharo where a package Seaside-Pharo-Development is referenced. While trying to find the definition of that package it fails. > > Does somebody know why it behaves that weird? Or even better know a solution :) > > thanks, > > Norbert > > <ConfigurationOfSeaside3-NorbertHartl.321.mcz> > >> Am 18.10.2016 um 10:37 schrieb Johan Brichau <johan(a)inceptive.be>: >> >> 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] [Seaside] Seaside can not be used with Pharo 60261

by Norbert Hartl

I tried to but I failed. It is very strange indeed. I added the platform attribute #'pharo6.x' to every location where there is a #'pharo5.x' attribute (see attached configuration). When loading metacello looks into older versions as well (in this case version 3.1.6). There the platform attribute does not exist and it seems to fallback on a configuration for #pharo where a package Seaside-Pharo-Development is referenced. While trying to find the definition of that package it fails. Does somebody know why it behaves that weird? Or even better know a solution :) thanks, Norbert > Am 18.10.2016 um 10:37 schrieb Johan Brichau <johan(a)inceptive.be>: > > 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] [Seaside] Seaside can not be used with Pharo 60261

by Cyril Ferlicot D.

Le 18/10/2016 Ã 15:41, Cyril Ferlicot D. a Ã©crit : > Hi! > > I could load Seaside but when I start the adaptor and go to > localhost:8080 I get an error[1] `receiver of #from:to: is nil`. > There is some error on Jenkin's logs that where not here before[2]. > > > [1] http://puu.sh/rN9fV/780adbcfe0.png > [2] http://puu.sh/rN9rb/dd9de6776a.png > I think that this mcz should correct the problem but I don't have the rights on Seaside repo. Can someone add me to the Seaside Team or copy the mcz? I just added a 'pharo6.x' in the configuration where there is a 'pharo5.x' so it should be a safe change. -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Oct. 18, 2016

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

by Otto Behrens

> 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). Nice. Will have a look. Thanks. > 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). We have some domain specific objects, for example investment instructions, that go through some domain specific state transitions. It is not enormous, but a state transition model helps to understand what valid transitions there are. As a simplistic example, when we receive an investment instruction, one user "submits" the instruction, another "authorises". From there it moves into a processing state and then complete when the investment is placed. What will be nice is to set up guards on transitions, entry / exit actions and more nice things that can be done with a state machine. Reading the state machine then gives a nice overview of the logic. What will be nice is to see that in the form of a graph, with all the annotations. We do not currently use complexities like concurrency and nesting, but have seen that working before. Does this answer what you're asking? > > 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] looking for a tutorial on sounds in Pharo

by Grigory Hatsevich

Iâm interested in using a computer as a musical instrument and a XXI-century tool to learn how to play and compose music. First, Iâd like to implement a Janko keyboard emulator in Pharo (like this one http://monxmood.free.fr/roche/roche.html, but with various customizations) â it is an alternative piano keyboard layout that is 12 times easier to learn to play because of its regular structure â unlike traditional piano keyboard layout. Demonstration of a real Janko piano: https://www.youtube.com/watch?v=cK4REjqGc9w&t=4m Also I see playing with note sequences as a good way to learn programming (for those who love music, like me). On Mon, 17 Oct 2016 02:21:57 +0700, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > I have used the Sound library for my project ChronosManager to play back > an alarm sound, its an easy to use library but >quite powerful. Last > time I checked could not get it working on Linux but it worked like a > charm on MacOS and I think it >worked well also on windows. > Is there something specific you are interested for ? > > On Sun, Oct 16, 2016 at 2:16 PM Grigory Hatsevich > <g.hatsevich(a)gmail.com> wrote: >> Hi! I'm looking for a tutorial about sound generation in Pharo. I've >> found >> "PharoSoundTutorial" (https://github.com/xmessner/PharoSoundTutorial) >> but >> it is in French. Is there an English version of this tutorial or some >> other English text about sounds in Pharo?

Oct. 18, 2016