Re: [Pharo-users] MetaLink invocation with method returned value
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 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 > >> On 25 Feb 2016, at 07:42, Alain Rastoul wrote: >> >> Hi, >> >> I would like to trace returned values with MetaLink, but didn't found the >> correct #arguments: parameter. >> Here in my example I would like to call aMethodCall:returned: with the >> return value of aMethodCall: >> (the method on which the link is installed) >> >> >> (MyObject>>#aMethodCall:) ast >> link: (MetaLink new >> metaObject: myObject; >> control: #after; >> selector: #aMethodCall:returned: ; >> arguments: #( arguments object)). >> >> object is myObject not the returned value, value does not work, and I didn't >> found any one working. >> >> Does anyone know the correct invocation and can help me ? >> >> Many thanks >> >> >> regards, >> >> Alain >> >> > >
Re: [Pharo-users] A Spec widget to hold non-editable multi-lines text?
> > 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
Re: [Pharo-users] A Spec widget to hold non-editable multi-lines text?
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
Re: [Pharo-users] A Spec widget to hold non-editable multi-lines text?
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 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 >> >> > >
Re: [Pharo-users] A Spec widget to hold non-editable multi-lines text?
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 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
Re: [Pharo-users] [Moose-dev] Call for action for Roassal
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 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-...@list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com “Live like you mean it."
Re: [Pharo-users] MetaLink invocation with method returned value
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 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
Re: [Pharo-users] [Moose-dev] Re: [Pharo-dev] Call for action for Roassal
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 wrote: > > Do you have an example? I am not sure to understand. > > Alexandre > > >> On Feb 25, 2016, at 12:40 PM, Tudor Girba 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 >>> 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-...@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-...@list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Value is always contextual."
Re: [Pharo-users] [Pharo-dev] [Moose-dev] Call for action for Roassal
Do you have an example? I am not sure to understand. Alexandre > On Feb 25, 2016, at 12:40 PM, Tudor Girba 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 >> 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-...@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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Re: [Pharo-users] [Moose-dev] [Pharo-dev] Re: Call for action for Roassal
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 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
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>
>
> Cheers,
> Alexandre
>
>> On Feb 25, 2016, at 1:37 PM, Tudor Girba 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
>>> wrote:
>>>
>>> Do you have an example? I am not sure to understand.
>>>
>>> Alexandre
>>>
>>>
On Feb 25, 2016, at 12:40 PM, Tudor Girba 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
> 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-...@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-...@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-...@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."
[Pharo-users] Is Seaside's Canvas/Brush metaphor for creating HTML available outside of Seaside?
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-available-outside-of-Seaside-tp4880825.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] [Pharo-dev] Who is using Pharo Launcher and for what
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-tp4879192p4880830.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] Is Seaside's Canvas/Brush metaphor for creating HTML available outside of Seaside?
Depends on what you mean with ‘outside of Seaside’ but maybe this is what you would be looking for: WAHtmlCanvas builder render: [ :html | html anchor url: 'htttp://www.seaside.st'; with: 'Seaside Homepage' ] See WABuilderCanvasTest for some examples. Hope this helps? Johan > On 25 Feb 2016, at 18:21, MartinW wrote: > > 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-available-outside-of-Seaside-tp4880825.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >
Re: [Pharo-users] I wish there were ePUB versions of Pharo books
ePub export should be pretty easy to add to Pillar, based on the existing html export. Any volunteers ? Le jeudi 25 février 2016, MartinW a écrit : > 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-tp4880836.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet
Re: [Pharo-users] Is Seaside's Canvas/Brush metaphor for creating HTML available outside of Seaside?
Hi Martin, > On 25 Feb 2016, at 18:21, MartinW wrote: > > 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? Yes you can: WAHtmlCanvas builder render: [ :html | html heading: 'Test'; paragraph: 'foo bar' ]. Or just instantiate any component and let it render. Sven > Best regards, > Martin. > > > > -- > View this message in context: > http://forum.world.st/Is-Seaside-s-Canvas-Brush-metaphor-for-creating-HTML-available-outside-of-Seaside-tp4880825.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >
Re: [Pharo-users] I wish there were ePUB versions of Pharo books
Le 25/02/2016 19:04, MartinW a écrit : > 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-tp4880836.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > Hi, We need manpower to implement the ePUB exporter in Pillar. If we implement it we could have an ePUB version of all the books (except Deep Into Pharo for the moment). But there is still the problem of manpower :( It should not be that hard since there is a lot of tests to help. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France signature.asc Description: OpenPGP digital signature
Re: [Pharo-users] I wish there were ePUB versions of Pharo books
2016-02-25 15:40 GMT-03:00 Damien Pollet : > ePub export should be pretty easy to add to Pillar, based on the existing > html export. Any volunteers ? I don't volunteer, but the ebook creator of the ProGit book creates really good looking book, with a menu to access the chapters. https://github.com/progit/progit/blob/master/README.original.md Regards! Esteban A. Maringolo
Re: [Pharo-users] I wish there were ePUB versions of Pharo books
Hi martin Why don't you give a try? Pillar has - a nice document - some nice visitors - nice test system So someone can extend it. Because we cannot do everything. You cannot imagine how we are busy right now. Stef Le 25/2/16 19:04, MartinW a écrit : 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-tp4880836.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
[Pharo-users] I wish there were ePUB versions of Pharo books
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-tp4880836.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] Is Seaside's Canvas/Brush metaphor for creating HTML available outside of Seaside?
Hi johan What would be good is to have it in a separate package because I wanted to output HTML and loading seaside for that was heavy. Stef Le 25/2/16 19:33, Johan Brichau a écrit : Depends on what you mean with ‘outside of Seaside’ but maybe this is what you would be looking for: WAHtmlCanvas builder render: [ :html | html anchor url: 'htttp://www.seaside.st'; with: 'Seaside Homepage' ] See WABuilderCanvasTest for some examples. Hope this helps? Johan On 25 Feb 2016, at 18:21, MartinW wrote: 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-available-outside-of-Seaside-tp4880825.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] Is Seaside's Canvas/Brush metaphor for creating HTML available outside of Seaside?
MartinW writes: > 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? Pillar has this which is less powerful thank Seaside but good enough for us: canvas tag name: 'a'; parameterAt: 'id' put: anId; with: '' -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-users] Is Seaside's Canvas/Brush metaphor for creating HTML available outside of Seaside?
And Zn has a very simple one too (since recently):
generateHelp
"Generate an HTML page with links to all pages I support"
^ ZnHtmlOutputStream streamContents: [ :html |
html page: (self class name, ' Help') do: [
html tag: #h3 with: 'Available Pages'.
html tag: #ul do: [
prefixMap keys sorted do: [ :each |
html tag: #li do: [
html tag: #a attributes: { #href. each } with: each ] ] ] ] ]
But Seaside's is better, though much larger.
> On 26 Feb 2016, at 06:38, Damien Cassou wrote:
>
> MartinW writes:
>
>> 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?
>
> Pillar has this which is less powerful thank Seaside but good enough for
> us:
>
> canvas tag
> name: 'a';
> parameterAt: 'id' put: anId;
> with: ''
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill
>
