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

Re: [Pharo-project] about DependencyBrowser

by HernÃ¡n Morales Durand

Hi again Mariano, 2010/1/4 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Mon, Jan 4, 2010 at 8:34 PM, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: >> >> Hi Mariano, >> Â Thank you for the feedback, I've updated the dependency browser >> package in SqueakSource, have a look for the latest package releases >> or evaluate the installation script again found in >> http://swikicaicyt.homeip.net/WebOpus/65 > > > Cool, thank you very much for your work. >> >> > Hey! I have more questions :) >> > >> > 3) Please, take a Pharo dev image and you will see that the package >> > OCForOB >> > for example, only depends on OmniBrowser and OB-Standard (using >> > dependency >> > browser). However, that package also depends on OCompletion I think. >> > Look >> > for example the method >> > >> > OBTextPanel >> createCompletionControllerÂ (category ocforob) >> > >> > and you will see that it uses the class OControllerÂ which is from the >> > package OCompletion....So, shouldn't be OCompletion a dependency ? >> > >> >> True, it is fixed now in the latest release. >> > > > Yes, cool. At this in this case It is fixed :) > > >> >> > 4) There are certain packages that are not listed in the dependency >> > browser. >> > Examples OB-Standard, OB-Morphic, O2-Standard , etc...most of them >> > (maybe >> > all) seem to have the pattern XXX-YYY. Do you know what can be the >> > problem >> > here? Maybe something related to what you told me about normalized and >> > un-normalized?Â I would really like to see these packages also. >> >> No, this was a missing line in the package listing. Fixed too. >> > > This is not working very well. When you select OB , Refectoring or any other > which is "not normalized" and it brings the popup, even selecting something > the popup brings again and again and again....and I THINK the amount of > times the pop up raises is the amount of packages you have as dependencies > (the size of the collection of the right ;) > Maybe this can help you to detect the problem. Yes, I was aware of the problem, but I don't know if I want to fix it :) Seriously, the problem is a package name is not an object (well, it's a String...) so people can name packages as they want. (e.g. things like : MyPackage-MySubcategory1-MySubcategory2-MySubcategory3-... ) Besides that, or because of that, there are PackageInfo's for packages with names including arbitrary number of separators...please evaluate: ( PackageOrganizer default packages collect: [: pkg | pkg packageName ] ) asSortedCollection and scroll through Collections. There is a 'Collection' package and 11 more 'Collection-XXXX' packages. This kind of textual division of categories with separators is complicating things. My question is: Is the 'Collection' package one and there are 11 dirty package info's which should not be there, or there are 12 Collection packages and the one without subcategory name which is not shown in the Browser? > > Another problem I have right now is this example: NewInspector. It extends > the class ProtoObject with this method: > > ProtoObject>> > niChildrenBlockForFixedFields (an extension for NewInspector). > In that method, it uses the class TypeCollector which is form RoelTyper. > However, RoelTyper is not shon as a dependency. > > Do you know what can be the problem ? I have no idea but I will check it out, thanks for reporting. Cheers, HernÃ¡n

Jan. 4, 2010

[Pharo-project] [update 1.1] #11136

by StÃ©phane Ducasse

> 11136 > ----- > > - Issue 1738: CompiledMethodTrailer post action > > So now this should be fixed. > I should remove createHeader: > I will do that during the next batches tomorrow evening. > > Stef > > >

Jan. 4, 2010

Re: [Pharo-project] Notifications of windows opening/closing/focus

by StÃ©phane Ducasse

Yes it would be good to see if this is ok to get it into the system. Stef On Jan 4, 2010, at 5:39 PM, Alexandre Bergel wrote: > Gary, > > In this email I attached a .st file. Just load it, and it will install the change set to get notifications. > A number of people already expressed their need for such an extension. > > Cheers, > Alexandre > > <MOMorphicExtensionInstaller.st> > On 4 Jan 2010, at 17:20, Gary Chambers wrote: > >> Nothing like that currently or previously AFAIK. >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "Simon Denier" <Simon.Denier(a)inria.fr> >> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> >> Sent: Monday, January 04, 2010 4:00 PM >> Subject: [Pharo-project] Notifications of windows opening/closing/focus >> >> >>> Hi >>> >>> How do you get notified of windows opening, closing, or getting focus in >>> Pharo? Is there some announcements or some older events? >>> >>> >>> -- >>> Simon >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 4, 2010

Re: [Pharo-project] [squeak-dev] Re: 64 bit images (was Re: The Trunk: Collections-dtl.268.mcz)

by David T. Lewis

On Mon, Jan 04, 2010 at 09:30:45PM +0100, St?phane Ducasse wrote: > david > > I would really like to continue the cleaning of SystemDictionary > because I do not like the current state of affair. > > Now we can either have a namespace class (with only namespace behavior) > and a imageManagement class > > Now we could have one variable Smalltalk to point to either of it. > but we will need another name. > Now the point behind the current (which I do not like but live with it is that) > it would be cool to be able to do from my image some query into your image). > This was about thinking about that that SmalltalkImage current got birth. > > Now I would love to get some discussions about a way to > - have a class management class = SystemDictionary but with clean contents and cool name => namespace? > (which often people confused with having namespace at the language level and it not part of the proposal > don't open the box please) > - have a cool abstraction over image housekeeping > - a cool abstraction about vm information > > so if you have ideas please let me know. Stef, I think it would be good to step away from the details and just think about the high level objects - what do they represent and what are they responsible for (http://www.wirfs-brock.com/Design.html)? Maybe there would be two or three classes involved, as few as possible. Then write the class comments for the empty classes. Think about it for a few weeks, and if it still makes sense then start the refactoring. But I would not touch a single line of code until the class comments are clearly written and understood. $0.02, Dave

Jan. 4, 2010

[Pharo-project] [update 1.1] #11135

by StÃ©phane Ducasse

11135 ----- fixing trailer: #(0 0 0 0) by adding first createMethod: numberOfBytesForAllButTrailer header: headerWord

Jan. 4, 2010

Re: [Pharo-project] Thanks Danny :)

by StÃ©phane Ducasse

I put the stamp into https://gforge.inria.fr/frs/?group_id=1299 I will add the mp4 (apparently it did not make it). Stef

Jan. 4, 2010

Re: [Pharo-project] Issues in 1.1 (was: Re: [update 1.1] #11126 - 27 (final ...))

by StÃ©phane Ducasse

yes this is probably easier. Glad I was looking for lenses :) I will do it now. Stef On Jan 4, 2010, at 9:57 PM, Igor Stasenko wrote: > 2010/1/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Igor when I try to recompile TPureBehavior>>addTraitSelector: >> >> I get a DNU >> Array>>createMethod:header: >> because the system uses itself when I add a method to a trait. >> >> This morning I did something and it worked but now I do not remember and I'm thinking how to turn around the >> problem. >> Do you have an idea? >> > you can restore the ArrayedCollection>>createMethod:header: > method, just temporary. So you will be able to produce methods using > array of bytes as trailer. > > But it is strange.. i remember i fixed that method (addTraitSelector:) > in pharo changesets. Or maybe it was something else. > >> Stef >> >> >>> >>>> >>>>> methodAndNode := self >>>>> compile: source >>>>> classified: nil >>>>> notifying: nil >>>>> trailer: self defaultMethodTrailer >>>>> ifFail: [^nil]. >>>> >>>> ?? >>>> >>> >>> yup. >>> >>> -- >>> 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

Jan. 4, 2010

Re: [Pharo-project] Issues in 1.1 (was: Re: [update 1.1] #11126 - 27 (final ...))

by Igor Stasenko

2010/1/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Igor when I try to recompile TPureBehavior>>addTraitSelector: > > I get a DNU > Array>>createMethod:header: > because the system uses itself when I add a method to a trait. > > This morning I did something and it worked but now I do not remember and I'm thinking how to turn around the > problem. > Do you have an idea? > you can restore the ArrayedCollection>>createMethod:header: method, just temporary. So you will be able to produce methods using array of bytes as trailer. But it is strange.. i remember i fixed that method (addTraitSelector:) in pharo changesets. Or maybe it was something else. > Stef > > >> >>> >>>> methodAndNode Â := self >>>> Â Â Â Â Â Â Â compile: source >>>> Â Â Â Â Â Â Â classified: nil >>>> Â Â Â Â Â Â Â notifying: nil >>>> Â Â Â Â Â Â Â trailer: self defaultMethodTrailer >>>> Â Â Â Â Â Â Â ifFail: [^nil]. >>> >>> ?? >>> >> >> yup. >> >> -- >> 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.

Jan. 4, 2010

Re: [Pharo-project] Building Pharo and Plugins for Mac OS X and Linux

by HernÃ¡n Morales Durand

2010/1/4 David Li <taweili(a)yahoo.com>: > > On Jan 5, 2010, at 3:24 AM, pharo-project-request(a)lists.gforge.inria.fr wrote: > >> On Mon, Jan 4, 2010 at 7:19 PM, David Li <taweili(a)yahoo.com> wrote: >> Hi, >> >> Â I am new to Pharo >> >> Hi and welcome! >> >> and wonder if there is a step by step instruction on building Pharo for Mac OS X and Linux. >> >> The only thing I am aware of is http://code.google.com/p/pharo/wiki/BuildingAVMOnPharo > > Thanks. I have come across that document as well. I kind of got stuck on figuring how how I can install VMMaker. > Try (and proceed with the Warning) Gofer new squeaksource:'JBARepo'; package:'FFI-Kernel'; load. (Smalltalk at: #ExternalType) initialize. (Smalltalk at: #ExternalStructure) compileAllFields. Smalltalk recreateSpecialObjectsArray. Gofer new squeaksource:'VMMaker'; package:'VMMaker'; load. HernÃ¡n

Jan. 4, 2010

Re: [Pharo-project] [squeak-dev] Re: 64 bit images (was Re: The Trunk: Collections-dtl.268.mcz)

by StÃ©phane Ducasse

> david > > I would really like to continue the cleaning of SystemDictionary > because I do not like the current state of affair. > > Now we can either have a namespace class (with only namespace behavior) both > and a imageManagement class > > Now we could have one variable Smalltalk to point to either of it. them :) > but we will need another name. > Now the point behind the current (which I do not like but live with it is that) > it would be cool to be able to do from my image some query into your image). > This was about thinking about that that SmalltalkImage current got birth. > > Now I would love to get some discussions about a way to > - have a class management class = SystemDictionary but with clean contents and cool name => namespace? > (which often people confused with having namespace at the language level and it not part of the proposal > don't open the box please) > - have a cool abstraction over image housekeeping > - a cool abstraction about vm information > > so if you have ideas please let me know. > > Stef > > > On Jan 4, 2010, at 9:16 PM, David T. Lewis wrote: > >> On Mon, Jan 04, 2010 at 07:09:01PM +0100, Laval Jannik wrote: >>> Hi, >>> >>> I understand your comments, >>> So: >>> - i will put word size a class var, >>> - this class var will be modify only by systemTracer >>> >>> Now I have a question: >>> Why using Smalltalk wordSize whereas the vm parameter is getting by SmalltalkImage current ? >> >> Hi Jannik, >> >> Different people may answer this question in different ways, because it >> is a matter of style and personal opinion. But it may help to know that >> earlier versions of Squeak had the vm parameter query in SystemDictionary >> ("Smalltalk") rather than in SmalltalkImage. This was moved as part of >> a larger effort to reorganize SystemDictionary, which is a rather large >> class that has accumulated many functions over the years. >> >> As matter of function, it makes no difference either way. The part that >> is subject to opinion is whether it makes more sense for a person to >> say "Smalltalk wordSize" to refer to the size of a word in the object >> memory, or whether "SmalltalkImage current wordSize" is more meaningful. >> >> FWIW, my own opinion is that neither one is right, but "Smalltalk wordSize" >> is easier to remember. But no matter what approach is taken, you will be able >> to find someone who does not agree, so you should form your own opinion ;-) >> >> HTH, >> >> Dave >> >> >> _______________________________________________ >> 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

Jan. 4, 2010