On Tuesday, December 10, 2013 3:06:31 AM UTC+1, dmccunney wrote: > > On Mon, Dec 2, 2013 at 10:05 AM, Jan Honza Odvarko > <[email protected]<javascript:>> > wrote: > > On Monday, December 2, 2013 5:35:53 AM UTC+1, pd wrote: > > > >> My impression was that the DevTools people (of which there are > seemingly > >> many) were fully intending to develop the DevTools in an open manner in > that > >> Add-ons would be free to interact with them. > > > > That's correct. All API related to JSD2 (the new debugging engine) as > well > > as RDP (remote debugging protocol) are open and supposed to be used by > > extensions like Firebug. > > The impression that I've gotten is that browser makers are all > proceeding full speed ahead on improving and extending the toolset > available for development and debugging in the browser. In one sense, > that's good: it gives things like Firebug a base to build on and > extend. > Correct
> > On the other, it appears that these developments are increasingly > adding things people used to use Firebug to do, and in some cases > browser tools are competing with Firebug. How much of Firebug's code > is being made redundant because you can now do it in the browser > itself? How much does Firebug need to change to call browser > functions through an API instead of doing things itself? > Firebug has been always a Firefox extension and its primary purpose has been to extend Firefox, i.e. append features for web developers and designers. Since Firefox has currently also built-in developer features Firebug can focus on extending those. Some features might be duplicated and it mostly depends on whether Firebug offers something more over them (e.g. better UI, better integration with other features, better UX, ...). Otherwise Firebug can directly use/embed/integrate entire built-in components (e.g. the Inspector UI) (also depends on feedback from users). Further, there is whole bunch of features that are not available built-in (and probably won't be in foreseeable future) like, support for specific libraries (e.g. YUI, Dojo, ..), integration with specific server side technologies (NodeJS,..), features like Pixel perfect that are not for every one, etc. Firebug is also planning to extend the built-in UI, appending new actions directly into it so, users don't have to necessarily switch between two UIs. Honza > > > Honza > ______ > Dennis > https://plus.google.com/u/0/105128793974319004519 > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/cca2f517-cb9a-46cc-8934-2ccba1db191a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
