On Mon, 2005-10-17 at 13:12 +0100, Joao Inacio wrote: > > I don't know exactly how to do this without taking up to much screen > > real estate or clutter the prefs dialog. We could use two tabs > > "Available Handlers" and "Unavailable Handlers" or something like that. > > We could also use an expander but it doesn't fit that good in the > > current layout. > > Then there's an external dialog (activated by a button in prefs)... > > > > Hmm how about showing all handlers? > the ones who dont want to load could be shown diferently (a change in > color?) and if i try to activate one, a pop up would open with a > textview containing the console messages? > or is it too much work to intercept these? > What I don't get is why display handlers that cannot be loaded anyway ? The error message is just for debugging purpose, it isn't even translated. If the "requirements" function return False, the handler cannot be loaded, that's it, there is no point in showing it. Why would i see Galeon or mozilla handlers if i'm not using them ? They would just take place and serve no useful purpose.. I don't see other cases in the current situation where a module could usefully display an error message.. Either it crashes and then it's a bug, or it works and it's fine. If the module don't want to be loaded, we just don't load it.. Does that sound convincing ? Raf
Attachment:
signature.asc
Description: This is a digitally signed message part