Summary | Add fluid growl notifications |
Queue | Horde Base |
Queue Version | Git master |
Type | Enhancement |
State | Accepted |
Priority | 1. Low |
Owners | |
Requester | chuck (at) horde (dot) org |
Created | 09/10/2009 (5725 days ago) |
Due | |
Updated | 12/06/2011 (4908 days ago) |
Assigned | |
Resolved | |
Milestone | |
Patch | No |
Version ⇒ Git master
Queue ⇒ Horde Base
about. Think I was confused because it was in the IMP queue (probably
because it was added when Growl was exclusive to dimp).
Growl is apparently no longer free software.
with the desktop is a worthwhile goal, especially with our Ajax GUIs
looking more like desktop apps anyway.
hardcoding application specific parameters into general purpose
javascript code. That is what I do not agree with.
If we wanted to setup some sort of Event firing/listening system
(similar to prototypejs), that would be nifty. But that is not what
this ticket is about.
Growl is apparently no longer free software.
the desktop is a worthwhile goal, especially with our Ajax GUIs
looking more like desktop apps anyway.
State ⇒ Feedback
Growl is apparently no longer free software.
I would rather see improvements with our notification system instead.
Or a growl interface to the notification system. But this should not
be hardcoded in.
I would also like to see the references to 'window.fluid' removed from
IMP's code. Again - extremely software specific. We should not be
including hacks like this in the base code.
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Add fluid growl notifications
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Accepted
growl notifications now that we have them:
window.fluid.showGrowlNotification({
title: "title",
description: "description",
priority: 1,
sticky: false,
identifier: "foo",
onclick: callbackFunc,
icon: imgEl // or URL string
})
http://www.fluidapp.com/developer/
This could even replace the in-browser js notifications if growl is available.