December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 1633: Object allSubInstances appears to loop forever

by Stan Shepherd

StÃ©phane Ducasse wrote: > > thanks eliot > > this is strange I thought that we fixed that already .... I have to check. > > On Dec 18, 2009, at 6:28 PM, Eliot Miranda wrote: > >> with closures the block in allSubInstances will be a different object on >> each evaluation. Pre closures this would have been a single BlockContext >> used for each evaluation of the block (and hence non-reentrant). So you >> need to modify, e.g. by implementing allInstancesDo: in MethodContext >> class: >> >> 'From Croquet1.0beta of 11 April 2006 [latest update: #1] on 18 December >> 2009 at 9:26:47 am'! >> >> !MethodContext class methodsFor: 'hacks' stamp: 'ar 9/17/2008 16:24'! >> allInstancesDo: aBlock >> "Only count until thisContext" >> | inst next | >> inst := self someInstance. >> [inst == thisContext] whileFalse:[ >> next := inst nextInstance. >> aBlock value: inst. >> inst := next]! ! >> >> find it attached >> >> On Fri, Dec 18, 2009 at 7:47 AM, Stan Shepherd >> <stan.shepherd414(a)gmail.com> wrote: >> >> Pharo image: Pharo | Pharo-core >> PharoCore1.0rc1 Latest update: #10502 >> VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: >> #10074] >> >> Steps to reproduce: >> 1.Object allSubInstances >> >> It appears to be repeatedly adding its current context. >> >> ...Stan >> >> OrderedCollection>>addLast: >> Receiver: an OrderedCollection(an Object an Object an Object an >> Object an Object an Object an Object...etc... > > I think the fixed bug was the similar 'Issue 1044: MethodContext allInstances loops forever'. Not quite the same: 'From Pharo1.0beta of 16 May 2008 [Latest update: #10470] on 17 October 2009 at 4:49:35 pm'! !Behavior methodsFor: 'accessing instances and variables' stamp: 'MarcusDenker 10/17/2009 16:49'! allInstances "Answer a collection of all current instances of the receiver." | all inst next | all := OrderedCollection new. inst := self someInstance. [inst == nil] whileFalse: [ next := inst nextInstance. inst == all ifFalse: [all add: inst]. inst := next]. ^ all asArray! ! -- View this message in context: http://n2.nabble.com/Issue-1633-Object-allSubInstances-appears-to-loop-fore… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 18, 2009

Re: [Pharo-project] [update 1.1] #11108

by Nicolas Cellier

2009/12/18 Marcus Denker <marcus.denker(a)inria.fr>: > 11108 > ----- > > Issue 1610: Â Â (Float class >> #nan) = (Float class >> #nan) > Â Â Â Â Thanks, Niko Schwarz Here is how I would attack the new implementation : MyClass class>>nan ^NaN (Float class>> #nan) = (MyClass class >> #nan) -> MNU nil doesNotUnderstand: isNan MyClass>>a0 ^0.5 MyClass>>a1 ^0.5s1 MyClass>>a2 ^0.5s2 (MyClass>>#a1)=(MyClass>>#a2) (MyClass>>#a0)=(MyClass>>#a2) MyClass class>>componentMask ^ComponentMask ifNil: [ ComponentMask := 1023 ] MyClass class>>componentMax ^ComponentMax ifNil: [ ComponentMax := 1023.0 ]. (MyClass class>>#componentMax) = (MyClass class>>#componentMask). -> false MyClass componentMax; componentMask. (MyClass class>>#componentMax) = (MyClass class>>#componentMask). -> true (MyClass class>>#componentMask) = (MyClass class>>#componentMax). -> false Of course, these are unlikely, but... Nicolas (Float class nan) = (MyClass class nan) -> MNU nil doesNotUnderstand: isNan > Issue 1625: Â Â IdentityBag asSet does not answer an IdentitySet > Â Â Â Â Thanks, Nicolas! > Issue 1623: Â Â make DependentsArray more robust > Â Â Â Â Thanks, Nicolas! > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 18, 2009

Re: [Pharo-project] Rome port

by Tudor Girba

Yes, that works, but initially Michael only mentioned: Gofer new impara: 'RomePharo'; addPackage: 'Rome-BalloonCanvas'; addPackage: 'Rome-Base'; addPackage: 'Rome-PluginCanvas'; addPackage: 'Rome-Fonts'; addPackage: 'Rome-Demo'; load Rome-Reference was missing, hence, the error. Cheers, Doru On 18 Dec 2009, at 20:08, Alexandre Bergel wrote: > Gofer new > impara: 'RomePharo'; > addPackage: 'Rome-BalloonCanvas'; > addPackage: 'Rome-Base'; > addPackage: 'Rome-PluginCanvas'; > addPackage: 'Rome-Fonts'; > addPackage: 'Rome-Demo'; > addPackage: 'Rome-Reference'; > load > > loads fine in a 10500 for me. > > Alexandre > > > On 18 Dec 2009, at 16:57, Tudor Girba wrote: > >> Hi Alex, >> >> In what image are you loading it that it works? Only after adding >> Rome- >> Reference to what was said before was it Ok. >> >> Cheers, >> Doru >> >> >> On 18 Dec 2009, at 15:51, Alexandre Bergel wrote: >> >>> Hi Doru, >>> >>> As I said, just load what is suggested with Gofer. >>> >>> Alexandre >>> >>> >>> On 18 Dec 2009, at 13:30, Tudor Girba wrote: >>> >>>> Hi, >>>> >>>> Thanks, but the packages do not seem to load either: >>>> >>>> - in 10496dev I can load Graphics-MichaelRueger.168 and FreeType- >>>> MichaelRueger.498, but when I try to load Rome, I get >>>> "This package depends on the following classes: >>>> RomePath >>>> RomeReferenceCanvas ... " >>>> >>>> - in 10500dev the image crashes when I try to load Graphics- >>>> MichaelRueger.168 >>>> >>>> What am I doing wrong? >>>> >>>> Cheers, >>>> Doru >>>> >>>> On 18 Dec 2009, at 13:12, Simon Denier wrote: >>>> >>>>> >>>>> On 18 dÃ©c. 2009, at 13:03, Tudor Girba wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I am a bit confused :). This link seems to not work: >>>>>>>>>> https://gforge.inria.fr/frs/download.php/25047/ >>>>>>>>>> RomePlugin.bundle.zip >>>>>>>> >>>>>> >>>>>> What exactly should I do if I wanted to get Rome in 1.0 using a >>>>>> 4.2.2 >>>>>> VM? >>>>> >>>>> >>>>> You just need to install the packages indicated by Michael, the >>>>> plugin is already there. It works for me. >>>>> >>>>> >>>>>> >>>>>> Cheers, >>>>>> Doru >>>>>> >>>>>> >>>>>> >>>>>> On 17 Dec 2009, at 20:33, StÃ©phane Ducasse wrote: >>>>>> >>>>>>> Thanks john >>>>>>> >>>>>>> I deleted the plugging file. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> On Dec 17, 2009, at 6:46 PM, John M McIntosh wrote: >>>>>>> >>>>>>>> Ya, for years now I've shipped the latest Rome plugin, which >>>>>>>> BTW I >>>>>>>> did compile, >>>>>>>> within the Squeak macintosh carbon VM. >>>>>>>> >>>>>>>> It's version 1.2.1 >>>>>>>> >>>>>>>> Likely the one https://gforge.inria.fr/frs/download.php/25047/RomePlugin.bundle.zip >>>>>>>> should disappear to avoid confusion. Just use a 4.2.2 VM >>>>>>>> >>>>>>>> I'll add building a RomePlugin for Squeak V5.0 to my list of >>>>>>>> things to do for Christmas. >>>>>>>> >>>>>>>> On 2009-12-17, at 9:38 AM, Alexandre Bergel wrote: >>>>>>>> >>>>>>>>> Michael, this is an excellent start! >>>>>>>>> Thanks for this. This is important. >>>>>>>>> >>>>>>>>>> You will need the RomePlugin for your platform. >>>>>>>>>> https://gforge.inria.fr/frs/download.php/25047/ >>>>>>>>>> RomePlugin.bundle.zip >>>>>>>>>> https://gforge.inria.fr/frs/download.php/25046/rome.zip >>>>>>>>> >>>>>>>>> There is a plugin next to the MacOSX VM. I do not know whether >>>>>>>>> this is >>>>>>>>> the same version of the plugin >>>>>>>> >>>>>>>> -- >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> =============================================================== >>>>>>>> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: >>>>>>>> squeaker68882 >>>>>>>> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> = >>>>>>>> =============================================================== >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>> >>>>>> -- >>>>>> www.tudorgirba.com >>>>>> >>>>>> "Don't give to get. Just give." >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>>> project >>>>> >>>>> -- >>>>> Simon >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "One cannot do more than one can do." >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow." >> >> >> >> >> _______________________________________________ >> 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 -- www.tudorgirba.com "Problem solving should be concentrated on describing the problem in a way that is relevant for the solution."

Dec. 18, 2009

Re: [Pharo-project] Rome port

by Alexandre Bergel

Gofer new impara: 'RomePharo'; addPackage: 'Rome-BalloonCanvas'; addPackage: 'Rome-Base'; addPackage: 'Rome-PluginCanvas'; addPackage: 'Rome-Fonts'; addPackage: 'Rome-Demo'; addPackage: 'Rome-Reference'; load loads fine in a 10500 for me. Alexandre On 18 Dec 2009, at 16:57, Tudor Girba wrote: > Hi Alex, > > In what image are you loading it that it works? Only after adding > Rome- > Reference to what was said before was it Ok. > > Cheers, > Doru > > > On 18 Dec 2009, at 15:51, Alexandre Bergel wrote: > >> Hi Doru, >> >> As I said, just load what is suggested with Gofer. >> >> Alexandre >> >> >> On 18 Dec 2009, at 13:30, Tudor Girba wrote: >> >>> Hi, >>> >>> Thanks, but the packages do not seem to load either: >>> >>> - in 10496dev I can load Graphics-MichaelRueger.168 and FreeType- >>> MichaelRueger.498, but when I try to load Rome, I get >>> "This package depends on the following classes: >>> RomePath >>> RomeReferenceCanvas ... " >>> >>> - in 10500dev the image crashes when I try to load Graphics- >>> MichaelRueger.168 >>> >>> What am I doing wrong? >>> >>> Cheers, >>> Doru >>> >>> On 18 Dec 2009, at 13:12, Simon Denier wrote: >>> >>>> >>>> On 18 dÃ©c. 2009, at 13:03, Tudor Girba wrote: >>>> >>>>> Hi, >>>>> >>>>> I am a bit confused :). This link seems to not work: >>>>>>>>> https://gforge.inria.fr/frs/download.php/25047/ >>>>>>>>> RomePlugin.bundle.zip >>>>>>> >>>>> >>>>> What exactly should I do if I wanted to get Rome in 1.0 using a >>>>> 4.2.2 >>>>> VM? >>>> >>>> >>>> You just need to install the packages indicated by Michael, the >>>> plugin is already there. It works for me. >>>> >>>> >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> >>>>> On 17 Dec 2009, at 20:33, StÃ©phane Ducasse wrote: >>>>> >>>>>> Thanks john >>>>>> >>>>>> I deleted the plugging file. >>>>>> >>>>>> Stef >>>>>> >>>>>> On Dec 17, 2009, at 6:46 PM, John M McIntosh wrote: >>>>>> >>>>>>> Ya, for years now I've shipped the latest Rome plugin, which >>>>>>> BTW I >>>>>>> did compile, >>>>>>> within the Squeak macintosh carbon VM. >>>>>>> >>>>>>> It's version 1.2.1 >>>>>>> >>>>>>> Likely the one https://gforge.inria.fr/frs/download.php/25047/RomePlugin.bundle.zip >>>>>>> should disappear to avoid confusion. Just use a 4.2.2 VM >>>>>>> >>>>>>> I'll add building a RomePlugin for Squeak V5.0 to my list of >>>>>>> things to do for Christmas. >>>>>>> >>>>>>> On 2009-12-17, at 9:38 AM, Alexandre Bergel wrote: >>>>>>> >>>>>>>> Michael, this is an excellent start! >>>>>>>> Thanks for this. This is important. >>>>>>>> >>>>>>>>> You will need the RomePlugin for your platform. >>>>>>>>> https://gforge.inria.fr/frs/download.php/25047/ >>>>>>>>> RomePlugin.bundle.zip >>>>>>>>> https://gforge.inria.fr/frs/download.php/25046/rome.zip >>>>>>>> >>>>>>>> There is a plugin next to the MacOSX VM. I do not know whether >>>>>>>> this is >>>>>>>> the same version of the plugin >>>>>>> >>>>>>> -- >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> ================================================================ >>>>>>> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: >>>>>>> squeaker68882 >>>>>>> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> = >>>>>>> ================================================================ >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Don't give to get. Just give." >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>> >>>> -- >>>> Simon >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> www.tudorgirba.com >>> >>> "One cannot do more than one can do." >>> >>> >>> >>> >>> _______________________________________________ >>> 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 > > -- > www.tudorgirba.com > > "Every thing has its own flow." > > > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 18, 2009

Re: [Pharo-project] Default code browser

by Schwab,Wilhelm K

When I said the package browser+MC was not deterministic, I meant it. My experience was that _sometimes_ packages would be created from categories, and sometimes not. Things get more clear if you fire up the MC GUI and explicitly create a package. Then it suffices (with the other browsers at least) to put a class in the corresponding category, and to categorize methods with *packageName (yuk!!!!, but it works). There are MC tutorials, and you should read one if you have not already done so. My biggest gripe is that I find myself being forced (AFAIK) to type category names far more often than should be the case. There is what appears to be "recent categories" list but it is both hard to read and (I suspect[*]) not predictable. May the overseers be with you if you ever type something with a bad mix of capitalization - deleting the offending package never seems to rid the image of it. As Murphey would have it, type something wrong and the tools never forget; type something correct and you will end up typing it again, at least until you no longer need it :( That is based on fixing a many badly-formatted category names created by SIF. FWIW, I have learned how to use the regex package to make changes to a .sif file before loading it into Pharo, which is a nice way to go. For now, I get along fairly well and am looking forward to a new package system. What I find beyond comprehension is that the rough spots have not been fixed. In my relatively short time making real use of Pharo, I have found it essential to "clone" tools that I use in Dolphin to manage packages. The core of it is no longer an absolute must in Dolphin, mostly because its package system has improved over the years. However, I have something that attempts to identify "your" work that is not assigned to one of a collection of packages identified to it, provides one-shot saving of those packages, and can "easily" be loaded into a new image and load the packages into it. It is rough around the edges, but I plan to make it available to anyone who wants it after it settled down a little more. One thing I would like to be able to do is to create separate .mcz files for Migrate-core and Mirgrate-uf, with assurance that **nothing** from Migrate-uf will end up in Migrate-core.mcz. So far, that is not happening, perhaps my fault. Since I have been spouting complaints all day, I should mention that I have noted that a Pharo image has been serving a Seaside app off of a vmware based win2k3 machine, and has done so with higher reliability than vmware itself, or so it seems. I have frequent problems with network routing, but it appears to happen only when pings fail to the offending host, and magically gets fixed when the pings begin to succeed again. Any dÃ©jÃ vu?? I'd like to hear about how you fixed it. Reports on the net suggest that it could be a known and long-standing defect. I have also had DNS related hassles, but is really no surprise. Years ago, I learned the hard way to disable XP's DNS cache service; it is said to be essential to win2k3, and I hesitate to learn the hard way on a vm. In short, Pharo sucks a LOT less than Windows :) Bill [*] Not meaning to spread FUD, just being honest about my observations. -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of GeertClaes Sent: Friday, December 18, 2009 12:31 PM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Default code browser Schwab,Wilhelm K wrote: > > You didn't ask, but here's how I see it on pakages :) PackageInfo > **ABUSES** method categories to associate methods with packages. > Methods should be able to belong to multiple categories (you won't > miss it until you can do it), and to one package. Dolphin also has a > class category option, but I am not aware that anyone ever found it > useful - packages are enough to categorize classes. > I think I am with you that class categories are probably a bit overkill here since these class types are already grouped in separate (monticello) packages . Schwab,Wilhelm K wrote: > > I don't know a nice way to say it: if you are confused about packages, > ditch the package browser for a while. I have not used it for a few > versions, but I was shocked at how slow it could be, and began to > suspect that its behavior was (queue throat-clearing.wav) not deterministic. > Another possibility (if this level of re-entrancy is possible??) is > that it is SO slow that one fails to appreciate that it is still > crunching on the organization?? > It's not just that I am a bit confused or think the package browser is too slow, from a usability point of view it just does not make sense to me that it seems so complicated to load/share packages from other projects and/or components. Maybe this discussion belongs more in the 'Pharo IDE usability (was Re: Pharo for Professional Development) ' thread now? -- View this message in context: http://n2.nabble.com/Default-code-browser-tp4183317p4187788.html 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

Dec. 18, 2009

Re: [Pharo-project] [Moose-dev] MorphTreeMorph>>mouseEnter: broken in Moose

by Tudor Girba

Hi Oscar, Thanks for reporting. It looks like MorphTreeMorph moved to support Pharo 1.1 and in the meantime it brakes in 1.0. Loading Morphic-MorphTreeWidget-AlainPlantec.39 solves the problem. I updated ConfigurationOfGlamour to hardcode the version for the moment when loading the default configuration. I also released: - Glamour version: 2.0-beta.2 - Moose version: 4.0-beta.3 Cheers, Doru On 18 Dec 2009, at 18:49, Oscar Nierstrasz wrote: > > I get an infinite loop of exceptions in the Moose Finder when I load > Moose into the latest Pharo. > > LazyMorphTreeMorph does not understand keyboardFocusOnMouseDown ... > > Sleuthing shows: > > MorphTreeMorph>>mouseEnter: event > "Changed to take keyboardFocusOnMouseDown preference into account." > > super mouseEnter: event. > self wantsKeyboardFocus ifFalse: [^self]. > self keyboardFocusOnMouseDown > ifFalse: [self takeKeyboardFocus] > > But keyboardFocusOnMouseDown is not implemented anywhere in the > system. > > What gives? > > Alain, it seems this method comes from you. What gives? I am > unsure what to do ... > > - on > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

Dec. 18, 2009

Re: [Pharo-project] Issue 1633: Object allSubInstances appears to loop forever

by StÃ©phane Ducasse

thanks eliot this is strange I thought that we fixed that already .... I have to check. On Dec 18, 2009, at 6:28 PM, Eliot Miranda wrote: > with closures the block in allSubInstances will be a different object on each evaluation. Pre closures this would have been a single BlockContext used for each evaluation of the block (and hence non-reentrant). So you need to modify, e.g. by implementing allInstancesDo: in MethodContext class: > > 'From Croquet1.0beta of 11 April 2006 [latest update: #1] on 18 December 2009 at 9:26:47 am'! > > !MethodContext class methodsFor: 'hacks' stamp: 'ar 9/17/2008 16:24'! > allInstancesDo: aBlock > "Only count until thisContext" > | inst next | > inst := self someInstance. > [inst == thisContext] whileFalse:[ > next := inst nextInstance. > aBlock value: inst. > inst := next]! ! > > find it attached > > On Fri, Dec 18, 2009 at 7:47 AM, Stan Shepherd <stan.shepherd414(a)gmail.com> wrote: > > Pharo image: Pharo | Pharo-core > PharoCore1.0rc1 Latest update: #10502 > VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: > #10074] > > Steps to reproduce: > 1.Object allSubInstances > > It appears to be repeatedly adding its current context. > > ...Stan > > OrderedCollection>>addLast: > Receiver: an OrderedCollection(an Object an Object an Object an > Object an Object an Object an Object...etc... > Arguments and temporary variables: > newObject: [] in Object > class(Behavior)>>allSubInstances > Receiver's instance variables: > array: an Array(an Object an Object an Object an Object an > Object an Object an ...etc... > firstIndex: 1 > lastIndex: 1173805 > > OrderedCollection>>add: > Receiver: an OrderedCollection(an Object an Object an Object an > Object an Object an Object an Object...etc... > Arguments and temporary variables: > newObject: [] in Object > class(Behavior)>>allSubInstances > Receiver's instance variables: > array: an Array(an Object an Object an Object an Object an > Object an Object an ...etc... > firstIndex: 1 > lastIndex: 1173805 > > [] in Object class(Behavior)>>allSubInstances > Receiver: Object > Arguments and temporary variables: > aCollection: [] in Object > class(Behavior)>>allSubInstances > x: an OrderedCollection(an Object an Object an Object > an Object an Object an Ob...etc... > Receiver's instance variables: > superclass: ProtoObject > methodDict: a MethodDictionary(size 408) > format: 2 > instanceVariables: nil > organization: ('*DynamicBindings' binding binding: > hasBinding removeBinding) > ('...etc... > subclasses: {BalloonState. StandardFileMenuResult. > UndefinedObject. Boolean. Fi...etc... > name: #Object > classPool: a Dictionary(#DependentsFields->a > WeakIdentityKeyDictionary(MCWorkin...etc... > sharedPools: nil > environment: Smalltalk > category: #'Kernel-Objects' > traitComposition: {} > localSelectors: nil > ... > -- > View this message in context: http://n2.nabble.com/Issue-1633-Object-allSubInstances-appears-to-loop-fore… > 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 > > <MethodContext class-allInstancesDo.st>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 18, 2009

Re: [Pharo-project] MetacelloRepository is online

by StÃ©phane Ducasse

cool! On Dec 18, 2009, at 6:23 PM, Romain Robbes wrote: > I added the ConfigurationOfOCompletion: > > Gofer new > > squeaksource: 'MetacelloRepository'; > > > addPackage: 'ConfigurationOfOCompletion'; > > > load. > > > (Smalltalk at: #ConfigurationOfOCompletion) perform: #loadDefault > > > Romain > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 18, 2009

Re: [Pharo-project] Pharo for Professional Development

by Schwab,Wilhelm K

You guys didn't ask what I think about this either :) Native windows are not the panacea that many believe them to be. My most intense GUI in Dolphin uses a fair amount of emulation to obtain adequate performance. However, the problem (AFAIK) arises only when creating large numbers of widgets, e.g. the cells of a spreadsheet. I think our goal should be to offer a good emulated widget framework AND to use native windows for the various tool shells. A useful transition would be to use native shells with the current Polymorph widgets inside of each shell. The concept of "the" desktop (world menu) will disappear, and the current approach to startup/shutdown will be revealed to be as broken as it is. Toolshells will need menus and/or toolbars (hopefully with tasteful and compact, fixed-size buttons). Once those things are sorted, we could begin to convert the various tools to native widgets, if we even care to do so. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Levente Uzonyi Sent: Friday, December 18, 2009 7:52 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Pharo for Professional Development On Fri, 18 Dec 2009, George Herolyants wrote: > 2009/12/18 Michael Rueger <m.rueger(a)acm.org>: >> Henrik Johansen wrote: >> >> Interestingly enough a lot of the (complex) multiple native window >> applications have (gone back to) all in one window UIs (Eclipse, all >> of the Adobe products, ...). > > Yeah! That's true. And their look&feel may differ from the underlying > os. And everyone uses them without complaining. So what's wrong with > pharo? Maybe one of the weak points is that it simulates windowing > system inside another one, when other applications (Eclipse, > Netbeans...) have strongly defined layout (though customizable)? I > think it's a real issue. Pharo Development Environment is *Integrated* > but the UI still lacks this integration in some places, IMHO. > > But I think multiple windows in the meaning of what for example > firefox has will be helpful as well. I mean two or more usual pharo > windows "connected" to the same image. Is that possible? > HostWindowPlugin is available: http://wiki.squeak.org/squeak/3862 > And native basic dialogs may be helpful too, to not reinvent the wheel > (aka FileBrowser :). At first sight this idea seems to be cool, but it's not. FileBrowser is not a "reinvented wheel", it's really useful in a closed environments like smalltalk. FileBrowser has the same features on all platforms while native dialogs don't. Some platforms don't even have a graphical UI, would you open a terminal in the image on those? Levente > > I vote for the WhiskerBrowser with all the cool OB stuff integrated! > ;) > > Cheers, > George > > _______________________________________________ > 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

Dec. 18, 2009

[Pharo-project] MorphTreeMorph>>mouseEnter: broken in Moose

by Oscar Nierstrasz

I get an infinite loop of exceptions in the Moose Finder when I load Moose into the latest Pharo. LazyMorphTreeMorph does not understand keyboardFocusOnMouseDown ... Sleuthing shows: MorphTreeMorph>>mouseEnter: event "Changed to take keyboardFocusOnMouseDown preference into account." super mouseEnter: event. self wantsKeyboardFocus ifFalse: [^self]. self keyboardFocusOnMouseDown ifFalse: [self takeKeyboardFocus] But keyboardFocusOnMouseDown is not implemented anywhere in the system. What gives? Alain, it seems this method comes from you. What gives? I am unsure what to do ... - on

Dec. 18, 2009