jason at keirstead.org
Tue Mar 25 16:14:09 GMT 2003
On March 25, 2003 11:47 am, George Staikos wrote:
> The screenshot looks good, and I think we probably should have a global
> OSD. However you should have a look at all the OSDs in KDE. There is one
> in kdeui, one in kdeaddons, at least one in kdenonbeta, and of course this
> one in kdelibs. Does it provide everything that those ones need? The one
> in kdenonbeta, and soon the one in kdeutils, are "skinnable" for instance.
> You can make the OSD look how you like. The one that you display in the
> screenshot does not look like it will work too well for all applications,
> and in that case, it should either be enhanced or used just in specific
> cases and not kdeui.
As well, I feel a big thing missing from the KNotify display classes (passive
popup and the regular popup ), is a way to get feedback from the user
to respond to the notification.
An example would be, instead of
KNotifyClient::event (StandardEvent event, const QString &text=QString::null)
you could have
KNotifyClient::event (StandardEvent event, const QString &text=QString::null, const QString &handleText = QString::null, const char* handleSlot = 0L )
... where handleSlot is a slot that is fired when the user signals a response within the popup.
- Within the passive popup, the hanldeText could be a link you can click on
- Within the normal popup, it could be a KPushButton with the text on it
Uses for this would be, example in KMail, instead of just saying "New Mail Arrived" (ok) in the
popup, it could say "New Mail Arrived (Click To View) (Cancel)" in the popup. Many other apps
could use a way to get feedback from a graphical KNotify event as well.
Jason Keirstead, BCS
More information about the kde-core-devel