And here is the missing reference of the famous but lost in a deep menu tree "Seaside Control Panel":
[1] http://blog.fitzell.ca/2009/03/seaside-server-adaptors.html On Wed, Mar 18, 2009 at 2:04 PM, Lukas Renggli <[email protected]> wrote: >> I never found custom menu items useful because they can't easily be >> moved between images. Since I often start over from a fresh image >> adding custom entries to the menu makes no sense. If a lot of people >> really need this feature, we can put it back. > > What would be cool is a more convenient menu registration mechanism > that gives control over where, when and how a menu item is displayed. > I guess method annotations would be a nice solution again. > > Like this a tool such as "Seaside 2.9 Control Panel" [1] could appear > slightly more prominent than it does today. The menu item is currently > nested within a sub-sub-menu and that is far from optimal. When people > load this extension package, they very likely would also be able to > open this tool conveniently. > > Furthermore such an approach would solve the problem of Rob and > Mariano cleanly. They could just bundle their scripts in a special > package and register them to appear in a custom sub-menu. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
