On 3/3/06, Stefan Urbanek <[EMAIL PROTECTED]> wrote:
> Citát Nicolas Roard <[EMAIL PROTECTED]>:
>
> However, I do not agree with your opiniton about menu separators :-) good
> space
> is enough, bars just add noise to the menu. Users are already accustomed to
> click on grouped letters (menu label)
I would tend to agree, but separators turns them into "real buttons"
and keep things more consistent.. I'll need to wait for the next
"subdued" version with lighter separators to make my mind definitely.
> > It's very nice ! NSStatusBar should be modified to work as a "menulet"
> > then...
>
> ?
to have NSStatusBar directly included in the menu.
> > One thing though, the service menu should probably be a button at the
> > left of the application name -- we want it easily accessible...
> >
>
> No, services menu at the end is not bad position, it is easily accessible
> because it is "the last menu item", and you use it less frequently compared to
> other menus in the application. what is more important about the services menu
> is, that it should stay as the top-level menu. Apple put the menu iside the
> application menu and therefore made services non-accessible. I use them less
> frequently, because they are just too deep...
They are used less frequently because we're not used to them ;-) but
étoilé wants to use them more.. And, more importantly, Services are
independant of the current application -- they are dependant of the
selection. Thus putting the service menu before the app menu make
sense, and it will be in a fixed position too.
> Another suggestion for top-level menus:
> - scripting menu (shared across applications) - on Apple it is a menu with
> paper
> leaf icon instead of a label
> - object menu
>
> The "Object menu" should have similar function to right-click contextual menu
> and/or the apple menus on different places depicted with teethed-wheel icon,
> for example like the one in finder. The entries in that menu would mean "what
> I
> can do with selected or object". Content will change depending on the
> selection. That would require new concept inside the application: focused
> object:
>
> object = [[NSApp sharedFocus] object];
> menu = [NSMenu menuForObject:object];
>
> and each class would implement:
>
> MyObject:NSObject
> + objectMenu
> {
> ... get supermenu ...
> ... add items either at top or at bottom ...
> ... return the menu ...
> }
>
> Having the contextual object menu in the menu bar will make it visible (not
> obscure as it is on all systems), and will provide common place where user
> will
> be able to find the menu.
Excellent idea !!
For this one I'd prefer to have it as the last top-level menu item, as
it is dependant of the app yet we want it to be in a somehow fixed
position for easy access.
>
> As for the label, i would suggest to use something similar to apple's
> teethed-wheel icon - takes less space than a label, is easily spottable.
agree.
--
Nicolas Roard
"Any sufficiently advanced technology is indistinguishable from magic."
-Arthur C. Clarke
_______________________________________________
Etoile-dev mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-dev
