On Oct 14, 2010, at 16:42:13, Pedro Estarque wrote: > I think there are two separate discussions here. > - Is it in Growl's goal to display a progress bar? > - Is there any use to a progress bar at all? > > The first one is not up to me to decide. > The second, in my opinon, is pretty obvious. If the day ever comes that we > achieve a real-time computing experience, then progress bars will be obsolete. > Until then, they are invaluable.
Progress bars *are* nice for some applications. Maybe yours is one of those; I'd say you're in the best position to make that call. However, displaying progress is not what Growl is for. It is for notifying you that something has finished (or failed). It exists mostly so that you don't have to watch a progress bar; you don't have to wait around watching the progress bar to know when the job is done, because the application will tell you through Growl when it is done. If CocoaDialog currently sucks, the correct solutions are (a) to fix it or (b) to write a better version of the same idea. Growl is not an implementation of the same idea. For your make-and-upload-a-zip-file script, you might consider using Transmit to upload the file. This would solve your sucky-progress-bar issue and provide Growl notifications for free, since Transmit supports that itself. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
