But that is 1.) confusing 2.) causes extra work There should be an "off for all pages" rule, which would not allow exceptions, thus you could switch FB off even for the site(s) you are testing. No exceptions would be allowed. The rule "off for all pages, except" would be the current "off for all pages" rule. Thus when I add new pages, etc to my site, I could set the "off for all pages" rule until I need FB to debug the javascript, when I would switch to the "off for all pages except" rule, which specifies my exception(s). It is questionable, whether the "on for all pages" rule is legally allowed. My code is my intelectual property protected by national and international copyright laws. I might even sue anyone stealing my code for his site. Thus FB should prevent intelectual theft, not encourage it. I read a number of posts from people who state, that they use FB for reverse engineering. These request should not be complied with. I would go even further to prevent such misdemanour: there should be a kind of "password" protection that would allow only the owner(s) to run FB on their site. When entering an exception, a password should be entered (cookie?) which would be sent to a "Firebug" module at the website. This would be a PHP module slightly modified by the user using a small standalone program and then stored on the server. This standalone program would ask for the new name of the module, the passport and for a choice of passport encryption/security routines. FB could be activated for a site only when: 1.) the named security-module exists at the site 2.) the the password is correct, in which case an "Allow" reply would be sent. This would depend on the selected security routine.
Of course you could argue: 1.) it is not your job to prevent theft of code: As you provide means for this theft, the courts may not accept this argument 2.) if someone really wants it, he can find ways to get around this security feature. If someone is able to do that, than he is able to develop the code for his page himself, does not need to steal the code. If he than puts his solution on the internet, HE is commiting a crime, and all those, who use it to steal code. 3.) Stupid/lazy people do not program their sites themself, but use such programs that provide code off the shelf, ignoring the fact, that these, being jacks of all trade, mean a huge overhead for each page. Most of these programs cost a lot of money and buying pirated code would be cheaper. On Jul 4, 4:57 pm, johnjbarton <[email protected]> wrote: > The option "Off for all pages, except" is already implemented. Here > is how you use it: > > First, please note that you do not need to select any option to cause > "off for all pages", because Firebug is off by default. So the only > part you need to concentrate on is "except". > > To create an exception to the "off for all pages" rule, do the > following: > 1) open the site you want to debug > 2) press the firebug status bar icon. > Firebug will open and put that site on the white list. From now on > that page will be "except". > > jjb > > On Jul 4, 4:50 am, Rako <[email protected]> wrote: > > > Having read this discussion, I think there should be two options: > > "On for all pages, except" > > "Off for all pages, except" > > This would be easy to understand. For both there would be an > > exceptions-list, or a number of alternative lists. > > Thus you could have alternative selection of sites or pages within the > > sites and choose the selection you currently want. > > To implement these, a small off-line settings program could be > > written: > > The user can create the selections before beginning with the on-line > > tests. During the tests he could merely choose between the selections. > > Under Windows, these can easily be stored in the registry. If you > > want, I can let you have some "Read/save Combo-box contents" functions > > (VB6+API) or a small stand-alone program to create such selections. > > > On Jul 2, 5:49 pm, johnjbarton <[email protected]> wrote: > > > > On Jul 2, 8:20 am, jjj <[email protected]> wrote: > > > > > Then tell me why turning 'on for all pages' causes firebug to fail to > > > > turn on while browsing in firefox? > > > > I don't know why this does not work for you. It works for me. > > > > > Can you confirm that by turning 'on for all pages', firebug stays on > > > > for every single page until you explicitly turn it off? > > > > I can confirm that Firebug will stay on for me if I select "on for all > > > pages" then visit a set of completely different sites. > > > > Here is are the specifics: > > > 1) Open Firefox 3.5 with Firebug 1.5a7. > > > 2) Right click Firebug Icon, select On for all Web Pages. > > > 3) Openwww.google.comfirebugisup > > > 4) search for "foo" and click on the first > > > result,http://en.wikipedia.org/wiki/Foo; > > > Firebug is up. > > > 5) typehttp://www.ibm.comintothelocation bar, hit enter. Firebug > > > is up > > > > Does this work for you? > > > > Based on my tests and the fact that other users have used this option > > > successfully, it's my guess that the reason it fails for you is > > > related to some property of your environment. A simple and effective > > > test for this is create a new Firefox profile, install Firebug, and > > > restart. > > > > jjb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
