> Someone of the Firebug team has already totally blown off this being a > design issue with the comment > "3) We can't satisfied everybody." Yes, that was me.
I definitely didn't want to blow off the discussion and I believe I am one of those who appreciate and listens to any (even negative) feedback that leads to a better solution. I don't think the post was well understood so, let me explain again. The message I wanted to send proposes support for alternative solutions using extensions - and Firebug is strong in the area of extensibility. I believe that the basic activation model built-in Firebug should be primarily easy-to-use and cover majority of use cases. Consequently, the model should be extensible enough so, it's possible to append any new activation features/logic (through extensions) that support other work-flows and/or new features like white/black lists, etc. This approach can also encourage extension developers to create extensions and propose/show better implementation of the activation model UI. Note that there are already Activation APIs in place and I am happy to get any feedback how to improve them. Just to point out my gut feelings. I still think there is no universal solution (based on all feedback collected over the time) that would match every-bodies needs - or at least we haven't been successful with discovering it. It was me who wrote the: http://www.softwareishard.com/blog/firebug/how-to-enable-and-disable-firebug-12/ post and as you could see there was also a lot's of negative feedback. So, this is why I said (#3). Honza --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" 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/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
