[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KNotificationItem class name is confusing
From:       Andreas Hartmetz <ahartmetz () gmail ! com>
Date:       2009-10-28 23:38:01
Message-ID: 200910290038.02010.ahartmetz () gmail ! com
[Download RAW message or body]

On Wednesday 28 October 2009 16:46:31 Aurélien Gâteau wrote:
> Thomas Lübking a écrit :
> > Am Wednesday 28 October 2009 schrieb Aurélien Gâteau:
> >> I like it, but it's a bit long. Maybe "Persistent" could be removed?
> >> KWorkspaceStatusItem sounds better to me.
> >
> > Afaiu this does not entirely describe neither the element nor the
> > protocol, mainly as it also provides input communication (interaction)
> >
> > Though this might not sound serious or complex enough, my /personal/
> > preference would still be :
> > 	KApplicationOutpost & KSystemOutpost
> > or (if the names sound too military)
> > 	KApplicationEmbassy & KSystemEmbassy
> >
> > Where KApplication* is a app specific subclass of the more generic
> > KSystem*
> 
> Funny, my initial suggestions on xdg@ were:
> 
> - AppSatellite
> - SatelliteItem
> 
I really like SatelliteItem. A satellite [at least the currently common type] 
is spatially (ha!) detached from the rest of the structure it is a part of, 
and exchanges information with the rest of the structure. Also, its main 
purpose is usually exchange of information.
IMHO satellite area/space is also a good name for the systray.
Satellite is also a much shorter word than the other suggestions :)
It even sounds interesting, NotificationItem sounds dull.

> Aurélien
> 

[prev in list] [next in list] [prev in thread] [next in thread]