[haiku-development] Re: Notification Server?
- From: "Jonas Sundström" <jonas@xxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 24 May 2007 15:41:02 +0200 CEST
"Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> wrote:
> "Jonas Sundström" <jonas@xxxxxxxxxxx> wrote:
> > Have the notification class (Blurt ;) create attributed files in
> > ~/Notifications/, or something like it*, (Application Messages?)
> > instead of directly targetting the popup window thing.
>
> Besides that this wouldn't work on LiveCDs, I think it would be far
> easier to optionally implement a persistent logging feature than the
> other way around.
Are these notifications truly essential for LiveCD use?
Would the LiveCD even load a Deskbar hosted notification replicant,
when it's missing its security code attribute? I'm thinking there won't
be a security code until Deskbar runs off a writable volume, no?
In case the volume is write protected there could be a simple GUI alert
implemented by the notification class as a fallback mechanism. Problem
solved, IMO.
I know they are not a silverbullet, but files and queries, would -
empower- people, even non-coders, to create their own solutions, to
make scripts and utilities that react to the notification of
applications, like uploads/downloads/transfers/conversions/connects/
disconnects/etc.
When the feature by default isn't primarily intended to always
interrupt the user the possilibity appears to use the notifications for
more than just "popups". It could be used to expose application state
in a non-GUI way, which could be useful for all kinds of things. The
application scripting that Be created isn't exactly the most user
friendly. IMO, of course.
/Jonas Sundström.
Other related posts:
