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

Re: [Pharo-users] Metacello does not load the expected version from ConfigOf

by Dale Henrichs

Usman, It is likely that Pharo3.0 is not using the latest version of Metacello. You should be able to upgrade to the latest versions following the install instructions for Pharo3.0[1]. Dale [1] https://github.com/dalehenrich/metacello-work#pharo30 On 1/2/15 6:23 AM, Usman Bhatti wrote: > Dale, > > Thanks for your detailed explanations. > > Metacello class in my image does not seem to define the messages > described in the documentation for handling downgrading and upgrading > conflicts: > https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… > > I am using Pharo 3.0 with Moose. > > Inline image 1 > > Did I miss something? > > regards, > Usman > > On Fri, Dec 19, 2014 at 7:00 PM, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>> wrote: > > Usman, > > With classic Metacello (using the `(ConfigurationOfxxx project > version: 'xxx') load` pattern) you can only downgrade via an > explicit load of a particular version of the project. When loading > projects indirectly via a project reference from another project > Metacello is biased towards upgrade. > > With the Metacello Scripting API[1], you may include an > #onDowngradeUseIncoming: clause to selectively permit downgrades: > > Metacello new > configuration: 'DummyParser'; > version: '1.0'; > repository: '???'; > onDowngradeUseIncoming: #('PetitParser'); > load. > > For additional downgrade options see[2]. > > Since you are interested in using a specific version of a project > you may also be interested in locking the project[3][4]. With a > `lock` Metacello will not upgrade or downgrade the project but > always `honor` the lock unless an #onLock: clause is used ... > > Note that for `locking` to work, you must use the Metacello > Scripting API to do all of your project loads ... > > Dale > > [1] > https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… > [2] > https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… > [3] > https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… > [4] > https://github.com/dalehenrich/metacello-work/blob/master/docs/LockCommandR… > > > > On 12/19/2014 07:44 AM, Usman Bhatti wrote: >> Hi all, >> >> I am trying to load a specific version of PetitParser in a Moose >> image. A Moose image comes with the latest development version of >> PetitParser. So, I am trying to downgrade to an older version. >> So, when I load the version manually, older versions of the >> packages are loaded: >> (ConfigurationOfPetitParser project version: '1.51') load >> >> But when I try to load the same version within my ConfigOf the >> expected packages are not loaded and list of the PetitParser >> packages loaded remains unchanged. Here is how my baseline looks >> like: >> >> ConfigurationOfDummyParser>>baseline01: spec >> <version: '0.1-baseline'> >> >> spec for: #'common' do: [ >> spec blessing: #'baseline'. >> spec project: 'PetitParser' with: [ >> spec >> className: #ConfigurationOfPetitParser; >> versionString: '1.51'; >> repository: 'http://smalltalkhub.com/mc/Moose/PetitParser/main/' >> ]. ]. >> >> I also tried creating a version but it didn't help. >> >> ConfigurationOfDummyParser>>version10: spec >> <version: '1.0' imports: #('0.1-baseline' )> >> >> spec for: #'common' do: [ >> spec blessing: #'stable'. >> spec description: 'version 1.0'. >> spec author: 'usmanbhatti'. >> spec timestamp: '12/19/2014 16:35'. >> spec project: 'PetitParser' with: '1.51'. ]. >> >> I also had a look at the package the configuration tries to load >> and the list shows correct packages to be loaded (see screenshot). >> >> Does anyone have an idea what may be problematic in my code or >> that of Metacello? I am attaching the code of my ConfigOf for a >> Moose image. >> >> Thanks in advance. >> >> UsmanInline image 1 >> >> > >

Jan. 2, 2015

Re: [Pharo-users] Metacello does not load the expected version from ConfigOf

by Usman Bhatti

Dale, Thanks for your detailed explanations. Metacello class in my image does not seem to define the messages described in the documentation for handling downgrading and upgrading conflicts: https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… I am using Pharo 3.0 with Moose. [image: Inline image 1] Did I miss something? regards, Usman On Fri, Dec 19, 2014 at 7:00 PM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Usman, > > With classic Metacello (using the `(ConfigurationOfxxx project version: > 'xxx') load` pattern) you can only downgrade via an explicit load of a > particular version of the project. When loading projects indirectly via a > project reference from another project Metacello is biased towards upgrade. > > With the Metacello Scripting API[1], you may include an > #onDowngradeUseIncoming: clause to selectively permit downgrades: > > Metacello new > configuration: 'DummyParser'; > version: '1.0'; > repository: '???'; > onDowngradeUseIncoming: #('PetitParser'); > load. > > For additional downgrade options see[2]. > > Since you are interested in using a specific version of a project you may > also be interested in locking the project[3][4]. With a `lock` Metacello > will not upgrade or downgrade the project but always `honor` the lock > unless an #onLock: clause is used ... > > Note that for `locking` to work, you must use the Metacello Scripting API > to do all of your project loads ... > > Dale > > [1] > https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… > [2] > https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… > [3] > https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… > [4] > https://github.com/dalehenrich/metacello-work/blob/master/docs/LockCommandR… > > > On 12/19/2014 07:44 AM, Usman Bhatti wrote: > > Hi all, > > I am trying to load a specific version of PetitParser in a Moose image. > A Moose image comes with the latest development version of PetitParser. So, > I am trying to downgrade to an older version. So, when I load the version > manually, older versions of the packages are loaded: > (ConfigurationOfPetitParser project version: '1.51') load > > But when I try to load the same version within my ConfigOf the expected > packages are not loaded and list of the PetitParser packages loaded remains > unchanged. Here is how my baseline looks like: > > ConfigurationOfDummyParser>>baseline01: spec > <version: '0.1-baseline'> > > spec for: #'common' do: [ > spec blessing: #'baseline'. > spec project: 'PetitParser' with: [ > spec > className: #ConfigurationOfPetitParser; > versionString: '1.51'; > repository: 'http://smalltalkhub.com/mc/Moose/PetitParser/main/' ]. ]. > > I also tried creating a version but it didn't help. > > ConfigurationOfDummyParser>>version10: spec > <version: '1.0' imports: #('0.1-baseline' )> > > spec for: #'common' do: [ > spec blessing: #'stable'. > spec description: 'version 1.0'. > spec author: 'usmanbhatti'. > spec timestamp: '12/19/2014 16:35'. > spec project: 'PetitParser' with: '1.51'. ]. > > I also had a look at the package the configuration tries to load and the > list shows correct packages to be loaded (see screenshot). > > Does anyone have an idea what may be problematic in my code or that of > Metacello? I am attaching the code of my ConfigOf for a Moose image. > > Thanks in advance. > > Usman[image: Inline image 1] > > > > >

Jan. 2, 2015

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by stepharo

thanks I will have a look. Now busy building furnitures :) Le 2/1/15 08:36, Daniel Lyons a Ã©crit : > >> On Dec 28, 2014, at 3:17 PM, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> I would be interested by having an example that I could use to >> rewrite the spec documentation: >> - would be good to have a kind of container relationships >> to be able to display multiple list >> - the model should not be too complex to explain. >> >> So if you have data and idea I'm all ears. > > I have about 1/2 of an application written to implement PERT, which is > something management types study for doing project cost estimation, > but usually don't use in reality. It has a nice container hierarchy > (Project > Phase > Task > Task > ... > Task). I have part of the UI > written in Glamour and part in Spec, but it isn't finished. I'm using > this as a tutorial to teach my wife Pharoâalthough I'm probably not so > great at it that I should be teaching anybody. :) The tutorial isn't > as far along as the application and is probably wrongly titled at this > point. > > I'm happy to give away the code and the tutorial but I'm a little > stuck now since we have just had a baby and are now preparing to move > in three weeks. So I apologize for the rough state of affairs, but > since you asked I only hope it may be better than nothing. > > The tutorial can be read here: http://st.7gf.org/PERT/ > PDF: http://st.7gf.org/PERT/PERT.pdf > Markdown source: http://st.7gf.org/PERT/PERT.md > > Additionally I have a whiteboard capture of the interface I envision > with Glamour (which may or may not be appropriate). The size is quite > large despite the low quality, my apologies: > > http://st.7gf.org/PERT/project-window.jpg > http://st.7gf.org/PERT/simulation-window.jpg > http://st.7gf.org/PERT/project-graph-diagram.jpg > > It would be hard to come up with a more "boring" and "business" > application domain than thisâ¦ but for management people the problem is > pretty well-known and for my wife, her only prior programming > experience (not counting Excel) is C and the experience has been > positive for her so far. She's also greatly enjoying going through my > paper copy of Pharo by Example and the built-in tutorial. > > The basic concept, in case anyone is interested, is that you can form > a directed acyclic graph between subtasks and then using min/max cost > estimates, determine which tasks are "critical" and which tasks can be > late without affecting the deadline or budget. The "project window" > above uses a GLFinder-like approach to allow drilling down into > subtasks from projects and phases. This means you're stuck with a tree > instead of a DAG. > > The target level of sophistication for the final application is one > that can use expected costs and a beta distribution to simulate > thousands of different possible outcomes and then aggregate from there > to see which tasks are likely to be troublesome or have bad estimates. > This is what is pictured in the simulation-window mockup. > > The project graph diagram is just a sketch of something that would be > trivial to do with Roassal. > > The project and task/activity objects should be fairly obvious. Phase > is just recognition of the idea that projects are usually implemented > in phases, and you usually have to complete one phase before starting > the next: e.g., you must have made the prototype before you can put it > into production. This layer is unnecessary from a computational point > of view (there's nothing like it in the wiki page for PERT either) but > it's a helpful organizational tool, plus it lets you create a nice > boundary to get back some of the nice things about having a DAG that > you lose with a tree representation. > > I don't know if this is what you're looking for or not but here it is. > > All the best, > > â > Daniel Lyons > > >

Jan. 2, 2015

Re: [Pharo-users] Traveling from Pharo Days to FOSDEM

by Rafael Luque

Thank you guys! Phil thank you for your offer. We talk about it in Pharo Days. See you soon. 2014-12-31 17:33 GMT+01:00 FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com>: > With the high speed train "Lille Europe" to "Brussels South" takes around > 40 minutes. > You can check fares and book tickets on https://www.b-europe.com > > @Phil do you go back to Brussels from Lille on Friday night? > > On Wed, Dec 31, 2014 at 1:37 PM, Rafael Luque < > rafael.luque.leiva(a)gmail.com> wrote: > >> Hi Pharoers, >> >> I will attend Pharo Days with a friend and after the conference we'd like >> to attend FOSDEM. Which the best way to travel to Brussels from Lille? >> >> Thank you and see you in Pharo Days. >> > >

Jan. 2, 2015

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by Daniel Lyons

All that and I forgot to include the link to the code. http://smalltalkhub.com/#!/~DanielLyons/PERT <http://smalltalkhub.com/#!/~DanielLyons/PERT> â Daniel Lyons

Jan. 2, 2015

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by Daniel Lyons

> On Dec 28, 2014, at 3:17 PM, stepharo <stepharo(a)free.fr> wrote: > > I would be interested by having an example that I could use to rewrite the spec documentation: > - would be good to have a kind of container relationships > to be able to display multiple list > - the model should not be too complex to explain. > > So if you have data and idea I'm all ears. I have about 1/2 of an application written to implement PERT, which is something management types study for doing project cost estimation, but usually don't use in reality. It has a nice container hierarchy (Project > Phase > Task > Task > ... > Task). I have part of the UI written in Glamour and part in Spec, but it isn't finished. I'm using this as a tutorial to teach my wife Pharoâalthough I'm probably not so great at it that I should be teaching anybody. :) The tutorial isn't as far along as the application and is probably wrongly titled at this point. I'm happy to give away the code and the tutorial but I'm a little stuck now since we have just had a baby and are now preparing to move in three weeks. So I apologize for the rough state of affairs, but since you asked I only hope it may be better than nothing. The tutorial can be read here: http://st.7gf.org/PERT/ <http://st.7gf.org/PERT/> PDF: http://st.7gf.org/PERT/PERT.pdf <http://st.7gf.org/PERT/PERT.pdf> Markdown source: http://st.7gf.org/PERT/PERT.md <http://st.7gf.org/PERT/PERT.md> Additionally I have a whiteboard capture of the interface I envision with Glamour (which may or may not be appropriate). The size is quite large despite the low quality, my apologies: http://st.7gf.org/PERT/project-window <http://st.7gf.org/PERT/project-window>.jpg http://st.7gf.org/PERT/simulation-window.jpg <http://st.7gf.org/PERT/simulation-window.jpg> http://st.7gf.org/PERT/project-graph-diagram.jpg It would be hard to come up with a more "boring" and "business" application domain than thisâ¦ but for management people the problem is pretty well-known and for my wife, her only prior programming experience (not counting Excel) is C and the experience has been positive for her so far. She's also greatly enjoying going through my paper copy of Pharo by Example and the built-in tutorial. The basic concept, in case anyone is interested, is that you can form a directed acyclic graph between subtasks and then using min/max cost estimates, determine which tasks are "critical" and which tasks can be late without affecting the deadline or budget. The "project window" above uses a GLFinder-like approach to allow drilling down into subtasks from projects and phases. This means you're stuck with a tree instead of a DAG. The target level of sophistication for the final application is one that can use expected costs and a beta distribution to simulate thousands of different possible outcomes and then aggregate from there to see which tasks are likely to be troublesome or have bad estimates. This is what is pictured in the simulation-window mockup. The project graph diagram is just a sketch of something that would be trivial to do with Roassal. The project and task/activity objects should be fairly obvious. Phase is just recognition of the idea that projects are usually implemented in phases, and you usually have to complete one phase before starting the next: e.g., you must have made the prototype before you can put it into production. This layer is unnecessary from a computational point of view (there's nothing like it in the wiki page for PERT either) but it's a helpful organizational tool, plus it lets you create a nice boundary to get back some of the nice things about having a DAG that you lose with a tree representation. I don't know if this is what you're looking for or not but here it is. All the best, â Daniel Lyons

Jan. 2, 2015

what is the state of remote prowsing and debugging?

by Martin BÃ¤hr

hi, i have read some discussions about this topic going back half a decade ago, and i wonder if any progress has been made since. is anyone still working on this? the use-case i am interested in is development on headless servers. i found that VNC is just to slow. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org BLUG secretary beijinglug.org foresight developer foresightlinux.org realss.com unix sysadmin Martin BÃ¤hr working in china http://societyserver.org/mbaehr/

Jan. 2, 2015

Re: [Pharo-users] PetitParser and PPBrowser in Pharo 3.0

by stepharo

The postload action of roassal could be wirtten in a way to set the Freetype Le 31/12/14 14:14, Tudor Girba a Ã©crit : > Hi, > > PPBrowser uses Roassal which relies on the Athens canvas which > requires FreeType fonts :). > > To fix this, you can go to Settings: > - Make Use Free type ... true > - Choose a Free type font as the default one. > > Or you can just use the Moose 5.0 image: > http://moosetechnology.org/#install > > Or you can use some ready made setup script we have in Moose: > Gofer new > smalltalkhubUser: 'Moose' project: 'GToolkit'; > package: 'GT-Setup'; > load. > #GTImageSetupCommandLineHandler asClass activateWithoutSaving > > Cheers, > Doru > > > > On Wed, Dec 31, 2014 at 2:10 PM, Hartmut <krasemann(a)acm.org > <mailto:krasemann@acm.org>> wrote: > > Hi Jan, > > since a while I get a MessageNotUnderstood on PPBrowser open after > ConfigurationOfPetitParser loadDevelopment. > Has to do with fonts. > Debugger Stack fueled out can be accessed here: > https://dl.dropboxusercontent.com/u/4548797/Debugger-Stack-StrikeFont-2014-… > > Regards, Hartmut > > Am 16.12.14 14:34, schrieb Jan KurÅ¡: >> Hi, >> >> Anyone experience with Athens can help with the first issue? >> TRLabelShape>>drawOn: seem to be somehow responsible, but I don't >> see into this :( >> >> Regarding to the second issue, there are some cases, when one >> really needs a start rule, e.g when computing follow. Yet I >> updated the code so that it handles missing start rule a bit better. >> >> Please, let me know, if you have some other ideas/suggestions/issues. >> >> Regards, >> Jan >> >> On 9 December 2014 at 15:17, Hartmut <krasemann(a)acm.org >> <mailto:krasemann@acm.org>> wrote: >> >> Hi to all, >> >> I'm working with PetitParser in a Pharo 3 image. >> Until now I had to do without the PPBrowser which I loved in >> Pharo 2. >> >> On forum.world.st <http://forum.world.st> I now found the >> hint by Jan Kurs to install all of the Petit suite: >> >> > "Configuration should be loaded like this:" >> > Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; >> > configurationOf: #PetitParser; load. >> > >> > "All the petit parser suite:" >> > ConfigurationOfPetitParser loadDevelopment. >> >> Apart from the fact that this installed a real lot into my >> image, I notice the following problems >> in PPBrowser: >> >> 1. The map of none of the 18 parsers included, is displayed >> (it becomes red crossed). >> However, this was the most useful part of it >> >> 2. My interrelated parsers consist of a tree of parsers where >> each leave has its own start clause. >> They define related languages. It makes no sense to add a >> /start/ clause to the root. >> However, without such a meaningless /start/ clause, only >> the /source/ is displayed, >> neither /graph, example, first/ or /follow/ of any clause. >> (this can be reproduced when you move >> PPJsonGrammar>>start to PPJsonParser) >> >> I like the style of having a grammar class above a parser (or >> compiler) class. >> This is as seen in most of the accompanying parsers. >> My preferred petit parser style comprises: >> a) keeping grammar rules (without ==>) in the upper >> classes of the grammar hierarchy tree, >> such that we find the complete grammar there (without >> the /start/ clause). >> b) keeping replacement rules (using ==>) as low as >> possible the grammar hierarchy tree >> c) writing the start clause to the class that is actually >> called. (this gives different entries >> in a grammar allowing for different languages with >> grammar subsets) >> >> Is there an idea to have 1. and/or 2. resolved? >> >> Hartmut >> >> -- >> Hartmut Krasemannâ¨ >> KÃ¶nigsberger Str. 41 c >> â¨D 22869 Schenefeldâ¨ >> Tel. 040.8307097â¨ >> Mobil 0171.6451283â¨ >> krasemann(a)acm.org <mailto:krasemann@acm.org> >> > > -- > Hartmut Krasemannâ¨ > KÃ¶nigsberger Str. 41 c > â¨D 22869 Schenefeldâ¨ > Tel. 040.8307097â¨ > Mobil 0171.6451283â¨ > krasemann(a)acm.org <mailto:krasemann@acm.org> > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Jan. 1, 2015

Re: [Pharo-users] PetitParser problem with plus

by stepharo

Le 31/12/14 16:37, Jan KurÅ¡ a Ã©crit : > You mean deep into pharo? Or something else? I can do this... Yes I mean let us improve **OUR** documentation. Soon we will release an official version of Deep into Pharo. Then we will convert it to pillar and this means that we will all the Pharo books online and on different formats. Stef > > On 21 December 2014 at 13:27, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Could one of you write a small paragraph for the petit parser chapter? > > Le 18/12/14 09:07, Jan KurÅ¡ a Ã©crit : >> Exactly... >> >> This happens so often that we should add some warning somewhere >> in these cases.... >> >> >> Cheers, >> Jan >> >> On 18 December 2014 at 08:36, Guillaume Larcheveque >> <guillaume.larcheveque(a)gmail.com >> <mailto:guillaume.larcheveque@gmail.com>> wrote: >> >> So you just have to remove the #star in notA or replace it by >> #plus to makes it succeed only when it consume at least one >> character >> >> 2014-12-18 7:54 GMT+01:00 Guillaume Larcheveque >> <guillaume.larcheveque(a)gmail.com >> <mailto:guillaume.larcheveque@gmail.com>>: >> >> With x, x it will only go to 2 level deep. >> >> With the plus you allow to go as far as the x rule >> succeed and your x rule always succeed because notA >> always succeed due to the star without consuming anything >> so you fall into infinite loop. >> >> 2014-12-18 6:47 GMT+01:00 James Foster >> <Smalltalk(a)jgfoster.net <mailto:Smalltalk@jgfoster.net>>: >> >> There is something about plus that I donât >> understand. In the following code if I parse for (x , >> x) then I get what I expect. If I parse for (x plus) >> then the image hangs. What am I doing wrong? >> >> James >> >> | a notA x y | >> a := $a asParser. >> notA := $a asParser negate star flatten. >> x := a / notA. >> y := x , x. âworks fineâ >> y := x plus. ânever finishesâ >> ^y end parse: 'abâ. >> >> >> >> >> -- >> *Guillaume Larcheveque* >> >> >> >> -- >> *Guillaume Larcheveque* >> > >

Jan. 1, 2015

Re: [Pharo-users] Implementation of book editor for PillarHub application

by stepharo

https://ci.inria.fr/pharo-contribution/job/Pier3/ https://ci.inria.fr/pharo-contribution/job/PierMongoVoyage/ Le 1/1/15 09:00, stepharo a Ã©crit : > Hi > > This night I was thinking that what would be good is to have a look at > Pier again. > http://www.piercms. > Why: > Solid > Proven > esteban made a version working with Magritte 3, saved with Voyage, > we can have Reef components inside Pier (reef are components embedding > Javascript). > We extracted Pillar from Pier and it could be nice to be able to plug > pillar in Pier. > > http://www.piercms.com/download does not work. > I will ask esteban. > > Stef > > > Le 28/12/14 15:21, Flayer a Ã©crit : >> Hello everyone! My name is Maxim Skripnik, and I wish to tell you >> about my >> first project that deals with Pharo and Pillar world. >> >> To make a long story short, it's about extension of functional for >> web-application called "PillarHub" that is written fully on Pharo with >> Seaside's tools. In substance, today it's a editor and viewer for >> articles >> written on Pillar markup but I will add opportunity to compile complete >> books from them. >> >> Anyway, if you are interested in it, you may find full description * >> here >> <http://pillarhub.pharocloud.com/hub/MaximSkripnik/bookcompilerintro> *. >> >> There, on PillarHub, I will report on progress, so check for updates >> there. >> >> Feel free to comment and share your ideas with me, I would be very >> glad to >> see some. >> >> Thank you for your attention! >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Implementation-of-book-editor-for-PillarHub-applicati… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> > > > >

Jan. 1, 2015