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

Re: [Pharo-project] Thanks Danny :)

by StÃ©phane Ducasse

I just did a 2400 dpi scan and I can use it as desktop => 29 Mb image but this cool on my 30 inches screen. I will put this file on the inria web site for other lighhouse stamp lovers. Stef

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) 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 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

Jan. 4, 2010

Re: [Pharo-project] about DependencyBrowser

by Mariano Martinez Peck

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. 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 ? Cheers Mariano

Jan. 4, 2010

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

by Laval Jannik

Thank you Dave, Jannik On Jan 4, 2010, at 21:16 , 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

Jan. 4, 2010

Re: [Pharo-project] Thanks Danny :)

by StÃ©phane Ducasse

> Which reminds me, I almost thought you'd made a sponsorship deal with > the airport in Brest when I left ESUG, there was a shop there with > lighthouses on _everything_! Apparently there are some lighthouses around brest. Did you ever see the movie on the tempest sent by samuel > Though the Confit de Canard-boxes were tempting, I ended up just buying > a deck of cards :) I would have taken the other with caramel au beurre sale. :) this brings me to the next point we could have a pharo goodies shop (like the one I did for Squeak and the squeakfoundation). With mugs and others. Does anybody interested in managing one at cafepress or better? Stef

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 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

Jan. 4, 2010

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

by StÃ©phane Ducasse

As a solution I was planning to redefine Behavior>>addTraitSelector, TraitBehavior>>addTraitSelector and then redefine it TPureBehavior then remove Behavior>>addTraitSelector, TraitBehavior>>addTraitSelector I imagine that it can work now I will try to see Stef On Jan 4, 2010, at 8:54 PM, StÃ©phane Ducasse wrote: > 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? > > 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

Jan. 4, 2010

Re: [Pharo-project] Thanks Danny :)

by Henrik Sperre Johansen

Which reminds me, I almost thought you'd made a sponsorship deal with the airport in Brest when I left ESUG, there was a shop there with lighthouses on _everything_! Though the Confit de Canard-boxes were tempting, I ended up just buying a deck of cards :) Cheers, Henry On 04.01.2010 20:51, Danny Chan wrote: > Am Montag, 4. Januar 2010 20:24:34 schrieb StÃ©phane Ducasse: > >> Hi guys >> >> I can tell you that seeing this letter in my mailbox was ***really*** cool. >> Thanks danny this is a great license agreement. >> >> Stef >> >> > Glad that you liked it, it is my favourite stamp, too. > > Danny > > _______________________________________________ > 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] What about killing PharoWeb images?

by StÃ©phane Ducasse

good! We need a good collection of good packages :) > > Being able to easily load AidaWeb into GemStone was one of the other motivations for Metacello:) > > My todo list for Pharo, includes building a configuration for AidaWeb that will load AidaWeb into GLASS or Pharo (with feedback from Janko). > > I also plan incorporate Julian's work on Pier2 for Seaside3.0 into the Pier configuration (the current Pier configuration in MetacelloRepository is for Seaside2.8 only) > > Dale > > _______________________________________________ > 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] Building Pharo and Plugins for Mac OS X and Linux

by StÃ©phane Ducasse

David check the squeak documentation on how to invoke external library with FFI. In pharo you have also alien (not tested on non intel - works on mac). You do not have to recompile the vm to invoke external library. You define methods with specific pragmas annotations and the plugin code can be invoked. One if these days we should write a better doc http://wiki.squeak.org/squeak/2426 http://www.is.titech.ac.jp/~ohshima/squeak/DShowVideo/index.html http://www.visoracle.com/squeak/faq/ffi-windows.html http://wiki.squeak.org/squeak/356 VMMaker is published on SqueakSource. May be people with more experience will comment. Stef On Jan 4, 2010, at 7:19 PM, David Li wrote: > Hi, > > I am new to Pharo and wonder if there is a step by step instruction on building Pharo for Mac OS X and Linux. I am working on a project that requires extension either through itself or via plugins. I have been seeing the mention of VMaker but can't find a good document about it. > > Thanks a lot for the help. > > David Li > > > _______________________________________________ > 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