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

Re: [Pharo-project] Problem with senders?

by Adrian Lienhard

Hi Mariano, It seems this is a bug in the OB tools. It works in Pharo-core. Please create an issue in the tracker. Cheers, Adrian On Mar 20, 2009, at 05:16 , Mariano Martinez Peck wrote: > I am trying to see the senders of a message. I select "startsWith:" > in a > workspace -> right button -> extended search -> senders of it and I > get a > wallback. > > If you think this is a bug, let me know and I add it to the issue > tracker. > > Thanks, > > Mariano > > > > MessageNotUnderstood: OBShowSenders class>>of:label: > 20 March 2009 1:11:08 am > > VM: unix - a SmalltalkImage > Image: Pharo0.1 [Latest update: #10256] > > SecurityManager state: > Restricted: false > FileAccess: true > SocketAccess: true > Working Dir /home/mariano/squeak/imagenes > Trusted Dir /home/mariano/squeak/imagenes/secure > Untrusted Dir /home/mariano/squeak/imagenes/My Squeak > > OBShowSenders class(Object)>>doesNotUnderstand: #of:label: > Receiver: OBShowSenders > Arguments and temporary variables: > aMessage: of: an OBSelectorNode label: 'Senders of > startsWith: > [4]' > exception: MessageNotUnderstood: OBShowSenders > class>>of:label: > resumeValue: nil > Receiver's instance variables: > superclass: OBNavigate > methodDict: a MethodDictionary(#browserClass->a > CompiledMethod > (3617) #noChildr...etc... > format: 136 > instanceVariables: nil > organization: ('as yet unclassified' browserClass > noChildrenMessage) > > subclasses: nil > name: #OBShowSenders > classPool: nil > sharedPools: nil > environment: Smalltalk > category: #'OB-Standard-Announcements' > traitComposition: nil > localSelectors: nil > > DEVToolSet class>>browseSendersOf:name:autoSelect: > Receiver: DEVToolSet > Arguments and temporary variables: > aSymbol: #startsWith: > labelString: 'Senders of startsWith: [4]' > autoSelectString: 'startsWith:' > Receiver's instance variables: > superclass: StandardToolSet > methodDict: a MethodDictionary() > format: 2 > instanceVariables: nil > organization: ('as yet unclassified') > > subclasses: nil > name: #DEVToolSet > classPool: nil > sharedPools: nil > environment: Smalltalk > category: #ImageForDevelopers > traitComposition: nil > localSelectors: nil > > ToolSet class>>browseSendersOf:name:autoSelect: > Receiver: ToolSet > Arguments and temporary variables: > aSymbol: #startsWith: > titleString: 'Senders of startsWith: [4]' > autoSelectString: 'startsWith:' > Receiver's instance variables: > superclass: AppRegistry > methodDict: a MethodDictionary() > format: 2 > instanceVariables: nil > organization: ('as yet unclassified') > > subclasses: nil > name: #ToolSet > classPool: nil > sharedPools: nil > environment: Smalltalk > category: #'System-Applications' > traitComposition: nil > localSelectors: nil > registeredClasses: an OrderedCollection(StandardToolSet > OTToolset DEVToolSet) > default: DEVToolSet > > SystemNavigation>>browseSendersOf:name:autoSelect: > Receiver: a SystemNavigation > Arguments and temporary variables: > aSelector: #startsWith: > labelString: 'Senders of startsWith:' > autoSelectString: 'startsWith:' > title: 'Senders of startsWith: [4]' > size: 4 > senders: an OrderedCollection(a MethodReference Algernon >> > #isMatchingClass:gi...etc... > Receiver's instance variables: > browserClass: nil > hierarchyBrowserClass: nil > > > --- The full stack --- > OBShowSenders class(Object)>>doesNotUnderstand: #of:label: > DEVToolSet class>>browseSendersOf:name:autoSelect: > ToolSet class>>browseSendersOf:name:autoSelect: > SystemNavigation>>browseSendersOf:name:autoSelect: > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > SystemNavigation>>browseAllCallsOn: > [] in TextMorphForShoutEditor(ParagraphEditor)>>sendersOfIt {[self > systemNavigation browseAllCallsOn: aSelector]} > TextMorphForShoutEditor(Controller)>>terminateAndInitializeAround: > TextMorphForShoutEditor(ParagraphEditor)>>sendersOfIt > [] in PluggableShoutMorph(PluggableTextMorph)>>sendersOfIt {[textMorph > editor sendersOfIt]} > [] in PluggableShoutMorph(PluggableTextMorph)>>handleEdit: {[result := > editBlock value]} > TextMorphForShout(TextMorph)>>handleEdit: > PluggableShoutMorph(PluggableTextMorph)>>handleEdit: > PluggableShoutMorph(PluggableTextMorph)>>sendersOfIt > UndefinedObject(Object)>>perform:orSendTo: > [] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: > {[(selArgCount := > selector numArgs) = 0 ifTrue: [target perform: selector] ...]} > BlockContext>>ensure: > CursorWithMask(Cursor)>>showWhile: > ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: > ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: > ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: > MouseButtonEvent>>sentTo: > ToggleMenuItemMorph(Morph)>>handleEvent: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>dispatchEvent:with: > ToggleMenuItemMorph(Morph)>>processEvent:using: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>dispatchEvent:with: > ...etc... > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 20, 2009

[Pharo-project] Problem with senders?

by Mariano Martinez Peck

I am trying to see the senders of a message. I select "startsWith:" in a workspace -> right button -> extended search -> senders of it and I get a wallback. If you think this is a bug, let me know and I add it to the issue tracker. Thanks, Mariano MessageNotUnderstood: OBShowSenders class>>of:label: 20 March 2009 1:11:08 am VM: unix - a SmalltalkImage Image: Pharo0.1 [Latest update: #10256] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /home/mariano/squeak/imagenes Trusted Dir /home/mariano/squeak/imagenes/secure Untrusted Dir /home/mariano/squeak/imagenes/My Squeak OBShowSenders class(Object)>>doesNotUnderstand: #of:label: Receiver: OBShowSenders Arguments and temporary variables: aMessage: of: an OBSelectorNode label: 'Senders of startsWith: [4]' exception: MessageNotUnderstood: OBShowSenders class>>of:label: resumeValue: nil Receiver's instance variables: superclass: OBNavigate methodDict: a MethodDictionary(#browserClass->a CompiledMethod (3617) #noChildr...etc... format: 136 instanceVariables: nil organization: ('as yet unclassified' browserClass noChildrenMessage) subclasses: nil name: #OBShowSenders classPool: nil sharedPools: nil environment: Smalltalk category: #'OB-Standard-Announcements' traitComposition: nil localSelectors: nil DEVToolSet class>>browseSendersOf:name:autoSelect: Receiver: DEVToolSet Arguments and temporary variables: aSymbol: #startsWith: labelString: 'Senders of startsWith: [4]' autoSelectString: 'startsWith:' Receiver's instance variables: superclass: StandardToolSet methodDict: a MethodDictionary() format: 2 instanceVariables: nil organization: ('as yet unclassified') subclasses: nil name: #DEVToolSet classPool: nil sharedPools: nil environment: Smalltalk category: #ImageForDevelopers traitComposition: nil localSelectors: nil ToolSet class>>browseSendersOf:name:autoSelect: Receiver: ToolSet Arguments and temporary variables: aSymbol: #startsWith: titleString: 'Senders of startsWith: [4]' autoSelectString: 'startsWith:' Receiver's instance variables: superclass: AppRegistry methodDict: a MethodDictionary() format: 2 instanceVariables: nil organization: ('as yet unclassified') subclasses: nil name: #ToolSet classPool: nil sharedPools: nil environment: Smalltalk category: #'System-Applications' traitComposition: nil localSelectors: nil registeredClasses: an OrderedCollection(StandardToolSet OTToolset DEVToolSet) default: DEVToolSet SystemNavigation>>browseSendersOf:name:autoSelect: Receiver: a SystemNavigation Arguments and temporary variables: aSelector: #startsWith: labelString: 'Senders of startsWith:' autoSelectString: 'startsWith:' title: 'Senders of startsWith: [4]' size: 4 senders: an OrderedCollection(a MethodReference Algernon >> #isMatchingClass:gi...etc... Receiver's instance variables: browserClass: nil hierarchyBrowserClass: nil --- The full stack --- OBShowSenders class(Object)>>doesNotUnderstand: #of:label: DEVToolSet class>>browseSendersOf:name:autoSelect: ToolSet class>>browseSendersOf:name:autoSelect: SystemNavigation>>browseSendersOf:name:autoSelect: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - SystemNavigation>>browseAllCallsOn: [] in TextMorphForShoutEditor(ParagraphEditor)>>sendersOfIt {[self systemNavigation browseAllCallsOn: aSelector]} TextMorphForShoutEditor(Controller)>>terminateAndInitializeAround: TextMorphForShoutEditor(ParagraphEditor)>>sendersOfIt [] in PluggableShoutMorph(PluggableTextMorph)>>sendersOfIt {[textMorph editor sendersOfIt]} [] in PluggableShoutMorph(PluggableTextMorph)>>handleEdit: {[result := editBlock value]} TextMorphForShout(TextMorph)>>handleEdit: PluggableShoutMorph(PluggableTextMorph)>>handleEdit: PluggableShoutMorph(PluggableTextMorph)>>sendersOfIt UndefinedObject(Object)>>perform:orSendTo: [] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: {[(selArgCount := selector numArgs) = 0 ifTrue: [target perform: selector] ...]} BlockContext>>ensure: CursorWithMask(Cursor)>>showWhile: ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: MouseButtonEvent>>sentTo: ToggleMenuItemMorph(Morph)>>handleEvent: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>dispatchEvent:with: ToggleMenuItemMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>dispatchEvent:with: ...etc...

March 20, 2009

Re: [Pharo-project] Fwd: [vwnc] Would you start a new Smalltalk project today?

by Antony Blakey

On 20/03/2009, at 1:30 PM, Michael van der Gulik wrote: > So now it seems that Gemstone is the only multi-core capable > Smalltalk VM :-(. And maybe this: http://etoileos.com/ ? Antony Blakey -------------------------- CTO, Linkuistics Pty Ltd Ph: 0438 840 787 Plurality is not to be assumed without necessity -- William of Ockham (ca. 1285-1349)

March 20, 2009

Re: [Pharo-project] Fwd: [vwnc] Would you start a new Smalltalk project today?

by Michael van der Gulik

On Thu, Mar 19, 2009 at 10:02 AM, Michael van der Gulik <mikevdg(a)gmail.com>wrote: > > > If you want to use multiple CPU cores, I believe that ST/X and Gemstone > both do this. I haven't tried though. > > Smalltalk/X: http://www.exept.de/ > Gemstone: http://seaside.gemstone.com/ > > I'm sorry, I lied. Smalltalk/X can *not* use multiple cores. I tried it on a dual-core system; only one core was used :-(. So now it seems that Gemstone is the only multi-core capable Smalltalk VM :-(. Gulik. -- http://gulik.pbwiki.com/

March 20, 2009

Re: [Pharo-project] [squeak-dev] Organising and Documenting Micro-Universes in Squeaksource

by Keith Hodges

Damien Pollet wrote: > On Thu, Mar 19, 2009 at 22:46, Keith Hodges <keith_hodges(a)yahoo.co.uk> wrote: > >> I have long been frustrated that there is no place in squeaksource for >> documenting what is in a repository, and offering feedback as to what >> works where. >> > > Yes, and the MC tools should support that IMHO. > It was one of the first ideas I was going to add to MC, even just to have a simple text file explaining what is going on in a repo. I put a lot of effort into MC to bring the forks together, and make it maintained and able to move forward with one voice. That failed, so my motivation for hacking MC anymore is pretty low. > BTW I'd also add: no nice support for named/tagged branches (I mean, > in a big project there should be released/working/devel/in-progress > branches, or at least documented sequences of snapshots for stable > versions, and we have > package-developerUniversallyKnownToNotRegularlyBreakThings.biggestNumber.mcz) > My brain struggles with branches. Perhaps not having them is a good idea? >> I have started to use Sake/Packages as a kind of micro "universe" for my >> Seaside "Client" UI & Backend Component Framework. Having seen how >> useful this is I thought that this might be useful for pier, and of >> course seaside and other projects. >> > > Yup, I like the idea. Great! >> Some have reservations about Sake/Packages because they say it is not >> declaritive. >> > > Huhâ¦ it's a rule system, right ? The alternative I know about being > scripts that explicitly load snapshots in sequence, I fail to see > where sake is not declarative. > Its because the rules to load: a package can be blocks executing an arbitrary script. In normal use the #defaultAction is to process the given "declared" url to find the package to load. > From my discussions on the subject, problems are more about the > perception of what level of predictability and control one would get > by using sake. Questions like "how do I know what will get installed > if I pull this one" (Package named: 'SomePackage) what explore. This could be improved to ask Installer exactly what it will install, perhaps - (Package named: 'SomePackage) whatUsingDryRun explore. Also with DeltaStreams integration with Installer, we might have the ability to load into a "Delta/SystemEditor" rather than actually in to the image. > or "how do I install this, but with this > particular version of that", and so on. Maybe it's a problem of > Interesting point. I cant think of how to do that. Unless you use sake to generate a script or a task data scructure, and then you manually edit it. How about merging two dependency trees like so: (Packages current named: 'Seaside) using: (Packages beta named: 'Pier) > polishing the DSL, of documentation, maybe of tools, I'm not sure; > that could be investigated a bit more. > Can never get enough Documentation! > For me it's clear that automatic dependancy management is the way to > go, though the squeak/pharo community does not have resources or > organization like debian's, so I think we need a more decentralized > and agile way of managing dependancies, detecting and resolving > incoherencies, etc. > Bob might be able to do something like that in the future. He is sitting there monitoring a number of repositories, he could periodically process contributions and derive dependencies because he has some knowledge of the big picture. Keith

March 20, 2009

Re: [Pharo-project] How to rename a package ?

by Keith Hodges

Lukas Renggli wrote: >>> Long answer: By renaming all the categories and protocols (this can be >>> automated using the OB-Refactoring and OB-Regex tools), creating a new >>> >> Would those support finding orphaned package extensions? Especially with >> removing stuff and reorganizing we will have that need occasionally. >> > > No, but the following remnant from the Seaside 2.9 packaging effort does: > > | packages | > packages := MCWorkingCopy allManagers > collect: [ :each | each packageInfo ]. > Smalltalk organization categories do: [ :cat | > (packages anySatisfy: [ :pak | pak includesSystemCategory: cat ]) > ifFalse: [ Transcript show: 'Category: '; show: cat; cr ] ]. > Smalltalk allClassesAndTraitsDo: [ :class | [ :cls | > cls organization categories do: [ :cat | > (packages anySatisfy: [ :pak | pak includesMethodCategory: cat ofClass: cls ]) > ifFalse: [ Transcript show: 'Class: '; show: cls; show: ' Protocol: > '; show: cat; cr ] ] ] > value: class; value: class class ] > > Lukas > Why why why is the default position of whoever wrote the above code to NOT contribute to the community? I dont get it. For me it would be the first thought that enters my mind... "perhaps someone else might find this useful". That code if properly factored could easily go straight into MCWorkingCopy. It can do, the squeaksource.com/mc repo is open for contributions, and has been for a long time. Keith

March 20, 2009

Re: [Pharo-project] [squeak-dev] Organising and Documenting Micro-Universes in Squeaksource

by Damien Pollet

On Thu, Mar 19, 2009 at 22:46, Keith Hodges <keith_hodges(a)yahoo.co.uk> wrote: > I have long been frustrated that there is no place in squeaksource for > documenting what is in a repository, and offering feedback as to what > works where. Yes, and the MC tools should support that IMHO. BTW I'd also add: no nice support for named/tagged branches (I mean, in a big project there should be released/working/devel/in-progress branches, or at least documented sequences of snapshots for stable versions, and we have package-developerUniversallyKnownToNotRegularlyBreakThings.biggestNumber.mcz) > I have started to use Sake/Packages as a kind of micro "universe" for my > Seaside "Client" UI & Backend Component Framework. Having seen how > useful this is I thought that this might be useful for pier, and of > course seaside and other projects. Yup, I like the idea. > Some have reservations about Sake/Packages because they say it is not > declaritive. Huhâ¦ it's a rule system, right ? The alternative I know about being scripts that explicitly load snapshots in sequence, I fail to see where sake is not declarative. >From my discussions on the subject, problems are more about the perception of what level of predictability and control one would get by using sake. Questions like "how do I know what will get installed if I pull this one" or "how do I install this, but with this particular version of that", and so on. Maybe it's a problem of polishing the DSL, of documentation, maybe of tools, I'm not sure; that could be investigated a bit more. For me it's clear that automatic dependancy management is the way to go, though the squeak/pharo community does not have resources or organization like debian's, so I think we need a more decentralized and agile way of managing dependancies, detecting and resolving incoherencies, etc. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

March 20, 2009

Re: [Pharo-project] [Vm-dev] newDelta >0 failed in sqUnixMemory -- Was Re: Incompatibility between Pharo and Seasidehosting

by Mariano Martinez Peck

On Wed, Mar 4, 2009 at 5:39 PM, <bryce(a)kampjes.demon.co.uk> wrote: > StÃ©phane Ducasse writes: > > creating a unix vm. > > Here's a Unix VM built with an up to date VMMaker and a Windows VM: > > http://ftp.squeak.org/Exupery/vms/exupery-vm-0.15-linux.tz > http://ftp.squeak.org/Exupery/vms/exupery-vm-0.15-win32.zip > > Both have the closure bytecodes and the FreeType bitblit extensions. > The Linux VM includes the FreeType plugin, the Windows VM doesn't. > Good job man!. I really notice a difference in response time. For me, in Linux, it seems to be faster than standard VM. However, In windows, It seems it doesnt work te FreeType plugin. My fonts are not nice :( any idea? The same image, but with standard VM, FreeType works well. thanks, Mariano > > Bryce > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 20, 2009

[Pharo-project] Could not merge changes... DNU

by StÃ©phane Ducasse

PSMCmergePatchMorph>>selectNextConflict "Select the next conflict after the current selection, if any." |next def| next := self nextConflict ifNil: [^self]. def := next remoteDefinition ifNil: [next localDefinition]. self changed: {#changes. #openPath. next targetClassName asString. def selector asString} def = a MCOrganizationDefinition(#(#'System-Object Events')) and does not understand selector

March 19, 2009

[Pharo-project] can load System-Platforms-michael_rueger.1 from inbox

by StÃ©phane Ducasse

so we will move it to threated Stef

March 19, 2009