February 2016 - Pharo-users

I wish there were ePUB versions of Pharo books

by MartinW

I like Pharo's new book site: http://files.pharo.org/books/ And since I use a tablet more often, I wish there were ePUB versions of the books. Why is it important? You could change the color scheme to light text on dark background and increase font sizes and thus have a much more comfortable reading experience than with PDFs. I remember there was some talk about this some time ago. Best regards, Martin. -- View this message in context: http://forum.world.st/I-wish-there-were-ePUB-versions-of-Pharo-books-tp4880… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 25, 2016

Re: [Pharo-users] [Pharo-dev] Who is using Pharo Launcher and for what

by MartinW

SergeStinckwich wrote > PharoLauncher is the cornerstone of my workflow in order to manage all > my Pharo images. Same here. I use it to create fresh images, manage and start all my images. I use it for my private projects as well as for my projects at Humboldt University Berlin. Thank you for the good work. Best regards, Martin. -- View this message in context: http://forum.world.st/Who-is-using-Pharo-Launcher-and-for-what-tp4879192p48… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 25, 2016

Is Seaside's Canvas/Brush metaphor for creating HTML available outside of Seaside?

by MartinW

Hi, I know, there are templating systems like Mustache, but I always loved Seaside's Canvas/Brush metaphor for creating HTML. Is it available as a standalone package, so it can be used outside of Seaside? Best regards, Martin. -- View this message in context: http://forum.world.st/Is-Seaside-s-Canvas-Brush-metaphor-for-creating-HTML-… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 25, 2016

Re: [Pharo-users] [Moose-dev] [Pharo-dev] Re: Call for action for Roassal

by Tudor Girba

Oh, I missed this one :). So, now I can refactor the code that is still using the RTEdge class side methods :). Great! Thanks, Doru > On Feb 25, 2016, at 1:59 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Oh, but this has been in Roassal for many months (I have implemented since right after ESUG). You need to use #source:connectFrom:toAll: > > Here is an example that randomly generate a graph and render it using this facility: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > nbOfNodes := 40. > nbOfRandomEdges := 40. > > nodes := 1 to: nbOfNodes. > edges := (1 to: nbOfRandomEdges) > collect: [ :notUsed | nodes atRandom -> {nodes atRandom . nodes atRandom} ]. > > b := RTMondrian new. > > b shape circle color: (Color black alpha: 0.5). > b nodes: nodes. > > b shape line color: (Color gray alpha: 0.3). > b edges > source: edges connectFrom: #key toAll: #value. > > b layout force. > b > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > <Screen Shot 2016-02-25 at 1.57.24 PM.png> > > Cheers, > Alexandre > >> On Feb 25, 2016, at 1:37 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> We discussed this before. Try to draw a hierarchy using classes and inheritance objects (so, without using the class to superclass navigation). Something like this: >> >> view := RTMondrian new. >> view nodes: classes. >> view edges objects: inheritances; connectFrom: #superclass to: #subclass. >> view layout tree. >> view >> >> It wonât work. >> >> Cheers, >> Doru >> >> >>> On Feb 25, 2016, at 1:29 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> >>> Do you have an example? I am not sure to understand. >>> >>> Alexandre >>> >>> >>>> On Feb 25, 2016, at 12:40 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> This is very cool. We will all benefit from this documentation. >>>> >>>> One thing that I would still like to see fixed before the release is the edge building (this problem of not being able to properly specify random objects to be taken into account when building edges). Could we work on that? >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>>> On Feb 24, 2016, at 9:51 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>> >>>>> Dear community, >>>>> >>>>> As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: >>>>> >>>>> What are the 3 aspects you would like to see improved in Roassal? >>>>> >>>>> You can answer publicly or by sending private messages. >>>>> >>>>> Kind regards, >>>>> Alexandre >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)list.inf.unibe.ch >>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> âLive like you mean it." >>>> >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Value is always contextual." >> >> >> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Next time you see your life passing by, say 'hi' and get to know her."

Feb. 25, 2016

Re: [Pharo-users] [Pharo-dev] [Moose-dev] Re: Call for action for Roassal

by Alexandre Bergel

Oh, but this has been in Roassal for many months (I have implemented since right after ESUG). You need to use #source:connectFrom:toAll: Here is an example that randomly generate a graph and render it using this facility: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= nbOfNodes := 40. nbOfRandomEdges := 40. nodes := 1 to: nbOfNodes. edges := (1 to: nbOfRandomEdges) collect: [ :notUsed | nodes atRandom -> {nodes atRandom . nodes atRandom} ]. b := RTMondrian new. b shape circle color: (Color black alpha: 0.5). b nodes: nodes. b shape line color: (Color gray alpha: 0.3). b edges source: edges connectFrom: #key toAll: #value. b layout force. b -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre > On Feb 25, 2016, at 1:37 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > We discussed this before. Try to draw a hierarchy using classes and inheritance objects (so, without using the class to superclass navigation). Something like this: > > view := RTMondrian new. > view nodes: classes. > view edges objects: inheritances; connectFrom: #superclass to: #subclass. > view layout tree. > view > > It wonât work. > > Cheers, > Doru > > >> On Feb 25, 2016, at 1:29 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >> Do you have an example? I am not sure to understand. >> >> Alexandre >> >> >>> On Feb 25, 2016, at 12:40 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> This is very cool. We will all benefit from this documentation. >>> >>> One thing that I would still like to see fixed before the release is the edge building (this problem of not being able to properly specify random objects to be taken into account when building edges). Could we work on that? >>> >>> Cheers, >>> Doru >>> >>> >>>> On Feb 24, 2016, at 9:51 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> >>>> Dear community, >>>> >>>> As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: >>>> >>>> What are the 3 aspects you would like to see improved in Roassal? >>>> >>>> You can answer publicly or by sending private messages. >>>> >>>> Kind regards, >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)list.inf.unibe.ch >>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> âLive like you mean it." >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > "Value is always contextual." > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 25, 2016

Re: [Pharo-users] [Moose-dev] Re: [Pharo-dev] Call for action for Roassal

by Tudor Girba

Hi, We discussed this before. Try to draw a hierarchy using classes and inheritance objects (so, without using the class to superclass navigation). Something like this: view := RTMondrian new. view nodes: classes. view edges objects: inheritances; connectFrom: #superclass to: #subclass. view layout tree. view It wonât work. Cheers, Doru > On Feb 25, 2016, at 1:29 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Do you have an example? I am not sure to understand. > > Alexandre > > >> On Feb 25, 2016, at 12:40 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> This is very cool. We will all benefit from this documentation. >> >> One thing that I would still like to see fixed before the release is the edge building (this problem of not being able to properly specify random objects to be taken into account when building edges). Could we work on that? >> >> Cheers, >> Doru >> >> >>> On Feb 24, 2016, at 9:51 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> >>> Dear community, >>> >>> As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: >>> >>> What are the 3 aspects you would like to see improved in Roassal? >>> >>> You can answer publicly or by sending private messages. >>> >>> Kind regards, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> âLive like you mean it." >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Value is always contextual."

Feb. 25, 2016

Re: [Pharo-users] [Pharo-dev] [Moose-dev] Call for action for Roassal

by Alexandre Bergel

Do you have an example? I am not sure to understand. Alexandre > On Feb 25, 2016, at 12:40 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > This is very cool. We will all benefit from this documentation. > > One thing that I would still like to see fixed before the release is the edge building (this problem of not being able to properly specify random objects to be taken into account when building edges). Could we work on that? > > Cheers, > Doru > > >> On Feb 24, 2016, at 9:51 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >> Dear community, >> >> As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: >> >> What are the 3 aspects you would like to see improved in Roassal? >> >> You can answer publicly or by sending private messages. >> >> Kind regards, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > âLive like you mean it." > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 25, 2016

Re: [Pharo-users] MetaLink invocation with method returned value

by Alain Rastoul

Thank you both for your answers, Great. No emergency for me, it's for a POC about design by contract with annotations I started last year and resumed recently. As it starts working (at least it looks like), I will publish on smalltalkhub soon so others can play with it too, tomorrow, time to finish some tests and at least one readme . Alain On 25/02/2016 09:52, Marcus Denker wrote: > Hi, > > yes, this is on the TODOâ¦ I am last and this week focussed on stabilising Pharo5, I will come > back to my backlog of MetaLinks starting next week. > > Marcus > >> On 25 Feb 2016, at 07:52, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> As far as I know return values for methods are not yet implemented. Iâve talked with Marcus, itâs planned but not the top priority. For now you can all links to the return nodes of a method. >> >> Uko >>

Feb. 25, 2016

Re: [Pharo-users] [Moose-dev] Call for action for Roassal

by Tudor Girba

This is very cool. We will all benefit from this documentation. One thing that I would still like to see fixed before the release is the edge building (this problem of not being able to properly specify random objects to be taken into account when building edges). Could we work on that? Cheers, Doru > On Feb 24, 2016, at 9:51 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Dear community, > > As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: > > What are the 3 aspects you would like to see improved in Roassal? > > You can answer publicly or by sending private messages. > > Kind regards, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com âLive like you mean it."

Feb. 25, 2016

Re: [Pharo-users] A Spec widget to hold non-editable multi-lines text?

by Julien Delplanque

Nice, can't wait to read it :) Julien On 25/02/16 10:58, Peter UhnÃ¡k wrote: > I'm sure it's documented somewhereâ¦ in any case new Spec documentation is > emerging so let's not forget to make sure it's there. > > Peter > > On Thu, Feb 25, 2016 at 10:49 AM, Julien Delplanque <julien(a)tamere.eu> > wrote: > >> Indeed but I mean, I was not able to deduce the fact that to have a widget >> holding not-editable multi-line text I have to use >> >> TextInputFieldModel and use #enabled: message... >> >> But maybe there is already documentation about that? >> >> Julien >> >> >> >> On 25/02/16 09:58, Peter UhnÃ¡k wrote: >> >>> Maybe this should be documented in the class comment of >>>> TextInputFieldModel? >>>> >>>> This is a feature of AbstractWidgetModel, so it applies to all widgets >>> (buttons, texts, selects, ...). >>> >>> Peter >>> >>> >>

Feb. 25, 2016