May 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo first timer

by stepharo

Le 22/5/15 12:30, Jan BlizniÄenko a Ã©crit : > Hello, I'm not so experienced ST user and I know your post is meant for the > developers more than other users, but I would like to join the discussion > and maybe help anyway :) > > (1) It is true that Nautilus (class browser) needs a lot of time to display > greater amounts of classes. For example displaying whole Roassal2 package > with 319 classes for first time takes 12 seconds on my PC and I always curse > myself for even clicking on it, so displaying all classes in Pharo (which is > almost 10 thousand in basic image) takes a lot of time, but honestly, I have > never needed to display all classes in whole Pharo. Esteban is working on a new list morph widgets that will solve all this problem. The logic of the pluggableListMorph is bogus > > (2) Class is "abstract" and should not have any instances. allInstances > method returns only instances of receiver, but not of subclasses of > receiver. Getting instances of Metaclass is something quite different - it > returns all "classes of classes". Maybe take a look at this: > http://pharo.gforge.inria.fr/PBE1/Metaclasses/figures/TranslucentMetaclassC… > Method allSubclasses gives you everything recursively connected by empty > arrows (subclasses) and allInstances gives you everything connected by > double filled arrows (instances). > > Jan > > > igblan wrote >> I am an experienced SMalltalk user. Two things surprised me when I first >> tried Pharo. >> >> (1) Selecting ProtoObject and then clicking Heirarchy takes about 10 >> seconds to display the full heirarchy. This seems awfully slow. >> >> (2) Inspecting 'Class allInstances' gives an empty array. This doesn't >> seem quite right! 'Metaclass allInstances' gives the expected result. >> >> Cheers, Paul > > > > > -- > View this message in context: http://forum.world.st/Pharo-first-timer-tp4827969p4828062.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

May 22, 2015

Re: [Pharo-users] SoundEx and Metaphone

by Udo Schneider

I ported some phonetic comparison code (including double metaphone) from Bob Jarvis' Dolphin Goodies to Pharo. Might be worth a look: http://www.smalltalkhub.com/#!/~UdoSchneider/SoundsLike You can also check "phonet" which is IMHO more applicable when dealing with German: http://www.smalltalkhub.com/#!/~UdoSchneider/Phonet Hope this helps, Udo On 22/05/15 16:13, Torsten Bergmann wrote: > We have SoundEx http://smalltalkhub.com/#!/~riverdusty/SXSoundEx > do we also already have http://en.wikipedia.org/wiki/Metaphone?

May 22, 2015

SoundEx and Metaphone

by Torsten Bergmann

We have SoundEx http://smalltalkhub.com/#!/~riverdusty/SXSoundEx do we also already have http://en.wikipedia.org/wiki/Metaphone?

May 22, 2015

Re: [Pharo-users] Pharo first timer

by Jan BlizniÄenko

Hello, I'm not so experienced ST user and I know your post is meant for the developers more than other users, but I would like to join the discussion and maybe help anyway :) (1) It is true that Nautilus (class browser) needs a lot of time to display greater amounts of classes. For example displaying whole Roassal2 package with 319 classes for first time takes 12 seconds on my PC and I always curse myself for even clicking on it, so displaying all classes in Pharo (which is almost 10 thousand in basic image) takes a lot of time, but honestly, I have never needed to display all classes in whole Pharo. (2) Class is "abstract" and should not have any instances. allInstances method returns only instances of receiver, but not of subclasses of receiver. Getting instances of Metaclass is something quite different - it returns all "classes of classes". Maybe take a look at this: http://pharo.gforge.inria.fr/PBE1/Metaclasses/figures/TranslucentMetaclassC… Method allSubclasses gives you everything recursively connected by empty arrows (subclasses) and allInstances gives you everything connected by double filled arrows (instances). Jan igblan wrote > I am an experienced SMalltalk user. Two things surprised me when I first > tried Pharo. > > (1) Selecting ProtoObject and then clicking Heirarchy takes about 10 > seconds to display the full heirarchy. This seems awfully slow. > > (2) Inspecting 'Class allInstances' gives an empty array. This doesn't > seem quite right! 'Metaclass allInstances' gives the expected result. > > Cheers, Paul -- View this message in context: http://forum.world.st/Pharo-first-timer-tp4827969p4828062.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 22, 2015

Re: [Pharo-users] [Pre-ANN][Job] We are looking for a "Engineer R&D"

by Marcus Denker

Hi, No job posting yet as we are seeing what exact kind of person we can hire. There is a certain chance that this will not be constrained to âtwo years after universityâ. Job posting will be finalised next week, if you are interested (or now someone who might) ==> please contact me already now. Marcus > On 19 May 2015, at 17:10, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We will put the official announce online later this weekâ¦ we are looking to fill a a âyoung engineer positionâ. > This is for recent graduates who finished their degree 2013/2014/2015. > > The topic is to work for 2 years on improving âremoteâ debugging for cases like server deployment, typical > cloud scenarios and when using embedded Pharo images (e.g. for robotics). > > If you are interested (or know someone who might), please contact me. > (official announcement will be online later this week). > > Marcus >

May 22, 2015

Re: [Pharo-users] Fun with pillar and mustache

by stepharo

>> - we made some themes based on the one I made for dbxtalk, the one >> from stef's personal website and esug website. >> - we tried to push site configuration to the pillar.conf (title, >> menu/navigation information, author/contact info) > > I had a look at Cocoon but I'm not sure what purpose it serves. Maybe > I need to get to used to it. This is to decouple the code managing the configuration parameter from Pier because we have different needs for Ecstatic > >> - another thing we wanted to push was the writing of plugins for >> the moment taking benefit from the [[[eval=true]]]. We were thinking >> however on making a special annotation for it. We have two really >> simple stupid "plugins", one that shows a list of news/blog feed, one >> that generates a list of publications based on a bib file using citezen. >> > YES! That is exactly what I was looking for. Something that can be > evaluated dynamically. That opens a wide range of possibilities. but for web site you do not want to get somebody to hack your system. So this is why we are defining pluggings. >> I originally started this for the new dbxtalk site which is written >> basically in pillar. >> >> http://dbxtalk.smallworks.eu/ >> >> You can see the source code of this site in here: >> >> https://github.com/guillep/DBXTalk/tree/gh-pages >> > Nice! > >> Of course, there you will notice a lot of *workarounds* to make it >> work. I've made a list of those workarounds and sent them to Cyril to >> see if we can have better support for them in pillar. >> >> I'd be pleased if you contribute and push it :). We have this trello >> board to add ideas and manage our backlog >> >> https://trello.com/b/2t7qTWpp/ecstatic >> > Thanks. I think I'll find some time this weekend to see how your > project fits into my needs. I'll be happy nagging you about some things ;)

May 22, 2015

Re: [Pharo-users] Fun with pillar and mustache

by Norbert Hartl

Guille, thanks for revealing the secret project :) I can see what it is doing. I'll experiment a little more with my own stuff and then I can see what might match. At the moment ecstatic and cocoon appear to be rather file centric. My approach is doing everything in the image first and export it then to somewhere. So I need to learn what I need and then I'll need cocoon and such as exports to be able to do commandline generation. I'm sure we can exchange some ideas and code. The rest is open. thanks again, Norbert > Am 21.05.2015 um 10:51 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi! > > Well, we have this secret really not mature project we started with stef a couple of weeks ago. > > https://github.com/guillep/Ecstatic <https://github.com/guillep/Ecstatic> > > For now it has some simple features: > - you open an image and it will start serving your site + regenerating it every couple of seconds (nice to debug and forget about running pillar commands) > - we made some themes based on the one I made for dbxtalk, the one from stef's personal website and esug website. > - we tried to push site configuration to the pillar.conf (title, menu/navigation information, author/contact info) > - another thing we wanted to push was the writing of plugins for the moment taking benefit from the [[[eval=true]]]. We were thinking however on making a special annotation for it. We have two really simple stupid "plugins", one that shows a list of news/blog feed, one that generates a list of publications based on a bib file using citezen. > > I originally started this for the new dbxtalk site which is written basically in pillar. > > http://dbxtalk.smallworks.eu/ <http://dbxtalk.smallworks.eu/> > > You can see the source code of this site in here: > > https://github.com/guillep/DBXTalk/tree/gh-pages <https://github.com/guillep/DBXTalk/tree/gh-pages> > > Of course, there you will notice a lot of *workarounds* to make it work. I've made a list of those workarounds and sent them to Cyril to see if we can have better support for them in pillar. > > I'd be pleased if you contribute and push it :). We have this trello board to add ideas and manage our backlog > > https://trello.com/b/2t7qTWpp/ecstatic <https://trello.com/b/2t7qTWpp/ecstatic> > > Guille > > > El jue., 21 de may. de 2015 a la(s) 1:10 a. m., Cyril Ferlicot <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> escribiÃ³: > Guille asked me to add some feature for that, I added it to the TODO > list of Pillar but I don't have the time to do it now. > > On 21 May 2015 at 00:40, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > > Good. I would be pleased if you could show me what you've done so far so I don't waste time on things already solved. > > > > Norbert > > > >> Am 21.05.2015 um 00:03 schrieb stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>>: > >> > >> We did the same with guillermo but we are bullet profing the code before announcing it. > >> > >> Stef > >> > >> > >> Le 20/5/15 21:45, Norbert Hartl a Ã©crit : > >>> I've found some minutes today to play with pillar and mustache. I wanted to know how far I can go when doing some static site generation. The exercise was to simulate a page that has multiple components either in mustache or pillar format. I could do this > >>> > >>> | masterTemplate masterPillar masterDocument partialPillar partialTemplate finalPillar | > >>> > >>> masterTemplate := '<master> > >>> <head>{{{title}}}</head> > >>> <masterContent> > >>> {{{content}}} > >>> </masterContent> > >>> </master>'. > >>> > >>> masterPillar := '{{title: This is the title of the master!}} > >>> !masterheading > >>> > >>> This text is contained in the master pillar template > >>> > >>> {{{{{>phase2Template}}}}}'. > >>> > >>> partialPillar := '!{{{{{{title}}}}}} > >>> > >>> Some text in the partial template before the content... > >>> > >>> {{{{{{content}}}}}}} > >>> > >>> ... and after'. > >>> > >>> finalPillar := 'I''m a text in pillar format that was inserted in a partial mustache template generated from pillar that was inserted in a mustache master template in pillar format that was inserted in a master mustache template'. > >>> > >>> masterDocument := PRDocumentParser parse: masterPillar readStream. > >>> > >>> partialTemplate := PRHTMLWriter write: (PRDocumentParser parse: partialPillar readStream). > >>> > >>> phase1Result := masterTemplate asMustacheTemplate > >>> value: masterDocument properties, { > >>> 'content' -> (PRHTMLWriter write: masterDocument) } asDictionary. > >>> > >>> phase2Result := phase1Result asMustacheTemplate > >>> value: { > >>> 'title' -> 'A partial title'. > >>> 'content' -> (PRHTMLWriter write: (PRDocumentParser parse: finalPillar readStream)) } asDictionary > >>> partials: { > >>> 'phase2Template' -> partialTemplate } asDictionary. > >>> > >>> and got > >>> > >>> <master> > >>> <head>This is the title of the master!</head> > >>> <masterContent> > >>> <h1>masterheading</h1> > >>> <p>This text is contained in the master pillar template</p> > >>> <p><h1>A partial title</h1> > >>> <p>Some text in the partial template before the content...</p> > >>> <p><p>I'm a text in pillar format that was inserted in a partial mustache template generated from pillar that was inserted in a mustache master template in pillar format that was inserted in a master mustache template</p>}</p> > >>> <p>... and after</p></p> > >>> </masterContent> > >>> </master> > >>> > >>> That is really cool. Actually pillar and mustache are a good match. > >>> > >>> FYI, > >>> > >>> Norbert > >>> > >>> > >>> > >>> > >> > >> > > > > > > > > -- > Cheers > Cyril Ferlicot >

May 21, 2015

Re: [Pharo-users] [Pharo-dev] Next Pharo sprint & Moose dojo

by Jean-Christophe Bach

* Tudor Girba <tudor(a)tudorgirba.com> [21.05.2015. @13:04:19 +0200]: > Great! > > It would be great if you could test Moose 5.1 (stable) and let us know if > you encounter problems or if you commit new changes so that we can finally > release it. Do you think this would fit in your sprint/dojo? > > Cheers, > Doru OK, I note it. I think it is possible: it will depend on the available people but I think it can be the focus for Moose sprinters. JC

May 21, 2015

Re: [Pharo-users] Fun with pillar and mustache

by Cyril Ferlicot

Cocoon allow you to manage configuration with a .conf file and a STON syntax. You can see how Cocoon work with the class PRCocoonConfiguration of Pillar. I'll try to create a demo of Cocoon when I'll have the time. But to make simple you can define some parameters on your configuration and you give them a default value. Then if the user define a configuration Cocoon will change the default value for the value of the user. You can also use the value to create something else with CocoonSTONInterpreter. (For example on Pillar we check the outputType parameter and we choose or Writer in the PRCocoonInterpreter). And after you can use Cocoon parameters in your application. On 21 May 2015 at 14:01, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 21.05.2015 um 10:51 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi! > > Well, we have this secret really not mature project we started with stef a > couple of weeks ago. > > https://github.com/guillep/Ecstatic > > For now it has some simple features: > - you open an image and it will start serving your site + regenerating it > every couple of seconds (nice to debug and forget about running pillar > commands) > > > Cool. I was thinking about in-image editing of pillar with Rubric (or the > best available choice). Then you can generate on save. > > - we made some themes based on the one I made for dbxtalk, the one from > stef's personal website and esug website. > - we tried to push site configuration to the pillar.conf (title, > menu/navigation information, author/contact info) > > > I had a look at Cocoon but I'm not sure what purpose it serves. Maybe I need > to get to used to it. > > - another thing we wanted to push was the writing of plugins for the > moment taking benefit from the [[[eval=true]]]. We were thinking however on > making a special annotation for it. We have two really simple stupid > "plugins", one that shows a list of news/blog feed, one that generates a > list of publications based on a bib file using citezen. > > YES! That is exactly what I was looking for. Something that can be evaluated > dynamically. That opens a wide range of possibilities. > > I originally started this for the new dbxtalk site which is written > basically in pillar. > > http://dbxtalk.smallworks.eu/ > > You can see the source code of this site in here: > > https://github.com/guillep/DBXTalk/tree/gh-pages > > Nice! > > Of course, there you will notice a lot of *workarounds* to make it work. > I've made a list of those workarounds and sent them to Cyril to see if we > can have better support for them in pillar. > > I'd be pleased if you contribute and push it :). We have this trello board > to add ideas and manage our backlog > > https://trello.com/b/2t7qTWpp/ecstatic > > Thanks. I think I'll find some time this weekend to see how your project > fits into my needs. I'll be happy nagging you about some things ;) > > Norbert > > Guille > > > El jue., 21 de may. de 2015 a la(s) 1:10 a. m., Cyril Ferlicot > <cyril.ferlicot(a)gmail.com> escribiÃ³: >> >> Guille asked me to add some feature for that, I added it to the TODO >> list of Pillar but I don't have the time to do it now. >> >> On 21 May 2015 at 00:40, Norbert Hartl <norbert(a)hartl.name> wrote: >> > Good. I would be pleased if you could show me what you've done so far so >> > I don't waste time on things already solved. >> > >> > Norbert >> > >> >> Am 21.05.2015 um 00:03 schrieb stepharo <stepharo(a)free.fr>: >> >> >> >> We did the same with guillermo but we are bullet profing the code >> >> before announcing it. >> >> >> >> Stef >> >> >> >> >> >> Le 20/5/15 21:45, Norbert Hartl a Ã©crit : >> >>> I've found some minutes today to play with pillar and mustache. I >> >>> wanted to know how far I can go when doing some static site generation. The >> >>> exercise was to simulate a page that has multiple components either in >> >>> mustache or pillar format. I could do this >> >>> >> >>> | masterTemplate masterPillar masterDocument partialPillar >> >>> partialTemplate finalPillar | >> >>> >> >>> masterTemplate := '<master> >> >>> <head>{{{title}}}</head> >> >>> <masterContent> >> >>> {{{content}}} >> >>> </masterContent> >> >>> </master>'. >> >>> >> >>> masterPillar := '{{title: This is the title of the master!}} >> >>> !masterheading >> >>> >> >>> This text is contained in the master pillar template >> >>> >> >>> {{{{{>phase2Template}}}}}'. >> >>> >> >>> partialPillar := '!{{{{{{title}}}}}} >> >>> >> >>> Some text in the partial template before the content... >> >>> >> >>> {{{{{{content}}}}}}} >> >>> >> >>> ... and after'. >> >>> >> >>> finalPillar := 'I''m a text in pillar format that was inserted in a >> >>> partial mustache template generated from pillar that was inserted in a >> >>> mustache master template in pillar format that was inserted in a master >> >>> mustache template'. >> >>> >> >>> masterDocument := PRDocumentParser parse: masterPillar readStream. >> >>> >> >>> partialTemplate := PRHTMLWriter write: (PRDocumentParser parse: >> >>> partialPillar readStream). >> >>> >> >>> phase1Result := masterTemplate asMustacheTemplate >> >>> value: masterDocument properties, { >> >>> 'content' -> (PRHTMLWriter write: masterDocument) } >> >>> asDictionary. >> >>> >> >>> phase2Result := phase1Result asMustacheTemplate >> >>> value: { >> >>> 'title' -> 'A partial title'. >> >>> 'content' -> (PRHTMLWriter write: (PRDocumentParser >> >>> parse: finalPillar readStream)) } asDictionary >> >>> partials: { >> >>> 'phase2Template' -> partialTemplate } asDictionary. >> >>> >> >>> and got >> >>> >> >>> <master> >> >>> <head>This is the title of the master!</head> >> >>> <masterContent> >> >>> <h1>masterheading</h1> >> >>> <p>This text is contained in the master pillar template</p> >> >>> <p><h1>A partial title</h1> >> >>> <p>Some text in the partial template before the content...</p> >> >>> <p><p>I'm a text in pillar format that was inserted in a partial >> >>> mustache template generated from pillar that was inserted in a mustache >> >>> master template in pillar format that was inserted in a master mustache >> >>> template</p>}</p> >> >>> <p>... and after</p></p> >> >>> </masterContent> >> >>> </master> >> >>> >> >>> That is really cool. Actually pillar and mustache are a good match. >> >>> >> >>> FYI, >> >>> >> >>> Norbert >> >>> >> >>> >> >>> >> >>> >> >> >> >> >> > >> > >> >> >> >> -- >> Cheers >> Cyril Ferlicot >> > -- Cheers Cyril Ferlicot

May 21, 2015

Re: [Pharo-users] [OT] Pharo pi machine

by Pierce Ng

On Sun, May 17, 2015 at 02:26:12PM +0200, Torsten Bergmann wrote: > Got my Raspberry Pi B+ with a TontecÂ® 3.5 touch screen display > to bootstrap into Pharo. > > The Raspberry Pi from CI (https://ci.inria.fr/pharo/view/RaspberryPi/) > worked out of the box on Raspbian. Nice! Nice! My Pi 2 just arrived but I didn't order a touch screen display though. Must get that! Scratch is shipped with Raspbian and there are actually two versions of the Squeak VM in the distro; see /usr/lib/squeak. The newer version started the Pharo 4 image fine. Pierce

May 21, 2015