September 2015 - Pharo-users

Re: [Pharo-users] [Moose-dev] Pillar 2.0.0: Introduction of PetitPillar

by Damien Cassou

Alexandre Bergel <alexandre.bergel(a)me.com> writes: > I use Pillar for AgileVisualization. One problem I have is that the > book contains many code snippets. How can I run all the code snippet > in order to spot error? Is there an easy way for that? something like https://github.com/pillar-markup/pillar/issues/71 ? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 14, 2015

[Survey] QualityAssistant experience mini-survey

by Yuriy Tymchuk

Dear Pharoers, I kindly ask you to participate in the QualityAssistant mini-survey: http://rio.inf.usi.ch/survey/index.php/818331 <http://rio.inf.usi.ch/survey/index.php/818331>. It will take only a few minutes of your time (or less), and will give us a better understanding of how QualityAssistant is currently used and how to improve it. Cheers! Yuriy

Sept. 14, 2015

Re: [Pharo-users] Pillar 1.1.0 released

by Johan Brichau

Hi Cyril, You are right. Itâs better to just fix the version of Pillar for Pier and that works just fine for me now. We will see what happens later if someone has the time to look at Pier. cheers Johan > On 13 Sep 2015, at 12:22, Ferlicot Delbecque Cyril <c.ferlicot-delbecque(a)etudiant.univ-lille1.fr> wrote: > > Le 13/09/2015 10:28, Johan Brichau a Ã©crit : >> Hi, >> >> I just noticed that in the most recent version of Pillar, the instvar #embedded was removed from PRReference >> This breaks Pierâ¦ though right before this change I could make Pier3 work with Pillar just fine. >> >> The embedded var is used to specify that component references are to be embedded in the page. There are more components than Figures in Pier. >> > > Hi Johan, > > We removed that because since Figures are not link anymore we do not > need it. If the reference is a link, it is not embedded, else it is. We > plan latter to have more embedded item than Figures, maybe we can just > and a class between Reference and Figure (PREmbeddedReferences). > With that we do not need the ivar. > > But since Pier3 doesn't evolve anymore I proposed to someone to freeze > the version of Pillar needed for the stable version of Pier3. But I > didn't get an answer. > > -- > Cyril > >> I am just trying to use and work with Pier3 for Seaside book and website, so it would be great if you can consider adding the embedded variable again. >> >> thanks guys! >> Johan >> >> ps: email me directly, since I might miss replies via the mailinglist. >> >> > >

Sept. 14, 2015

Re: [Pharo-users] Using Plan Board to actually planing an event at our local hackerspace

by Stephan Eggermont

On 13-09-15 22:59, Offray Vladimir Luna CÃ¡rdenas wrote: > - Json exportation to import the plan info in our website (powered by web2py: > http://web2py.com ), so this is the most important part > - SVG (I think this is supported right now). The SVG output is not in the PlanBoard example but should be not a problem to retrofit. Generation of json is even simpler. > 1. How I create an instance of a plan board instead of a new class side example? In the PlanBoard example there is no separation between model and view. It is directly coded in the morphs. That is something that doesn't scale, and it is something we know how to fix once it becomes a problem. While prototyping, you probably don't want the separation between model and view yet, as that makes the prototype less direct. > 2. In the instance I would like to send the message "columns" and I imagine I > will get all column data, including the "position" which is the start and end > time of each session/event on each day. Am I right? Yes. Columns are morphs themselves and the submorphs are the sessions. Position in the column determines starting time, the event morphs contain the duration. You at least want an accessor for startingTime that calculates it from the position. In your application you probably want to revisit the timeline drawing code in the column to make it independent of column size. There are hardcoded values that should depend on column size and grid resolution. If you only have a few timeslots, you might want to add a mouseMove: handler in the column that checks on isDragging, and moves the dragged event to the closest slot. Also you probably want to be able to resize the planboard. In the mindmap example you'll find how to load and save to fuel Stephan

Sept. 13, 2015

Using Plan Board to actually planing an event at our local hackerspace

by Offray Vladimir Luna CÃ¡rdenas

Hi, I'm living more and more inside Pharo, and as an experiment I would like to use plan board to plan an event. For that my idea is to build the event in plan board and export it in several formats: - Json exportation to import the plan info in our website (powered by web2py: http://web2py.com ), so this is the most important part - SVG (I think this is supported right now). I tried to create new instance of the plan board but I'm missing something from the syntax on how to proceed. So I started to modify exampleFour and create my own exampleDataweek (the event is called data week, look at [2] for details, about the previous version) and you now I can get something like this: [2] http://mutabit.com/dataweek/ So I would like to extend Stephan's example for Json exporting. Here are some questions: 1. How I create an instance of a plan board instead of a new class side example? 2. In the instance I would like to send the message "columns" and I imagine I will get all column data, including the "position" which is the start and end time of each session/event on each day. Am I right? 3. Once I have this, I imagine will be possible to use Ston to export this objects info to Json and teach my website how to read this information and show it properly in our activities calendar. Any pointer on how to start will be appreciated. Cheers, Offray

Sept. 13, 2015

Re: [Pharo-users] Pillar 1.1.0 released

by Damien Cassou

Hi Johan, Ferlicot Delbecque Cyril <c.ferlicot-delbecque(a)etudiant.univ-lille1.fr> writes: > Le 13/09/2015 10:28, Johan Brichau a Ã©crit : >> I just noticed that in the most recent version of Pillar, the instvar >> #embedded was removed from PRReference This breaks Pierâ¦ though right >> before this change I could make Pier3 work with Pillar just fine. >> >> The embedded var is used to specify that component references are to >> be embedded in the page. There are more components than Figures in >> Pier. >> > We removed that because since Figures are not link anymore we do not > need it. If the reference is a link, it is not embedded, else it is. > We plan latter to have more embedded item than Figures, maybe we can > just and a class between Reference and Figure (PREmbeddedReferences). > With that we do not need the ivar. > > But since Pier3 doesn't evolve anymore I proposed to someone to freeze > the version of Pillar needed for the stable version of Pier3. But I > didn't get an answer. I totally agree with Cyril. We can't limit the development of a dependency forever because a dependent has more or less stopped evolving. Before, a figure was a link with embedded = true. This was silly because each visitor had to do something specific for figures (e.g., in html you want a <img>, in latex you want \includegraphics). This is totally different from what is expected of a link. Now a figure is not a link anymore, it is a reference. There can be multiple kinds of references but the embedded parameter what not of any use for Pillar anymore. So we decided to remove it, knowing that Pier used it to embed Pier components. So, Pier users have 2 solutions now: - either adapt Pier's configuration so that it uses an old version of Pillar; - or adapt Pier's code to rely on the new Pillar. This might require some adaptations to Pillar which we can discuss. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 13, 2015

Fwd: Re: Pillar 1.1.0 released

by Ferlicot D. Cyril

Le 13/09/2015 10:28, Johan Brichau a Ã©crit : > Hi, > > I just noticed that in the most recent version of Pillar, the instvar #embedded was removed from PRReference > This breaks Pierâ¦ though right before this change I could make Pier3 work with Pillar just fine. > > The embedded var is used to specify that component references are to be embedded in the page. There are more components than Figures in Pier. > Hi Johan, We removed that because since Figures are not link anymore we do not need it. If the reference is a link, it is not embedded, else it is. We plan latter to have more embedded item than Figures, maybe we can just and a class between Reference and Figure (PREmbeddedReferences). With that we do not need the ivar. But since Pier3 doesn't evolve anymore I proposed to someone to freeze the version of Pillar needed for the stable version of Pier3. But I didn't get an answer. -- Cyril > I am just trying to use and work with Pier3 for Seaside book and website, so it would be great if you can consider adding the embedded variable again. > > thanks guys! > Johan > > ps: email me directly, since I might miss replies via the mailinglist. > >

Sept. 13, 2015

Re: [Pharo-users] Modify AST to send a message on Character nodes

by Marcus Denker

> > Cool. Intriguing. > > I'm sure I can use it to: > - patch problematic code on the fly without registering an override > - change the semantics of some smalltalk statement (so that a := becomes self a: or anything else) > Yes, it is for âevilâ experiments that can not be done else (short of changing the compiler itself). e.g. last week for an experiment, I wanted a form of âsuperâ where it is not âself, but start lookup in superclassâ, but instead âthis object, do a send to it but start lookup in the superclassâ. There are no messages called #super in the image, so you can so that by transforming all myObject super doSomething into myObject perform: #doSomething withArguments: #() inSuperclass: myObject class superclass. The needed Opal plugin has this #transform method: transform | superSends new | superSends := ast sendNodes select: [ :each | each selector = #super ]. superSends do: [ :spnode | new := RBMessageNode receiver: spnode receiver copy selector: #perform:withArguments:inSuperclass: arguments: {RBLiteralNode value: spnode parent selector copy . RBArrayNode statements: spnode parent arguments . RBMessageNode receiver: (RBMessageNode receiver: spnode receiver copy selector: #class) selector: #superclass}. spnode parent replaceWith: new ]. ^ast > Would it be possible to couple it with Clement work to have some ability to pre-compile some code in specific classes (strength reduction, once literals) where we know that this is valuable? > Good questionâ¦. > It would also be nice to have a way not to write bytecode by hand, like, say, in the slots example of a few days back. > Yes, the byte code writing for Slots is just a solution that works *today*. With a runtime optimizer you could instead always generate the reflective slow version and let Sista optimise it. > Oh, ok, for the literal stuff, I think I know how to do it: > > In a method: > - replace target expression with symbol literal. > - evaluate target expression in isolation, store value. > - compile method with symbol literal. > - in compiled method, replace symbol literal with value stored above. > > Would that work? > Hmmâ¦ messages to known objects without side effect could be evaluated by the compiler. What makes it hard ist mostly debugging: mapping the generated code back to the original sourceâ¦. Marcus

Sept. 13, 2015

Re: [Pharo-users] Something like pipeup.io?

by HernÃ¡n Morales Durand

2015-09-12 3:44 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > On 12 Sep 2015, at 01:43, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > > > > Hi, > > > > We are starting a project here which involves executing scripts in a > (remote) CentOS HPC environment I have built. The stack is going to be > Pharo + Seaside + QCMagritte + Voyage. > > > > The bash scripts could take a long time to finish, besides they are in > beta state so I want to monitor a RT log of what's happening. Like this > solution: > > > > http://pipeup.io/ > > > > Do we have something like that in Pharo? > > The key concept is quite easy: here is a live demo > > http://websocket.stfx.eu:9999/ws-status-client > > More live demos > > http://websocket.stfx.eu:9999/ws-demo > > Docs > > https://github.com/svenvc/docs/blob/master/zinc/zinc-websockets-paper.md > > Very nice! Thank you. HernÃ¡n > > I read Zinc/Swazoo supports web sockets but I would like to read > experiences or recommendations (links?). > > > > Cheers, > > > > HernÃ¡n > > > > >

Sept. 13, 2015

Re: [Pharo-users] Modify AST to send a message on Character nodes

by Thierry Goubier

Le 13/09/2015 08:56, Marcus Denker a Ã©crit : > >> On 12 Sep 2015, at 19:23, Peter UhnÃ¡k <i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com>> wrote: >> >> | rewriter | >> rewriter := RBParseTreeRewriter new >> replace: ' `#aLiteral `{:node | node value isCharacter}' >> with: '`#aLiteral aMessage'; yourself. >> rewriter executeTree: (RBParser parseExpression: 'Array with: $a >> asciiValue with: $b with: #c with: d'). >> rewriter tree formattedCode >> >> >> This is cool! And so simple! >> > > This can be combined with the compiler transform plugins of Opal: > > -> make subclass of OCCompilerASTPlugin > -> put your code in a method called #transform > > now when you override #compiler on the class side of a class like this: > > compiler > ^super compiler addPlugin: ASTPluginMeaningOfLife. > > the plugin will be active for the hierarchy, which means that all code > compiled will be transformed. > > There is a simple example ASTPluginMeaningOfLife in the image. Cool. Intriguing. I'm sure I can use it to: - patch problematic code on the fly without registering an override - change the semantics of some smalltalk statement (so that a := becomes self a: or anything else) Would it be possible to couple it with Clement work to have some ability to pre-compile some code in specific classes (strength reduction, once literals) where we know that this is valuable? It would also be nice to have a way not to write bytecode by hand, like, say, in the slots example of a few days back. Oh, ok, for the literal stuff, I think I know how to do it: In a method: - replace target expression with symbol literal. - evaluate target expression in isolation, store value. - compile method with symbol literal. - in compiled method, replace symbol literal with value stored above. Would that work? Thierry > > Marcus >

Sept. 13, 2015