1) This amount of debate and controversy is *exactly* why I was/am/will be in favor of keeping R1 as close to R5 as possible. I think that these conversations are good and valuable, don't get me wrong, but I think that there is always the potential to distract from completing R1. :-/
2) Having said that, what Chris said blends in nicely to the "design" (ideas, really) that I was talking about earlier: BNotification wraps BMessage and BMessanger to make a "Kit" (really this should go in the Interface Kit, at some point). Send() sends the message to some predefined mime type. By default, there is a Snarl-esque little popup view thing. Maybe an icon in the deskbar and allows you to turn them on or off or go to preferences.
Now, Niels, hating beyond all measure (teasing!) the little Snarl-esque app, takes it out of his startup folder and puts "SystemLogger" there in its place. SystemLogger is a little app that appends each message to a textfile and is able to scroll through that file, displaying some lines at a time using Haiku's mmap functionality (FTW!).
Everyone is happy. The API is simple, easy to write, straightforward and very Be-like. Developers are happy because they have notifications. Users are happy because they can manage their notifications and even how they view them. And the style police are happy because we use Little Apps That Do One Thing.
Ryan Leavengood wrote:
On 5/24/07, Chris Peel <chris.gsi@xxxxxxxxxxxx> wrote:[snipping good stuff]You'd construct a BNotificaton object, fill in the Setxxx() fields then call Show() - this would send the notification information to the daemon which would then decide whether it should be displayed or not (and where on-screen, and in what colour/style, etc.) Just my rather long 2c...What you described is *exactly* what I was thinking. Do you want to help with this? I'm not even kidding, your experience with Snarl could be invaluable. Thinking I may still do this despite my earlier email to Niels, Ryan
