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

Re: [Pharo-project] Managing Pharo external packages with Metacello, please read!

by Geert Claes

Is there no clean way to "not" have version numbers in the Repository name? Configuration packages like ConfigurationOfSeaside28 and ConfigurationOfSeaside30 just don't look right either. -- View this message in context: http://forum.world.st/Managing-Pharo-external-packages-with-Metacello-pleas… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 17, 2010

Re: [Pharo-project] Managing Pharo external packages with Metacello, please read!

by Mariano Martinez Peck

On Mon, May 17, 2010 at 3:50 PM, Geert Claes <geert.wl.claes(a)gmail.com>wrote: > > > StÃ©phane Ducasse wrote: > > > > Because I want to have them close to the Pharo repositories :) > > "Everything was carefully thought" (tm) > > > > Fair enough ... how about PharoConfigurationRepository :) > > I have read all replies here and I am still a bit confused, so is it the > idea to have a separate repository per release e.g. Pharo10Configurations, > Pharo11Configurations etc? > yes > -- > View this message in context: > http://forum.world.st/Managing-Pharo-external-packages-with-Metacello-pleas… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 17, 2010

Re: [Pharo-project] Class>>rename:

by Igor Stasenko

On 17 May 2010 16:54, Fernando olivero <oliverof(a)lu.unisi.ch> wrote: > Class>>rename: aString > Â Â Â Â .. > Â Â Â Â self environment renameClass: self from: oldName. > Â Â Â Â .. > > > I've believe that when the method Â SystemDictionary>>classRenamed: from: to: inCategory: Â is sent , the rename get's logged. > > Is that what you were asking? > yes > Fernando > > > > On May 17, 2010, at 1:11 PM, Igor Stasenko wrote: > >> Is #rename: still untracked by changes log? >> >> >> 2010/5/17 Fernando olivero <oliverof(a)lu.unisi.ch>: >>> Issue 2437. >>> Fix in Pharo Inbox: >>> >>> Name: Kernel-FernandoOlivero.662 >>> Author: FernandoOlivero >>> >>> >>> >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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 17, 2010

Re: [Pharo-project] Class>>rename:

by Fernando olivero

Class>>rename: aString .. self environment renameClass: self from: oldName. .. I've believe that when the method SystemDictionary>>classRenamed: from: to: inCategory: is sent , the rename get's logged. Is that what you were asking? Fernando On May 17, 2010, at 1:11 PM, Igor Stasenko wrote: > Is #rename: still untracked by changes log? > > > 2010/5/17 Fernando olivero <oliverof(a)lu.unisi.ch>: >> Issue 2437. >> Fix in Pharo Inbox: >> >> Name: Kernel-FernandoOlivero.662 >> Author: FernandoOlivero >> >> >> >> >> _______________________________________________ >> 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 17, 2010

[Pharo-project] FFI examples?

by Jake Bartlett

I'm trying to use SVMLight (http://svmlight.joachims.org/) from Pharo. SVMLight has some *.h files I need to load and some *.so libraries. I need to be able to call functions from them and manage the results. How do I create a FFI in Pharo? [jake]

May 17, 2010

Re: [Pharo-project] Managing Pharo external packages with Metacello, please read!

by Geert Claes

StÃ©phane Ducasse wrote: > > Because I want to have them close to the Pharo repositories :) > "Everything was carefully thought" (tm) > Fair enough ... how about PharoConfigurationRepository :) I have read all replies here and I am still a bit confused, so is it the idea to have a separate repository per release e.g. Pharo10Configurations, Pharo11Configurations etc? -- View this message in context: http://forum.world.st/Managing-Pharo-external-packages-with-Metacello-pleas… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 17, 2010

Re: [Pharo-project] [squeak-dev] Community Supported Packages

by Mariano Martinez Peck

On Mon, May 17, 2010 at 3:12 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Mariano Martinez Peck wrote on [1]: > >I don't agree here. You DON'T necessary need to have the packages inside > the > >image to have a UI. > > Please read what I wrote. I never, never, answer an email without reading. Ever. > I did not say that it is impossible > to build the UI when you have an external config - but "it would > be easy to build a UI" when it is already in the image. I'm sure > you will agree here. > Probably. But then you have to create a new tools with a UI, update (you will need to update the configurations, etc). > > However - even when SqueakMap is not well maintained - it's UI > was easy to use and was easy accessible and one could use it > with a few clicks. > Ok...but I still think there is not too much difference: In SM you have to: - first do always an update - browse categories, search the pacakge , select it, then select the version (hopefully you know which version works in THAT verion of squeak) Is this really too different to browse a repo with MonticelloBrowser and just load it ? The only thing we don't have is categories. > > Using Monticello tools, loading and evaluating by hand is > Not necessary. We can put a class side method initialize that does a self project version: 'theVersionThatWorksInPharo1.0' load and wala! not necessary even to create load method. No need to evaluate nothing by hand. Just browse, select a package, and click load button. And there, you are SURE you will load the version that works with that Pharo version. > currently possible - but this is a step backward in usability > compared to what Squeak has/had. But this is a convenience/tool > issue that has to be solved. > I even think that maybe managing projects "polymorphicly" with the same tool (Monticello Browser) is a nice idea. At least for a first step. If this infrastructure works well, there will be probably someone with time and willing to do a particular tool for what you want. Cheers Mariano > Bye > T. > > [1] > http://lists.gforge.inria.fr/pipermail/pharo-project/2010-May/026829.html > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > >

May 17, 2010

[Pharo-project] New inspector news :)

by StÃ©phane Ducasse

> It is fixed in the last version of NewInspector (on squeaksource). > > I removed from ProtoObject the calls to methods defined only in Object. I have to replace the calls by a default behavior: there is no way to inspect inst vars of a subclass of ProtoObject (and not Object). > > But NewInspector is designed to be extensible by anyone. For example, take a new class Proxy inheriting from ProtoObject with an instance variable named #object. You can firstly redefine the label redefining the method niLabel in the Proxy class (instance side): > > Proxy>>niLabel > ^ 'Proxy on: ' , object niLabel > > But you can also add a child for inspecting the inst var object with a label beginning by 'Object: ', redefining the method niConfiguration: > > Proxy>>niConfiguration > ^ super niConfiguration > addLast: [:obj | object asNINode label: 'Object: ' , object niLabel; yourself]; > yourself > > Note that the parameter obj of the block must be written but it is not really used. I must remove it in a next version of NewInspector. Write it and forget it :) > > The description (in the right pane) and the icon (between the triangle and the name of a node in the tree) can be also redefined. See the implementors of niLabel, niConfiguration, niDescription and niIcon for examples. > > FrÃ©d > > " > > Bien Ã toi, > > FrÃ©d > ---- > FrÃ©dÃ©ric Pluquet > UniversitÃ© Libre de Bruxelles (ULB) > Assistant > http://www.ulb.ac.be/di/fpluquet > > > 2010/5/13 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > http://code.google.com/p/pharo/issues/detail?id=1970 > > peut etre que si la superclass est pas Object > alors instVArNamed: doit etre evite je ne sais pas en fait. > > Stef >

May 17, 2010

Re: [Pharo-project] TextEditor and NewTextMorph merges and fixes

by StÃ©phane Ducasse

Tx!!!! Gaucho man On May 17, 2010, at 3:32 PM, Fernando olivero wrote: > Issue: 2375 > > Name: System-Text-FernandoOlivero.8 > Author: FernandoOlivero > Time: 17 May 2010, 3:22:14 pm > > > > ###################################### > Issue: -- > > Name: Morphic-FernandoOlivero.588 > Author: FernandoOlivero > Time: 17 May 2010, 1:42:04 pm > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 17, 2010

Re: [Pharo-project] Managing Pharo external packages with Metacello, please read!

by StÃ©phane Ducasse

Because I want to have them close to the Pharo repositories :) "Everything was carefully thought" (tm) :) On May 17, 2010, at 3:17 PM, Geert Claes wrote: > > > Mariano Martinez Peck wrote: >> >> 1) We create a squeaksource repository called Pharo10MetacelloRepository >> > > Just a wee idea here, since there are all these ConfigurationOfXXX packages, > why not have a MetacelloRepositoryForXXX (rather than > XXXMetacelloRepository). Maybe ConfigurationRepositoryForXXX is a better > name? > -- > View this message in context: http://forum.world.st/Managing-Pharo-external-packages-with-Metacello-pleas… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 17, 2010