"Tools" -> "more" removed from PharoCode 1.1...intentionally ? (alain ?)

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

"Tools" -> "more" removed from PharoCode 1.1...intentionally ? (alain ?)

Mariano Martinez Peck
Hi folks. In Pharo 1.0 we use to have under "Tools" -> "More" some tools like:

Language Editor
Language Editor For
Monticello Browser
Monticello Configurations
Preference Browser
Recent Submissions
Search Browser
Services Browser
Test Runner

However, in Pharo 1.1 there is not even a "more" menu item.

I saw the following issues:

http://code.google.com/p/pharo/issues/detail?id=1937
http://code.google.com/p/pharo/issues/detail?id=1945

but I am not sure if I understand. Alain said something has to be done in ImageForDevelopers...

Thanks

Maruano

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: "Tools" -> "more" removed from PharoCode 1.1...intentionally ? (alain ?)

Marcus Denker-4

On May 11, 2010, at 12:30 AM, Mariano Martinez Peck wrote:

> Hi folks. In Pharo 1.0 we use to have under "Tools" -> "More" some tools like:
>
> Language Editor
> Language Editor For
> Monticello Browser
> Monticello Configurations
> Preference Browser
> Recent Submissions
> Search Browser
> Services Browser
> Test Runner
>

This was where menu items where put when they registered using the old menu registration.

> However, in Pharo 1.1 there is not even a "more" menu item.
>

No. Reasion: tools now can register themselves anywhere in the menu hierarchy.
The missing tools are missing as nobody used them (Language editor) or where removed (Services).

> I saw the following issues:
>
> http://code.google.com/p/pharo/issues/detail?id=1937
> http://code.google.com/p/pharo/issues/detail?id=1945
>
> but I am not sure if I understand. Alain said something has to be done in ImageForDevelopers...
>
>
Tools should use the new pragma based menu registration mechanism and put themselves at a useful
place in the menu.

e.g. this is how the ProcessBrowser does it:

ProcessBrowser>>#menuCommandOn: aBuilder
        <worldMenu>
        (aBuilder item: #'Process Browser')
                parent: #Tools;
                action:[self open];
                icon: self taskbarIcon.



--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project