May 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Status of Rome?

by StÃ©phane Ducasse

somehow yes. Cyrille is working on it and he showed me some results using or not the rome pluging On May 22, 2010, at 10:50 AM, Igor Stasenko wrote: > On 22 May 2010 11:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> in Athens in squeaksource. >> We will flush all the other repositories and only keep this one. >> We will put the old files probably there too. >> >> Why that? >> Because the code was full of half done class, broken methods.... >> Tweak copied and pasted code from Squeak >> > > Yes, it requires some cleanup/reorganization. > So, SqS/Athens is the latest & current state of art? > >> Stef >> >> On May 22, 2010, at 7:29 AM, Igor Stasenko wrote: >> >>> Hello guys, >>> >>> i seen there are some recent activity with Rome in Pharo, >>> but i found that things are now scattered over a different repositories, >>> and its hard to find out, what version is latest and which one i could use. >>> >>> I found that the latest things is in a SqS/PharoTaskForces/Rome, >>> which is a merge of all Rome-XXX packages into a single one. >>> Is this most recent thing you are working on? >>> >>> Actually, all i need is just a reference canvas, >>> but it would be cool if i could run some working code & examples. :) >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 22, 2010

Re: [Pharo-project] CommandShell

by Schwab,Wilhelm K

Laurent, I have been getting snagged on this for a while now: http://article.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/15680 CommandShell itself is of no interest to me (at least not yet), but I load it to get pipes. I think this could be fixedm, or at least improved, by simply not trying to open the shell on initialization. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of laurent laffont [laurent.laffont(a)gmail.com] Sent: Saturday, May 22, 2010 3:30 AM To: An open mailing list to discuss any topics related to an open-source Smalltalk Subject: [Pharo-project] CommandShell Hi, I'm trying to load CommandShell into Pharo. I have the error: This package depends on the following classes: PluggableTextController PluggableTextView You must resolve these dependencies before you will be able to load these definitions: ShellWindowView ...... Do you know where I can find PluggableTextController and PluggableTextView ? Or maybe we can use other classes to make it compatible with Pharo Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

May 22, 2010

Re: [Pharo-project] Styler?

by Lukas Renggli

Why is a NullStyler necessary when Shout can load without overriding any code? Lukas 2010/5/22 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Sat, May 22, 2010 at 10:09 AM, stephane ducasse > <stephane.ducasse(a)free.fr> wrote: >> >> Hi guys >> >> what do we do with shout? >> Squeak introduced it directly in the system. Now I was thinking that what >> could be a solution is to have a >> default API/null pattern class that could be in the core and that when >> Shout gets loaded the shout class is used instead. > > Wasn't this the idea of ToolSet ?Â but sucks...(as we said few threads ago) > >> >> Now we could add Shout to the TextEditor package but I would like to >> understand how we can do it without. > > This is an excellent question and idea. Using some kind of Strategy pattern > or similar may help. > But I 9999999999^9999999Â not to put Shout neither Style in Core ;) > > I haven't look anything about the code. I have no idea. But cannot CodeMorph > or whatever have a class variable that holds the Styler? > Then we create, as you said, a NullStyler for core. Shout implements its own > Styler and when loaded, it does: > CodeMorph styler: ShoutStylerÂ or similar. > > I guess the NullStyler is better than having to do everywhereÂ codeMorph > styler isNil ifFalse: [ .... > > Cheers > > Mariano > > >> >> And also it is interesting to see if one day we will need selector >> namespace or something like that to deal well with extensions. >> Stef >> >> in PharoCore-1.1 11367 >> >> Fails as CodeMorph#stylerClass is not initialized. And no *Styler* class >> exists on PharoCore.... >> >> To make test passes on Pharo I've written >> >> CodeMorph#defaultStylerClass >> Â ^ SHTextStylerST80 >> >> CodeMorph#stylerClass >> Â ^ stylerClass ifNil: [stylerClass := self defaultStylerClass]. >> >> the solution proposed by laurent only works when shout is loaded and this >> is not always the case. >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

May 22, 2010

Re: [Pharo-project] Cross-fork Metacello configurations

by Hannes Hirzel

On 5/21/10, Dale Henrichs <dhenrich(a)vmware.com> wrote: > I had suggested that they not use the ConfigurationOf prefix for the Squeak > configuration package so that cross platform configurations could continue > to be used ... I would hope that folks continue to to create cross platform > packages ... the onus on copying shouldn't be on the developer, but the > folks that want a managed list of configs:) Yes, ConfigurationOfABC should remain as is. A configuration of a package is one thing and a managed list of configurations is something on a next level. > I would think that the managed list could be harvested from the > ConfigurationOf configs without any direct developer involvement...afterall > computers should be used for the things they are good at:) Interesting idea. It seems to me that the only thing which needs to be done is to remove instance variable 'project' and class 'LastVersionLoad' from ConfigurationOfABC and then move ConfigurationOfABC to be a subclass of MetacelloConfiguration > It will be interesting to see how the managed list idea evolves... Yes, indeed. Great work that you have started, Dale. I realise this a bit late but seemingly not too late :-)

May 22, 2010

Re: [Pharo-project] Styler?

by Mariano Martinez Peck

On Sat, May 22, 2010 at 10:09 AM, stephane ducasse <stephane.ducasse(a)free.fr > wrote: > Hi guys > > what do we do with shout? > Squeak introduced it directly in the system. Now I was thinking that what > could be a solution is to have a > default API/null pattern class that could be in the core and that when > Shout gets loaded the shout class is used instead. > Wasn't this the idea of ToolSet ? but sucks...(as we said few threads ago) > Now we could add Shout to the TextEditor package but I would like to > understand how we can do it without. > This is an excellent question and idea. Using some kind of Strategy pattern or similar may help. But I 9999999999^9999999 not to put Shout neither Style in Core ;) I haven't look anything about the code. I have no idea. But cannot CodeMorph or whatever have a class variable that holds the Styler? Then we create, as you said, a NullStyler for core. Shout implements its own Styler and when loaded, it does: CodeMorph styler: ShoutStyler or similar. I guess the NullStyler is better than having to do everywhere codeMorph styler isNil ifFalse: [ .... Cheers Mariano > And also it is interesting to see if one day we will need selector > namespace or something like that to deal well with extensions. > Stef > > in PharoCore-1.1 11367 > > Fails as CodeMorph#stylerClass is not initialized. And no *Styler* class > exists on PharoCore.... > > To make test passes on Pharo I've written > > CodeMorph#defaultStylerClass > ^ SHTextStylerST80 > > CodeMorph#stylerClass > ^ stylerClass ifNil: [stylerClass := self defaultStylerClass]. > > the solution proposed by laurent only works when shout is loaded and this > is not always the case. > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 22, 2010

Re: [Pharo-project] Where should I put ConfigurationOfGLMorphic

by Mariano Martinez Peck

2010/5/22 Javier PimÃ¡s <elpochodelagente(a)gmail.com> > Ok, I was doing it wrong, trying to put Conf.. in the same package as > GLMorphic. I hadn't undestood that the left part of the repo window (when > you click open) were actually packages and that you could create many > packages and upload them to the same repository... now its done right! > There was an ANN last week about a new draft about Monticello for Pharo By Example 2 ;) Now you have Monticello and Metacello chapters haha https://gforge.inria.fr/frs/download.php/27018/Monticello.pdf Cheers Mariano > > Thank's all for the help. > > > Javier. > > 2010/5/21 Mariano Martinez Peck <marianopeck(a)gmail.com> > >> >> >> 2010/5/21 Javier PimÃ¡s <elpochodelagente(a)gmail.com> >> >>> Wow, this is brilliant! it it'd have been of great help yesterday ;) >>> >> >> I am glad you like it. >> >> >>> I gave it a quick look an there's one thing I still don't know >>> how to do. I need to put ConfigurationOfGLMorphic inside GLMorphic package, >>> but as it isn't in any GLMorphic-* category it isn't automatically detected >>> by monticello. I don't see any button to add a class or category to the >>> package. What should I do? >>> >>> >> I don't know if I understood. I would recommend just to create a >> particular package in the same repository called ConfigurationOfGLMorphic >> where you put your class. Then your class will be in such package and will >> have also that category. This is what Henrik told you. >> >> Tell us if it is not yet clear. >> >> Cheers >> >> Mariano >> >> >>> thanks, >>> javier. >>> >>> 2010/5/21 Mariano Martinez Peck <marianopeck(a)gmail.com> >>> >>> >>>> >>>> 2010/5/21 Javier PimÃ¡s <elpochodelagente(a)gmail.com> >>>> >>>>> Hi, I made a very basic ConfigurationOfGLMorphic that manages it's >>>>> dependency on FFI. Where should I upload this configuration now? >>>>> >>>>> >>>> Hi Javier. Here I attach a first not-yet-draft chapter of Metacello. >>>> There you will find the answer ;) (feedback is welcome!!!) >>>> >>>> But in sumary, you should commit to the repository of the same project. >>>> In your case, as Igor said, to GLMorphic repository. >>>> There you can commit your development changes to the configuration. Once >>>> you have a released version, you just copy it to MetacelloConfiguration >>>> repository. >>>> >>>> Cheers >>>> >>>> Mariano >>>> >>>> >>>> >>>> >>>>> Regards, >>>>> Javier. >>>>> >>>>> -- >>>>> Javier PimÃ¡s >>>>> Ciudad de Buenos Aires >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> Javier PimÃ¡s >>> Ciudad de Buenos Aires >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 22, 2010

Re: [Pharo-project] Status of Rome?

by Igor Stasenko

On 22 May 2010 11:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > in Athens in squeaksource. > We will flush all the other repositories and only keep this one. > We will put the old files probably there too. > > Why that? > Because the code was full of half done class, broken methods.... > Tweak copied and pasted code from Squeak > Yes, it requires some cleanup/reorganization. So, SqS/Athens is the latest & current state of art? > Stef > > On May 22, 2010, at 7:29 AM, Igor Stasenko wrote: > >> Hello guys, >> >> i seen there are some recent activity with Rome in Pharo, >> but i found that things are now scattered over a different repositories, >> and its hard to find out, what version is latest and which one i could use. >> >> I found that the latest things is in a SqS/PharoTaskForces/Rome, >> which is a merge of all Rome-XXX packages into a single one. >> Is this most recent thing you are working on? >> >> Actually, all i need is just a reference canvas, >> but it would be cool if i could run some working code & examples. :) >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

May 22, 2010

Re: [Pharo-project] Adding BlockClosure>>timeToRunWithoutGC [WAS] Fwd: [squeak-dev] The Inbox: Kernel-ul.251.mcz

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=2463 \ On May 21, 2010, at 11:09 PM, Mariano Martinez Peck wrote: > Hi folks. I saw this method in Squeak and seems interesting to include in Pharo too. What do you think ? > > Cheers > > Mariano > > > > > ---------- Forwarded message ---------- > From: Michael van der Gulik <mikevdg(a)gmail.com> > Date: Mon, Sep 28, 2009 at 2:58 AM > Subject: Re: [squeak-dev] The Inbox: Kernel-ul.251.mcz > To: squeak-dev(a)lists.squeakfoundation.org > > > > > On Mon, Sep 28, 2009 at 1:38 PM, <commits(a)source.squeak.org> wrote: > Item was added: > + ----- Method: BlockClosure>>timeToRunWithoutGC (in category 'evaluating') ----- > + timeToRunWithoutGC > + "Answer the number of milliseconds taken to execute this block without GC time." > + > + ^(SmalltalkImage current vmParameterAt: 8) + > + (SmalltalkImage current vmParameterAt: 10) + > + self timeToRun - > + (SmalltalkImage current vmParameterAt: 8) - > + (SmalltalkImage current vmParameterAt: 10) > + ! > > > > > Could this method be put somewhere other than in Kernel, say for example in a separate profiling package? > > Gulik. > > > > -- > http://gulik.pbwiki.com/ > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 22, 2010

[Pharo-project] Styler?

by stephane ducasse

Hi guys what do we do with shout? Squeak introduced it directly in the system. Now I was thinking that what could be a solution is to have a default API/null pattern class that could be in the core and that when Shout gets loaded the shout class is used instead. Now we could add Shout to the TextEditor package but I would like to understand how we can do it without. And also it is interesting to see if one day we will need selector namespace or something like that to deal well with extensions. Stef in PharoCore-1.1 11367 Fails as CodeMorph#stylerClass is not initialized. And no *Styler* class exists on PharoCore.... To make test passes on Pharo I've written CodeMorph#defaultStylerClass ^ SHTextStylerST80 CodeMorph#stylerClass ^ stylerClass ifNil: [stylerClass := self defaultStylerClass]. the solution proposed by laurent only works when shout is loaded and this is not always the case.

May 22, 2010

Re: [Pharo-project] Status of Rome?

by StÃ©phane Ducasse

in Athens in squeaksource. We will flush all the other repositories and only keep this one. We will put the old files probably there too. Why that? Because the code was full of half done class, broken methods.... Tweak copied and pasted code from Squeak Stef On May 22, 2010, at 7:29 AM, Igor Stasenko wrote: > Hello guys, > > i seen there are some recent activity with Rome in Pharo, > but i found that things are now scattered over a different repositories, > and its hard to find out, what version is latest and which one i could use. > > I found that the latest things is in a SqS/PharoTaskForces/Rome, > which is a merge of all Rome-XXX packages into a single one. > Is this most recent thing you are working on? > > Actually, all i need is just a reference canvas, > but it would be cool if i could run some working code & examples. :) > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 22, 2010