Paul Cooper wrote:
On Thu, 2009-10-01 at 09:18 -0400, Kris Warkentin wrote:
FreeDesktop.org:
http://standards.freedesktop.org/systemtray-spec/latest/
Equally there's nothing that says we HAVE to have everything on FDO.
Using the systray when it's there is not broken, but using it the way a
small number of apps do is broken, even on a desktop system using GNOME
or KDE (the user could choose to remove it).
True enough. I said in another thread that I didn't know if it was a
required or optional feature. I only meant that it has a definition.
> If you really want a system tray, then you can add some other panel with
systray to Moblin 2.1 and it will work. For example you could use
MatchboxII panel to do this.
We've already done this and it does the job. It just doesn't feel like
it belongs...looks a little 'tacked on'.
Why should it be hidden when not in use? Or put another way, if Trype is
sitting on a zone of it's own then when I'm, for example, browsing the
web in another zone it is hidden (from me). What's the difference, other
than you've now added another complex interaction into the system.
This is not completely unreasonable. It's just a usage model that
people would need to get used to, not that there is anything wrong with
that.
Because we don't want the background to be a mess of throbbing
distracting icons?
If you're talking about modifying 3rd party apps to make this sort of
thing happen, then why not just modify them to use the Moblin UI
correctly. Use the notifications, panels, and zones that we already
have. No need for anything else.
If you're talking about doing something like this using the systray spec
then I'd be skeptical it's doable. IIRC applets don't emit a signal when
they change state, so in your example the desktop icon wouldn't know
when to start throbing.
I think you've misunderstood. I wasn't suggesting any sort of action or
throbbing on the part of the icon. I was only talking about giving them
some place to go when minimized/docked. It doesn't need animation but I
thought it would look nice if they had some sort of visual cue when you
hover. A good example is the Wii when you move the pointer over active
areas and get a visible 'swelling' and a tactile vibration in the
controller.
Anyway, I don't want to keep beating a dead horse. Ultimately there's
nothing to stop us from implementing some sort of tray solution of our own.
cheers,
Kris
_______________________________________________
Moblin dev Mailing List
[email protected]
To manage or unsubscribe from this mailing list visit:
http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org
once logged in.
For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists