- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Doc of mustache

by stepharo

Hi Norbert I'm improving the doc. I added some text on section and others.. And on list with collection I have the following behavior and I do not understand why on string. | templateString context | templateString := 'Shown. {{#number}} Shown too! {{/number}}'. context := { 'number' -> #(1 2 3) } asDictionary. (MustacheTemplate on: templateString) value: context 'Shown. Shown too! Shown too! Shown too! ' | templateString context | templateString := 'Shown. {{#number}} Shown too! {{/number}}'. context := { 'number' -> '1 2 3' } asDictionary. (MustacheTemplate on: templateString) value: context 'Shown. Shown too! Shown too! Shown too! Shown too! Shown too! ' On 11/7/14 10:53, Norbert Hartl wrote: > > Am 11.07.2014 um 10:43 schrieb stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > >> Hi guys >> >> I would like to experiment with template for a small web project I >> have (my web page) and >> I would like to try mustache. Is there any tutorial? doc? >> I know that "jose maria aguerra" wrote a tutorial but I cannot find >> it anymore. > > http://norbert.hartl.name/blog/2013/10/03/mustache-templates-for-smalltalk/ > > Norbert >

July 13, 2014

Re: [Pharo-dev] Nautilus - Recover Lost Changes - Class Comments

by stepharo

Hi Ben > > I had SomeClassA that did not have a class comment, and so an alert > icon showed for it in Nautilus. Then I used Recover-Lost-Changes > which added a class comment for SomeClassA, but the icon did not > update. I understood that Pharo 4 will be modifying how the > ".changes" file works. Will this include modifying the mechanism of > Recover-Lost-Changes mechanism? Hence, should create a Case for this > for Pharo 4, or just for Pharo 3 ? Report for 40 and we will see later. Because the community should stress test Ombu before we push it into the arena. > > cheers -ben > >

July 13, 2014

Re: [Pharo-dev] Reporting Segmentation fault

by stepharo

Hi Yuriy Pay attention (It happens to me) that you control which VM is launched. > Iâve encountered a situation where pharo crashes, and when I run it from command line I get: "Segmentation fault: 11". Also before that some trace appears starting with highlighted: "MessageNotUnderstood: ToolDockingBarMorph>>popUpEvent:in:â. Iâve also updated my Pharo launcher and now stack trace disappeared (probably because now I have to specify some flag), but the problem remains. Should I report this to pharo issue tracker, or this is a VM problem and it should be handled in a different way? Can you give us more information: - image - VM version - a reproducible case Stef

July 13, 2014

Reporting Segmentation fault

by Yuriy Tymchuk

Iâve encountered a situation where pharo crashes, and when I run it from command line I get: "Segmentation fault: 11". Also before that some trace appears starting with highlighted: "MessageNotUnderstood: ToolDockingBarMorph>>popUpEvent:in:â. Iâve also updated my Pharo launcher and now stack trace disappeared (probably because now I have to specify some flag), but the problem remains. Should I report this to pharo issue tracker, or this is a VM problem and it should be handled in a different way? Uko

July 13, 2014

Re: [Pharo-dev] handling method/classes updartes

by Yuriy Tymchuk

Itâs fine. I was asking because I am creating entities that should stay in sync with certain methods per entity. So I wandered if an entity could register to that method. Now if I need to register to SystemAnnouncer, I have either to register each entity separately and check if announcement is regarding the method Iâm interested in. Or I can create the manager of entities which will listen to announcer and tell entities what to do. I have to figure out which approach is better. Uko On 13 Jul 2014, at 18:10, stepharo <stepharo(a)free.fr> wrote: > What you should realize is that when we introduce the SystemAnnouncer ancestor with Roel Wuyts, there way no such a thing: a system that to whim you register and notify about changes. So in VW you had to go and find all the places and patch them to get you notified. > So to me this is a huge enhancements to support the creation of great tool. Now working with a real system is complex because > a class can recategorized, a method rename, recatogorized, removed.... and there is magical solution - at least that I know > > Stef > > On 10/7/14 19:38, Yuriy Tymchuk wrote: >> Hi, >> >> is there a way to subscribe directly to a method/class, so I san know when it updates/is removed and so on? Because it looks like a pain to subscribe to system announcer and check if the method changed is the one I need. >> >> Uko >> >> > >

July 13, 2014

Re: [Pharo-dev] handling method/classes updartes

by stepharo

What you should realize is that when we introduce the SystemAnnouncer ancestor with Roel Wuyts, there way no such a thing: a system that to whim you register and notify about changes. So in VW you had to go and find all the places and patch them to get you notified. So to me this is a huge enhancements to support the creation of great tool. Now working with a real system is complex because a class can recategorized, a method rename, recatogorized, removed.... and there is magical solution - at least that I know Stef On 10/7/14 19:38, Yuriy Tymchuk wrote: > Hi, > > is there a way to subscribe directly to a method/class, so I san know when it updates/is removed and so on? Because it looks like a pain to subscribe to system announcer and check if the method changed is the one I need. > > Uko > >

July 13, 2014

Nautilus - Recover Lost Changes - Class Comments

by Ben Coman

I had SomeClassA that did not have a class comment, and so an alert icon showed for it in Nautilus. Then I used Recover-Lost-Changes which added a class comment for SomeClassA, but the icon did not update. I understood that Pharo 4 will be modifying how the ".changes" file works. Will this include modifying the mechanism of Recover-Lost-Changes mechanism? Hence, should create a Case for this for Pharo 4, or just for Pharo 3 ? cheers -ben

July 13, 2014

Re: [Pharo-dev] Doc of mustache

by stepharo

Thanks Thanks Thanks. I want to check Marina too. >> And I'm reading pillar code because I would like to see how I can use a API >> to generate XHTML and take into account mustache > > pillarString := '! Some text > > -item1 > -item2'. > > pillarDocument := PRDocumentParser parse: pillarString. > > htmlString := PRHTMLWriter write: pillarDocument . > > > 'main.template.html' asFileReference mustacheTemplateDuring: [ :template| > > 'result.html' asFileReference writeStreamDo: [ :outStream | > > outStream nextPutAll: (template value: { 'contents' -> htmlString > } asDictionary) > > ] > > ] >

July 13, 2014

Design trends in UI for Mobiles

by GOUBIER Thierry

Food for thought for those working on theming for Pharo: http://arstechnica.com/gadgets/2014/07/the-software-design-trends-that-we-l… Flat buttons for a new kind of game... Finding out what is clickable in a GUI :) Thierry

July 13, 2014

Re: [Pharo-dev] Doc of mustache

by Damien Cassou

On Fri, Jul 11, 2014 at 10:55 AM, stepharo <stepharo(a)free.fr> wrote: > And I'm reading pillar code because I would like to see how I can use a API > to generate XHTML and take into account mustache pillarString := '! Some text -item1 -item2'. pillarDocument := PRDocumentParser parse: pillarString. htmlString := PRHTMLWriter write: pillarDocument . 'main.template.html' asFileReference mustacheTemplateDuring: [ :template| 'result.html' asFileReference writeStreamDo: [ :outStream | outStream nextPutAll: (template value: { 'contents' -> htmlString } asDictionary) ] ] -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 13, 2014