My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for
ApplicationsTabIdeas  
The Applications tab needs a remodel. Let's brainstorm.
Phase-Requirements, Phase-Design
Updated Mar 31, 2010 by prhgr...@gmail.com

Introduction

This is not The Plan—this is just a place to write ideas worth exploring or at least thinking about.

Ideas

  • By i.atent.dead on the discuss list (http://groups.google.com/group/growldiscuss/msg/dd8b3e2ca76f4974):
    • Indicate apps that seem to support Growl (have a Growl framework) but are not registered with Growl
    • Indicate apps that are no longer installed
    • Possibly warn the user when they attempt to configure an app that is not registered or is not installed —prh
  • prh: I envision three to four columns:
    1. Applications
    2. Notifications for this application
    3. Actions for this notification
    4. (Possibly) Settings for the action
The settings would go into either that fourth column, the lower half of the third column, or a sheet, depending on space.
Actions, as previously discussed elsewhere, are a superset of displays. An action can be a display, or a script, or another action such as sending an email message.
This UI is easily modeled, and that model would generalize easily to the rest of Growl. No more notification dictionaries!
Comment by project member chrisf.g...@gmail.com, Apr 3, 2010

We could fit the ui into this that you envision prh:

In the apps tab on the apps list column, we could have a main title with disclosure triangles.

Comment by prhgr...@gmail.com, Jun 11, 2010

Chris: Bleh, Google Code hates embedding images from tickets into wiki pages. For anyone reading, that's “GROWLApplications.png” from #95 (http://code.google.com/p/growl/issues/detail?id=95).


Sign in to add a comment
Powered by Google Project Hosting