Desktop Notifications Spec 0.3

[Rodrigo Moya]

On Wed, 2004-09-29 at 14:24 -0700, Christian Hammond wrote:
> On Wed, 29 Sep 2004 14:28:06 -0400, Bryan Clark <bclark at redhat.com> wrote:
> > On Wed, 2004-09-29 at 09:39 -0700, Christian Hammond wrote:
> > > Agreed. Simple messages with a little bit of HTML markup (bold,
> > > italic, etc.) is probably going to be sufficient. I don't see a need
> > > for complex formatting with CSS and such, but if we ever need it,
> > > things can be extended.
> > 
> > Hey ~
> > 
> > Sorry I haven't been back in the discussion much but I was thinking
> > about this the other day and started to realize that we're probably
> > heading in the wrong direction here.
> > 
> > Passing XML or HTML or anything over the wire seems excessive.  I'll try
> > to explain why.  Notifications are essentially a type of dialog, however
> > they are at a lower level of interaction then normal dialogs and modal
> > dialogs.  We have always used glade or pre-constructed dialogs in the
> > application code and then replaced the %s tags with the text that needs
> > to appear at the time.  This is an acceptable solution to dialogs since
> > we never want applications to auto-generate dialog prompts via whatever
> > messages need to be displayed.  The application programmer always knows
> > ahead of time what dialogs might appear when, and roughly what they will
> > say and display.
> 
> I think we're still going overboard. Why should the protocol care how
> it's layed out? Shouldn't that be the particular UI impementation's
> job?
>
exactly, take into account that some notification implementations could
decide to send the notification by email, or through a cell phone, so
forcing any kind of UI in the notification would make the job of these
particular notifications implementations too hard, if they need to
parse/convert the specific UI.

So, again, I'd vote for just having the simplest thing in the
notification (maybe using a basic markup for bold, etc), but nothing
more.
-- 
Rodrigo Moya <rodrigo at gnome-db.org>