Quotes are getting pretty deep, so I'm clipping some. Hopefully it'll be clear who is speaking in each quote :).
> > > If you would like to write an extension to view and manipulate the > > > page annotations, we would be happy to help. Dumping the list of > > > annotations to the Console would be fairly easy. Removing entries > > > would also not be difficult, though you can do that by visiting the > > > page and then turning Firebug off. Add entries is much harder, and you > > > can do that now by opening the page then opening Firebug. > > > Wow. This attitude stuns me. You are saying that it is *my* > > responsibility to manage the core functionality of FireBug either by > > pencil and paper or by writing my own add-on. Simply put: if FireBug > > keeps a list of sites that *controls how FireBug operates*, then IMHO > > FireBug *must* provide a way for me to view/manage that list of sites. > > Providing this function is on the list of things that could be done to > improve Firebug. It is not at the top. This is different from your previous position and, TBH, is more in line with what you'd expect of any software project. You can't do everything at once, so you have to prioritize. I just hope that this isn't a platitude to end the conversation, but rather something that is tracked and discussed in earnest. > > > To disable all existing annotations, use Firebug Statusbar icon right > > > click "Off for all pages". > > > Yes, I see this now. I don't understand why this is in neither > > FireBug's Window's menus nor FireFox's FireBug menu tree. These are > > pretty important functions so you'd think they'd be in several places > > instead of just one relatively hidden one. > > Opinions differ. I never use those other things and they are much > less convenient. Per Rako's comment, you need to target different user knowledge levels. Considering how blissfully verbose FireFox's FireBug menu tree is, I think it's a no-brainer to add the status bar icon's right-click menu options there. > So we agree on something, that's good. Yuppers. I think the tone of this discussion started a little hostile, but I'm guessing that it is more a case of having a bad day rather than being truly hostile. In any case, FireBug is a best-in-class tool that I'm getting for free so how unhappy can we be? :D > The current activation model is both the simplest version we have had > and the one we have now. There is no possibility that I will work on > an alternative. As you mention later, if a tab-oriented implementation was presented to you, you'd consider it. So what you meant here was that you are not planning to work on any alternatives _now_, but you will consider all viable FireBug improvements for the future, right? Assuming this is the case, that's a perfectly acceptable position. As a user, I'm not privy to the design and support information that you are, so I can't speak with authority. All I can do is outline my observations, experiences, and suggestions for consideration and I think I've accomplished that for this case. > Firebug tracks activations per site because I listened to the "massive > amount of user complaints" and implemented "Activate Same Domain". If > you prefer, you can turn that option off under Firebug Icon Menu > > Options > Activate Same Domain. Tone aside, that first sentence says a lot. It says that not only is FireBug committed to listening to the needs of its users, but it implies that tab-oriented activation was used by previous versions. Was tab-oriented used in previous versions? There was probably a lot of discussion before changing to the current model -- where are those discussions? We shouldn't need to rehash them now. Is the tab-oriented version's activation code still viable in FireFox 3.5+? If so, perhaps you could give some guidance on having someone port that functionality into a 1.4 test offshoot? It could perhaps even lead towards having both activation models in FireBug and letting the user choose one. Also, I can't find "Firebug Icon Menu > Options > Activate Same Domain" anywhere. I assume you mean "FireFox's Tools > FireBug > Options > Activate Same Origin URLs". In conclusion, let me point out that there may be no "right" activation model for FireBug. Some people will prefer one while others will prefer another. The fact is that you can never please everyone with when it comes to UIs. IMHO this is where things like use cases matter most. If you define the use cases that FireBug is meant to support, then the decision of an activation model becomes much easier. Thus this entire thread has two underlying goals: 1) to enumerate an unsupported use case of mine within the current activation model (namely being unable to view/manipulate the site activation list) and 2) to suggest an alternative activation model that would better satisfy all of my use cases. Cheers, -Foam --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
