I don't understand what this does that can't already be done a hell of a lot better with the combo of firefox/firebug and the web developer toolbar? What is the value proposition here? Perhaps I'm missing something but it just looks like a CLI interface over the top of JavaScript (as opposed to the GUI/CLI approach with firebug - which is a far more scaleable approach). Is this thing going to need 1000 plugins instal…
New Firefox Command Line helps you develop faster
71–73 of 73 posts
Re: New Firefox Command Line helps you develop faster
#72Earlier quoted context omitted.
It works, doesn't it? If you have to interface with HTML or CSS directly and frequently while writing your application, then you want to make sure your HTML and CSS are super clean and maintainable. But, as PG has said before, HTML can be treated like object code! There was once a time when everyone had to write super clean and maintainable assembly code, but now you rely on a compiler. Ever look at compiler generate…
I find that a shortsighted attitude by PG. Web pages shouldn't be just a black box to present to the user. They should be structured documents that is flexible and malleable, so that the user or third parties can filter, adapt and enhance the content. http://userscripts.org/ is the best example of that, but there are many others.
Seems to be a non-problem...
Re: New Firefox Command Line helps you develop faster
#73And yet firebug is still the better console. Why do fancy things like tilt and this input box have priority over getting basic things like the console output under control? Just look at this example side by side and tell me which one you prefer: http://i.imgur.com/tKr87.png
I have a good reason for wanting this to land "earlyish" – to encourage the creation of more commands and full command access to the tools. If the command line is there and seeded with a few commands, people will start adding more (both for built-in tools and add-ons)