- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Stability of 3.0

by Goubier Thierry

That was why I asked, to see if the problem was with my config or general. It was with my stuff :( Thierry Le 20/09/2013 15:14, kilon a Ã©crit : > I dont have such problem. The problem I had was code completion having > several errors while it tried to autocomplete and once I froze pharo because > I changed a live object while the morph was displaying , that method was > somewhat recycled (HelpBrowser class) so that may have been normal. > > But no problem with red boxes from what I can see, I am on 30402. > > > > -- > View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709358.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 20, 2013

Re: [Pharo-dev] [PBE] May be we should first just change PBE in git in Latex.

by btc＠openinworld.com

Sept. 20, 2013

Re: [Pharo-dev] Dynamically adding nodes to Roassal

by roberto.minelli＠usi.ch

I started yesterday to read the chapter. I bought the book at ESUG. :D On Sep 20, 2013, at 3:13 PM, Alejandro Infante <alejandroinfante91(a)gmail.com> wrote: > Also I forgot to tell you that the new book "Deep into Pharo" has a chapter for Roassal and another for Mondrian. > > Maybe that's the best place to start from, the link of the book is http://rmod.lille.inria.fr/pbe2/. > > > 2013/9/20 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > Thanks Alejandro, > > Yes I went through the examples and I understood the difference between the examples using the builder (which are easier) and with pure Roassal, which are..let's say.. less user friendly.. > > I am trying, in pure Roassal, to do a tree map and add another node to the ROView then calling signalUpdate. No luck 'till now.. > > Cheers, > R > > On Sep 20, 2013, at 3:01 PM, Alejandro Infante <alejandroinfante91(a)gmail.com> > wrote: > > > Well, > > If you started with the Easel then you must have seen the examples. Well at first you see two boxes with examples inside (one on the top and the other below (If you dont see the second one just drag the view). > > > > The first one has a label at the top-left corner that says ROMondrianExample, and this were done using the ROMondrianViewBuilder API, and you can see that you interact mainly with the "view" variable. > > The second box is called ROExample and then you interact mainly with the "rawView" variable which is pure Roassal. > > > > The difference between them is that the ROMondrianViewBuilder is a nice and friendly API, but doing really complex stuff it's not possible. So we go one level below to pure Roassal. > > > > Here you have the Collection class hierarchy in Roassal: > > |rawView| > > rawView := ROView new. > > Collection withAllSubclasses do: [ :c | > > | el | > > el := ROBorder elementOn: c. > > el @ ROPopup. > > rawView add: el ]. > > > > "Draw edges" > > rawView addAll: (ROEdge > > buildEdgesFromElements: rawView elements > > from: [ :cls | cls superclass ] > > to: #yourself > > using: ROLine new). > > > > ROTreeLayout on: rawView elementsNotEdge edges: rawView elementsAsEdge. > > rawView open. > > > > I recommend you to see the ROExamples and if there is something that you don't know just ask to the mailing list. > > You may like to see the ROExamples>>interactions>>addingOnClick example. > > > > > > 2013/9/20 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > > Thanks Alejandro, I will try what you propose! > > > > What do you mean by > > > Another thing bothering me is that you mentioned the method #nodes, thats from the ROMondrianViewBuilder, which I think is not that friendly with dynamic stuff. > > > > How would you construct a view without using the ROMondrianViewBuilder? I am used to start as in the Roassal Easel like > > rawView := ROView new. > > view := ROMondrianViewBuilder view: rawView > > > > And then adding nodes to the view, calling view nodes: myNodes > > > > Cheers, > > R > > > > > > > > On Sep 20, 2013, at 1:49 PM, Alejandro Infante <alejandroinfante91(a)gmail.com> > > wrote: > > > > > In Roassal calling the method #signalUpdate to the view should show those new nodes. If you want to re-layout the nodes you should apply a new layout to the nodes before the #signalUpdate. > > > > > > Another pretty interesting feature is the method ROContainer>>callback: aCallback. The idea is that every time an element is added inside the container the callback is called. > > > Now how you can use this: > > > > > > element callback: (ROContainerCallbackLayout new layout: (ROGridLayout new gapSize: 2)). > > > > > > Remember that you must send signalUpdate to the view if you want to see the changes. > > > > > > Another thing bothering me is that you mentioned the method #nodes, thats from the ROMondrianViewBuilder, which I think is not that friendly with dynamic stuff. > > > It is a little bit ugly but you can always get the ROView from ROMondrianViewBuilder sending the message #view and over that do all kind of Roassal magic stuff, like adding the callback with the TreeLayout the the ROView itself. Also for adding new nodes you should add them directly to the ROView, or at least I haven't found the way to do that without having to add all the nodes again to the Builder. > > > > > > Hope that help you. > > > > > > > > > 2013/9/20 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > > > *and have the visualization re-layouted? > > > > > > On Sep 20, 2013, at 11:24 AM, "roberto.minelli(a)usi.ch" <roberto.minelli(a)usi.ch> > > > wrote: > > > > > > > Hi, > > > > > > > > I was playing around with Roassal (in particular, a tree map) and I have a question: Is there a way to dynamically adding nodes? I mean, once the view is generated to update the #nodes by adding a new node (and associations as well, i.e., edges) and have the visualization re- > > > > > > > > Thanks in advance. > > > > > > > > Roby > > > > > > > > > > > > > > > > > >

Sept. 20, 2013

Re: [Pharo-dev] Please help us by buying the book

by kilon

yeah I know, I was just joking :) StÃ©phane Ducasse wrote > the money is given to the pharo association. > > On Sep 19, 2013, at 10:36 PM, kilon < > thekilon@.co > > wrote: > >> Just ordered the book in Lulu. Please don't spend all my money on beer :D >> >> >> >> >> kilon wrote >>> >>> Damien Cassou wrote >>>> On Tue, Sep 17, 2013 at 12:22 AM, kilon < >> >>>> thekilon@.co >> >>>> > wrote: >>>>> how long for the amazon version ? I am Greek and I am not sure if the >>>>> first >>>>> choice delivers here. >>>> >>>> >>>> the amazon version is there: http://deepintopharo.com/. >>>> >>>> Still, we get more money if you go through lulu. >>>> >>>> -- >>>> Damien Cassou >>>> http://damiencassou.seasidehosting.st >>>> >>>> "Success is the ability to go from one failure to another without >>>> losing enthusiasm." >>>> Winston Churchill >>> fair enough I will get it through lulu, I already have the pdf version >>> anyway so its not that I can't wait. >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Please-help-us-by-buying-the-book-tp4708575p4709232.h… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> -- View this message in context: http://forum.world.st/Please-help-us-by-buying-the-book-tp4708575p4709359.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 20, 2013

Re: [Pharo-dev] Stability of 3.0

by kilon

I dont have such problem. The problem I had was code completion having several errors while it tried to autocomplete and once I froze pharo because I changed a live object while the morph was displaying , that method was somewhat recycled (HelpBrowser class) so that may have been normal. But no problem with red boxes from what I can see, I am on 30402. -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709358.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 20, 2013

Re: [Pharo-dev] Dynamically adding nodes to Roassal

by Alejandro Infante

Also I forgot to tell you that the new book "Deep into Pharo" has a chapter for Roassal and another for Mondrian. Maybe that's the best place to start from, the link of the book is http://rmod.lille.inria.fr/pbe2/. 2013/9/20 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > Thanks Alejandro, > > Yes I went through the examples and I understood the difference between > the examples using the builder (which are easier) and with pure Roassal, > which are..let's say.. less user friendly.. > > I am trying, in pure Roassal, to do a tree map and add another node to the > ROView then calling signalUpdate. No luck 'till now.. > > Cheers, > R > > On Sep 20, 2013, at 3:01 PM, Alejandro Infante < > alejandroinfante91(a)gmail.com> > wrote: > > > Well, > > If you started with the Easel then you must have seen the examples. Well > at first you see two boxes with examples inside (one on the top and the > other below (If you dont see the second one just drag the view). > > > > The first one has a label at the top-left corner that says > ROMondrianExample, and this were done using the ROMondrianViewBuilder API, > and you can see that you interact mainly with the "view" variable. > > The second box is called ROExample and then you interact mainly with the > "rawView" variable which is pure Roassal. > > > > The difference between them is that the ROMondrianViewBuilder is a nice > and friendly API, but doing really complex stuff it's not possible. So we > go one level below to pure Roassal. > > > > Here you have the Collection class hierarchy in Roassal: > > |rawView| > > rawView := ROView new. > > Collection withAllSubclasses do: [ :c | > > | el | > > el := ROBorder elementOn: c. > > el @ ROPopup. > > rawView add: el ]. > > > > "Draw edges" > > rawView addAll: (ROEdge > > buildEdgesFromElements: rawView elements > > from: [ :cls | cls superclass ] > > to: #yourself > > using: ROLine new). > > > > ROTreeLayout on: rawView elementsNotEdge edges: rawView > elementsAsEdge. > > rawView open. > > > > I recommend you to see the ROExamples and if there is something that you > don't know just ask to the mailing list. > > You may like to see the ROExamples>>interactions>>addingOnClick example. > > > > > > 2013/9/20 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > > Thanks Alejandro, I will try what you propose! > > > > What do you mean by > > > Another thing bothering me is that you mentioned the method #nodes, > thats from the ROMondrianViewBuilder, which I think is not that friendly > with dynamic stuff. > > > > How would you construct a view without using the ROMondrianViewBuilder? > I am used to start as in the Roassal Easel like > > rawView := ROView new. > > view := ROMondrianViewBuilder view: rawView > > > > And then adding nodes to the view, calling view nodes: myNodes > > > > Cheers, > > R > > > > > > > > On Sep 20, 2013, at 1:49 PM, Alejandro Infante < > alejandroinfante91(a)gmail.com> > > wrote: > > > > > In Roassal calling the method #signalUpdate to the view should show > those new nodes. If you want to re-layout the nodes you should apply a new > layout to the nodes before the #signalUpdate. > > > > > > Another pretty interesting feature is the method > ROContainer>>callback: aCallback. The idea is that every time an element is > added inside the container the callback is called. > > > Now how you can use this: > > > > > > element callback: (ROContainerCallbackLayout new layout: (ROGridLayout > new gapSize: 2)). > > > > > > Remember that you must send signalUpdate to the view if you want to > see the changes. > > > > > > Another thing bothering me is that you mentioned the method #nodes, > thats from the ROMondrianViewBuilder, which I think is not that friendly > with dynamic stuff. > > > It is a little bit ugly but you can always get the ROView from > ROMondrianViewBuilder sending the message #view and over that do all kind > of Roassal magic stuff, like adding the callback with the TreeLayout the > the ROView itself. Also for adding new nodes you should add them directly > to the ROView, or at least I haven't found the way to do that without > having to add all the nodes again to the Builder. > > > > > > Hope that help you. > > > > > > > > > 2013/9/20 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > > > *and have the visualization re-layouted? > > > > > > On Sep 20, 2013, at 11:24 AM, "roberto.minelli(a)usi.ch" < > roberto.minelli(a)usi.ch> > > > wrote: > > > > > > > Hi, > > > > > > > > I was playing around with Roassal (in particular, a tree map) and I > have a question: Is there a way to dynamically adding nodes? I mean, once > the view is generated to update the #nodes by adding a new node (and > associations as well, i.e., edges) and have the visualization re- > > > > > > > > Thanks in advance. > > > > > > > > Roby > > > > > > > > > > > > > > > > > >

Sept. 20, 2013

How to browse SmalltalkHub ?

by kilon

I see in smalltalkhub there is an explore button, but it only displays a very small fragment of available projects. Is there a way to explore smalltalkhub and find all the available projects ? -- View this message in context: http://forum.world.st/How-to-browse-SmalltalkHub-tp4709355.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 20, 2013

Re: [Pharo-dev] Dynamically adding nodes to Roassal

by roberto.minelli＠usi.ch

Thanks Alejandro, Yes I went through the examples and I understood the difference between the examples using the builder (which are easier) and with pure Roassal, which are..let's say.. less user friendly.. I am trying, in pure Roassal, to do a tree map and add another node to the ROView then calling signalUpdate. No luck 'till now.. Cheers, R On Sep 20, 2013, at 3:01 PM, Alejandro Infante <alejandroinfante91(a)gmail.com> wrote: > Well, > If you started with the Easel then you must have seen the examples. Well at first you see two boxes with examples inside (one on the top and the other below (If you dont see the second one just drag the view). > > The first one has a label at the top-left corner that says ROMondrianExample, and this were done using the ROMondrianViewBuilder API, and you can see that you interact mainly with the "view" variable. > The second box is called ROExample and then you interact mainly with the "rawView" variable which is pure Roassal. > > The difference between them is that the ROMondrianViewBuilder is a nice and friendly API, but doing really complex stuff it's not possible. So we go one level below to pure Roassal. > > Here you have the Collection class hierarchy in Roassal: > |rawView| > rawView := ROView new. > Collection withAllSubclasses do: [ :c | > | el | > el := ROBorder elementOn: c. > el @ ROPopup. > rawView add: el ]. > > "Draw edges" > rawView addAll: (ROEdge > buildEdgesFromElements: rawView elements > from: [ :cls | cls superclass ] > to: #yourself > using: ROLine new). > > ROTreeLayout on: rawView elementsNotEdge edges: rawView elementsAsEdge. > rawView open. > > I recommend you to see the ROExamples and if there is something that you don't know just ask to the mailing list. > You may like to see the ROExamples>>interactions>>addingOnClick example. > > > 2013/9/20 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > Thanks Alejandro, I will try what you propose! > > What do you mean by > > Another thing bothering me is that you mentioned the method #nodes, thats from the ROMondrianViewBuilder, which I think is not that friendly with dynamic stuff. > > How would you construct a view without using the ROMondrianViewBuilder? I am used to start as in the Roassal Easel like > rawView := ROView new. > view := ROMondrianViewBuilder view: rawView > > And then adding nodes to the view, calling view nodes: myNodes > > Cheers, > R > > > > On Sep 20, 2013, at 1:49 PM, Alejandro Infante <alejandroinfante91(a)gmail.com> > wrote: > > > In Roassal calling the method #signalUpdate to the view should show those new nodes. If you want to re-layout the nodes you should apply a new layout to the nodes before the #signalUpdate. > > > > Another pretty interesting feature is the method ROContainer>>callback: aCallback. The idea is that every time an element is added inside the container the callback is called. > > Now how you can use this: > > > > element callback: (ROContainerCallbackLayout new layout: (ROGridLayout new gapSize: 2)). > > > > Remember that you must send signalUpdate to the view if you want to see the changes. > > > > Another thing bothering me is that you mentioned the method #nodes, thats from the ROMondrianViewBuilder, which I think is not that friendly with dynamic stuff. > > It is a little bit ugly but you can always get the ROView from ROMondrianViewBuilder sending the message #view and over that do all kind of Roassal magic stuff, like adding the callback with the TreeLayout the the ROView itself. Also for adding new nodes you should add them directly to the ROView, or at least I haven't found the way to do that without having to add all the nodes again to the Builder. > > > > Hope that help you. > > > > > > 2013/9/20 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > > *and have the visualization re-layouted? > > > > On Sep 20, 2013, at 11:24 AM, "roberto.minelli(a)usi.ch" <roberto.minelli(a)usi.ch> > > wrote: > > > > > Hi, > > > > > > I was playing around with Roassal (in particular, a tree map) and I have a question: Is there a way to dynamically adding nodes? I mean, once the view is generated to update the #nodes by adding a new node (and associations as well, i.e., edges) and have the visualization re- > > > > > > Thanks in advance. > > > > > > Roby > > > > > > > > >

Sept. 20, 2013

Re: [Pharo-dev] Dynamically adding nodes to Roassal

by btc＠openinworld.com

Sept. 20, 2013

Re: [Pharo-dev] Dynamically adding nodes to Roassal

by Alejandro Infante

Well, If you started with the Easel then you must have seen the examples. Well at first you see two boxes with examples inside (one on the top and the other below (If you dont see the second one just drag the view). The first one has a label at the top-left corner that says ROMondrianExample, and this were done using the ROMondrianViewBuilder API, and you can see that you interact mainly with the "view" variable. The second box is called ROExample and then you interact mainly with the "rawView" variable which is pure Roassal. The difference between them is that the ROMondrianViewBuilder is a nice and friendly API, but doing really complex stuff it's not possible. So we go one level below to pure Roassal. Here you have the Collection class hierarchy in Roassal: |rawView| rawView := ROView new. Collection withAllSubclasses do: [ :c | | el | el := ROBorder elementOn: c. el @ ROPopup. rawView add: el ]. "Draw edges" rawView addAll: (ROEdge buildEdgesFromElements: rawView elements from: [ :cls | cls superclass ] to: #yourself using: ROLine new). ROTreeLayout on: rawView elementsNotEdge edges: rawView elementsAsEdge. rawView open. I recommend you to see the ROExamples and if there is something that you don't know just ask to the mailing list. You may like to see the ROExamples>>interactions>>addingOnClick example. 2013/9/20 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > Thanks Alejandro, I will try what you propose! > > What do you mean by > > Another thing bothering me is that you mentioned the method #nodes, > thats from the ROMondrianViewBuilder, which I think is not that friendly > with dynamic stuff. > > How would you construct a view without using the ROMondrianViewBuilder? I > am used to start as in the Roassal Easel like > rawView := ROView new. > view := ROMondrianViewBuilder view: rawView > > And then adding nodes to the view, calling view nodes: myNodes > > Cheers, > R > > > > On Sep 20, 2013, at 1:49 PM, Alejandro Infante < > alejandroinfante91(a)gmail.com> > wrote: > > > In Roassal calling the method #signalUpdate to the view should show > those new nodes. If you want to re-layout the nodes you should apply a new > layout to the nodes before the #signalUpdate. > > > > Another pretty interesting feature is the method ROContainer>>callback: > aCallback. The idea is that every time an element is added inside the > container the callback is called. > > Now how you can use this: > > > > element callback: (ROContainerCallbackLayout new layout: (ROGridLayout > new gapSize: 2)). > > > > Remember that you must send signalUpdate to the view if you want to see > the changes. > > > > Another thing bothering me is that you mentioned the method #nodes, > thats from the ROMondrianViewBuilder, which I think is not that friendly > with dynamic stuff. > > It is a little bit ugly but you can always get the ROView from > ROMondrianViewBuilder sending the message #view and over that do all kind > of Roassal magic stuff, like adding the callback with the TreeLayout the > the ROView itself. Also for adding new nodes you should add them directly > to the ROView, or at least I haven't found the way to do that without > having to add all the nodes again to the Builder. > > > > Hope that help you. > > > > > > 2013/9/20 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > > *and have the visualization re-layouted? > > > > On Sep 20, 2013, at 11:24 AM, "roberto.minelli(a)usi.ch" < > roberto.minelli(a)usi.ch> > > wrote: > > > > > Hi, > > > > > > I was playing around with Roassal (in particular, a tree map) and I > have a question: Is there a way to dynamically adding nodes? I mean, once > the view is generated to update the #nodes by adding a new node (and > associations as well, i.e., edges) and have the visualization re- > > > > > > Thanks in advance. > > > > > > Roby > > > > > > > > >

Sept. 20, 2013