On Tue, 2005-10-18 at 00:12 +0200, Mikkel Kamstrup Erlandsen wrote: > When we (or others) start introducing more complex handlers it will be > nice to be able to produce feedback in some sane non-intrusive way. > > I really understand that we don't want to sprinkle unused handlers > around in the GUI, that was also why I asked you guys if you had any > ideas... > I still believe that there should be some way or other (not involving a > terminal) to discover all the handlers. > Point taken after seeing the google live handler i realize there is need for such handling. I propose the following UI discussed with mikkel on IRC: Current active handler selector: |-------------- | | | | |-------------- Note: blah [Show failed handlers] You click on it, and it show a list view with each failed handler, along with a message for the failure, a bit like active handlers have name +description. Is that a good UI, or maybe we need somthing better ? like having one single handler list, and only show acive handlers in it, then if a checkbow is clicked ([X] Show all handlers) the erratic handlers would be displayed greyed out, with the error replacing the description ? Raf
Attachment:
signature.asc
Description: This is a digitally signed message part