[Pharo-project] Feature: SystemOrganizer class>>default returns SystemOrganization
In Pharo inbox: System-Support-SeanDeNigris.291 Motivation: I was trying to delete a category, and found SystemOrganizer via Method Names. It wasn't immediately obvious how to use it, so I had to whip out SBE to remind me of SystemOrganization. In SystemOrganizer: * Added (overrides Categorizer class>>default): SystemOrganizer class>>default ^ SystemOrganization * updated class comment Sean p.s. also submitted to Squeak inbox -- View this message in context: http://forum.world.st/Feature-SystemOrganizer-class-default-returns-SystemOr... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Please no, we need to get rid of this global and move it to an instance variable of SystemDictionary. Like this (and with a few patches to class builder) we have working namespaces. Lukas On 18 May 2010 16:44, Sean P. DeNigris <sean@clipperadams.com> wrote:
In Pharo inbox: System-Support-SeanDeNigris.291
Motivation: I was trying to delete a category, and found SystemOrganizer via Method Names. It wasn't immediately obvious how to use it, so I had to whip out SBE to remind me of SystemOrganization.
In SystemOrganizer: * Added (overrides Categorizer class>>default): SystemOrganizer class>>default  ^ SystemOrganization * updated class comment
Sean
p.s. also submitted to Squeak inbox -- View this message in context: http://forum.world.st/Feature-SystemOrganizer-class-default-returns-SystemOr... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli www.lukas-renggli.ch
Sean Thanks for submitting this change. this is fun that this changes was accepted in Squeak because people were constantly mad that we introduce singleton instead (SystemNavigation default... SmalltalkImage current of global variables :). Time is changing. Good! Now can we do it better :) what I would love it if we can have SystemOrganization be an instance variable of the SystemDictionary and may be returned by the categorizer message sent to Smalltalk globals. This way each instance of SystemDictionary would have its own SystemOrganizer instance. This will make sure that people can experiment with alternate semantics and that we do not have one monolitic system :) Stef
In Pharo inbox: System-Support-SeanDeNigris.291
Motivation: I was trying to delete a category, and found SystemOrganizer via Method Names. It wasn't immediately obvious how to use it, so I had to whip out SBE to remind me of SystemOrganization.
In SystemOrganizer: * Added (overrides Categorizer class>>default): SystemOrganizer class>>default ^ SystemOrganization * updated class comment
Sean
p.s. also submitted to Squeak inbox -- View this message in context: http://forum.world.st/Feature-SystemOrganizer-class-default-returns-SystemOr... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Stéphane Ducasse wrote:
Now can we do it better :) what I would love it if we can have SystemOrganization be an instance variable of the SystemDictionary and may be returned by the categorizer message sent to Smalltalk globals. This way each instance of SystemDictionary would have its own SystemOrganizer instance.
Sounds good. I might be able to do that if I had more detail. Also, until that refactoring is done, it would be helpful to make SystemOrganizer easier to use - if not the method, maybe at least the class comment? Stéphane Ducasse wrote:
This will make sure that people can experiment with alternate semantics and that we do not have one monolitic system :)
Sounds interesting (even though I'm not sure exactly what that means, lol). Maybe I'll do a little digging here... Sean -- View this message in context: http://forum.world.st/Feature-SystemOrganizer-class-default-returns-SystemOr... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Sounds good. Â I might be able to do that if I had more detail.
Also, until that refactoring is done, it would be helpful to make SystemOrganizer easier to use - if not the method, maybe at least the class comment?
Currently it is impossible to instantiate a new namespace and open a browser on it, because the organization is global. If the organization would be a variable of the namespace (SystemDictionary) and not a global, there would be no such problem: Smalltalk globals organization Lukas -- Lukas Renggli www.lukas-renggli.ch
Right now SystemOrganization is a global stored in SystemDictionary. And it would be nice to have a new instance named organizer held by SystemDictionary that points to the organizer associated with the SystemDictionary. Similarly it would be good not to point to the global but use this new methods. I imagine that it requires some care. Now if you have a class comments please send it we will integrate it: add it to the bug tracker. I'm a bit worry to introduce a "singleton" Stef
Stéphane Ducasse wrote:
Now can we do it better :) what I would love it if we can have SystemOrganization be an instance variable of the SystemDictionary and may be returned by the categorizer message sent to Smalltalk globals. This way each instance of SystemDictionary would have its own SystemOrganizer instance.
Sounds good. I might be able to do that if I had more detail.
Also, until that refactoring is done, it would be helpful to make SystemOrganizer easier to use - if not the method, maybe at least the class comment?
Stéphane Ducasse wrote:
This will make sure that people can experiment with alternate semantics and that we do not have one monolitic system :)
Sounds interesting (even though I'm not sure exactly what that means, lol). Maybe I'll do a little digging here...
Sean -- View this message in context: http://forum.world.st/Feature-SystemOrganizer-class-default-returns-SystemOr... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On May 18, 2010, at 11:42 AM, Stéphane Ducasse [via Smalltalk] <ml-node+2221496-1604744895-217701@n4.nabble.co m> wrote:
Right now SystemOrganization is a global stored in SystemDictionary. And it would be nice to have a new instance named organizer held by SystemDictionary that points to the organizer associated with the SystemDictionary. Similarly it would be good not to point to the global but use this new methods. Ok, I undertand more now
Now if you have a class comments please send it we will integrate it: add it to the bug tracker Okay I'll remove mention of it from the class comment and resubmit.
I'm a bit worry to introduce a "singleton"
It seemed to me like I was just, in effect, clarifying access to an existing singleton, no? Thanks for the explanations. Sean -- View this message in context: http://forum.world.st/Feature-SystemOrganizer-class-default-returns-SystemOr... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
participants (3)
-
Lukas Renggli -
Sean P. DeNigris -
Stéphane Ducasse