#1245: implement notification service and API ----------------------------------+----------------------------------------- Reporter: wkornewald | Owner: stippi Type: enhancement | Status: in-progress Priority: normal | Milestone: Unscheduled Component: Kits/Application Kit | Version: R1/Development Keywords: | Platform: All Blockedby: | Patch: 0 Blocking: | ----------------------------------+----------------------------------------- Comment(by plfiorini): Replying to [comment:14 axeld]: > I agree with stippi about BNotification - it seems pretty much superfluous at one side (vs. just using a BMessage), and unnecessarily inflexible at the other side. > > For example, shouldn't it be possible to send a flattened BView to show as a notification (using the replicant mechanism)? I think limiting that to an icon and some plain text is very limiting for no good reason. That sounds good but I don't want people to mess up with the style of a notification window. Probably, a notification should always have a title, an icon and a content as specified by the BNotification setters, and have one or more optional BViews added after the content message using BNotification::AddChild. Then the notification_server might create NotificationViews using layouts (and probably the option to set the title above the icon or all the text right of icon should go away having a layout with an icon and all text and views right of it). Going to look how GNOME does with notifications since I've seen an update notification using an icon a text and a button... -- Ticket URL: <http://dev.haiku-os.org/ticket/1245#comment:18> Haiku <http://dev.haiku-os.org> Haiku - the operating system.