does a manual exist for the Firefox Webdeveloper toolbar?

Discussion in 'HTML & Website Design' started by driven, Aug 31, 2006.

  1. #1
    Maybe it's just me, but I find the FF Web Developer toolbar to have too many features. They are useful but if only I knew how to use it all. Is there such a thing as a documenation or manual to learn it?
     
    driven, Aug 31, 2006 IP
  2. Gordaen

    Gordaen Peon

    Messages:
    277
    Likes Received:
    12
    Best Answers:
    0
    Trophy Points:
    0
    #2
    http://chrispederick.com/work/webdeveloper/documentation/

    I don't know how much that will help, but that's the web dev toolbar's documentation site.

    A lot of it comes down to being familiar with webpages and then thinking, "I wish I could..." then you check and the toolbar can (usually) do it ;) For instance, if you want to view all the CSS a given page uses, click css, view css. All the validation stuff is under Tools, so you will probably use that a bit. To test different window sizes, you use resize (you can create your own sets too like 1024x768).

    Play around with it a bunch. If you have any specific questions, feel free to ask :)
     
    Gordaen, Sep 1, 2006 IP
  3. driven

    driven Well-Known Member

    Messages:
    400
    Likes Received:
    14
    Best Answers:
    0
    Trophy Points:
    138
    #3
    Yeah- I ran into that site a while back when I was searching for a document. Maybe it's just me, but isn't it stupid to not have a documenation manual that shows what all the buttons are for. Talk about the obvious...
     
    driven, Sep 1, 2006 IP
  4. Gordaen

    Gordaen Peon

    Messages:
    277
    Likes Received:
    12
    Best Answers:
    0
    Trophy Points:
    0
    #4
    I've noticed that a lot of the plug-ins don't have good documentation. Some of them even lack decent screenshots, which is a must for me to download something. A lot of times programmers don't realize how familiar they've become with a program while working on it, so they don't realize that the users can be overwhelmed.

    Part of it is that the intended audience is people who have significant web design experience. Probably another part of it is that the developer likes coding more than writing documentation (extremely common, that's one of many reasons wikis have become so popular). Of course, many plugins start out as the programmer developing something for his own benefit, so they get pretty far along with no documentation, because it wasn't intended to have a wide audience.

    Documentation would definitely help with a plug-in like this, because it has probably 100 things it can do.
     
    Gordaen, Sep 1, 2006 IP