Felipe Monteiro de Carvalho wrote:
On 1/31/07, Marc Weustink <[EMAIL PROTECTED]> wrote:
Thinking of it, isn't the dock comparable to the taskbar/quicklaunch ?
So showing it there is already something the user decides.
Yes, but we need to provide a menu for the Dock. Windows/Linux apps
don´t provide themselves the menu for the taskbar.
Windoes apps do have it, but it is not always used. You can add items to
the application menu.
For linux I don't know, but I guess it is very depending on what WM is used.
If the trayicon abstracts the Dock, we have a kind of cross-platform
way to deal with it.
If we add support for an application menu, then we have that also. Then
a tray icon can have its own abstraction (no idea for linux yet)
If you need a dock menu, but not a tray icon on other platforms, put
ifdefs around the code that shows trayicon. It´s a lot less
platform-dependent code then implementing a dock menu on Carbon
yourself. And we would probably need a component to abstract the Dock
anyway.
I see the dockmenu similar to the app menu.
So I think the trayicon should be implemented as menuicon, whith the
constraint that it is default off and only can be shown after configured
by the user.
ummm ... not sure what you mean by off by default. The trayicon is the
only way to interact with some software, like the magnifier for
example, so it must be on after it is executed.
In that case, it must be on.
But I still think it is better to let the user choose. When you launch
it the first time, the user has to choose if it is launched as normal
app so it goes to the dock for launched apps or if it should be shown as
menuitem.
But this is indeed an aplication desing level decision and not a LCL level.
Marc
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
