TheWorldMenu, TheWorldDockingBar

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

TheWorldMenu, TheWorldDockingBar

Frank Shearar-3
These guys live in Morphic, and they thus cause a whole bunch of
things to depend on Morphic.

While I do think something called "TheWorldMenu" is rather clearly a
UI thing, I don't think it's necessarily a _Morphic_ thing.

One way to approach this is to move TheWorldMenu and
TheWorldDockingBar into another package. Perhaps System-Support,
because that's where Project lives. Or perhaps System-World.

Then we move all Morphic referencing methods to *Morphic, and so on.
There are a fair number of these!

Alternatively, we implement a registry thing, and TheWorldMenu and
TheWorldDockingBar reference this registry to build its list of tools.

Thoughts?

frank

Reply | Threaded
Open this post in threaded view
|

Re: TheWorldMenu, TheWorldDockingBar

Chris Muller-3
> While I do think something called "TheWorldMenu" is rather clearly a
> UI thing, I don't think it's necessarily a _Morphic_ thing.

I think the "basic desktop UI" could be considered part of Morphic.
If other UI frameworks want to have a "world menu" they will implement
their own rather cloning Morphic's.

> One way to approach this is to move TheWorldMenu and
> TheWorldDockingBar into another package. Perhaps System-Support,
> because that's where Project lives. Or perhaps System-World.
>
> Then we move all Morphic referencing methods to *Morphic, and so on.
> There are a fair number of these!
>
> Alternatively, we implement a registry thing, and TheWorldMenu and
> TheWorldDockingBar reference this registry to build its list of tools.

There is already WorldMenuProvider which is part of the Services
framework.  We should investigate whether that could/should be used
before implementing new stuff.

Reply | Threaded
Open this post in threaded view
|

Re: TheWorldMenu, TheWorldDockingBar

Frank Shearar-3
On 1 June 2013 16:46, Chris Muller <[hidden email]> wrote:
>> While I do think something called "TheWorldMenu" is rather clearly a
>> UI thing, I don't think it's necessarily a _Morphic_ thing.
>
> I think the "basic desktop UI" could be considered part of Morphic.
> If other UI frameworks want to have a "world menu" they will implement
> their own rather cloning Morphic's.

Well, it's just a name. If Morphic wants to keep it it should have a
MorphicWorldMenu. "TheWorld" sounds bigger than Morphic. Regardless,
we need a way for apps (like the MC tools) to say "hey, I think I'm
important enough to warrant a menu item if this UI has such a thing".

>> One way to approach this is to move TheWorldMenu and
>> TheWorldDockingBar into another package. Perhaps System-Support,
>> because that's where Project lives. Or perhaps System-World.
>>
>> Then we move all Morphic referencing methods to *Morphic, and so on.
>> There are a fair number of these!
>>
>> Alternatively, we implement a registry thing, and TheWorldMenu and
>> TheWorldDockingBar reference this registry to build its list of tools.
>
> There is already WorldMenuProvider which is part of the Services
> framework.  We should investigate whether that could/should be used
> before implementing new stuff.

I'll take a look at the WorldMenuProvider. It sounds promising!

frank