Firebug Roadmap

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
m (Added "needs update" hint)
Line 1: Line 1:
-
{{needsUpdate}}
 
-
 
* This page is intended to summarize plans and directions for Firebug.next
* This page is intended to summarize plans and directions for Firebug.next
 +
* Provide any feedback on Firebug [https://groups.google.com/forum/#!forum/firebug newsgroup]
-
* This summary should also help [http://groups.google.com/group/firebug-working-group FWG] to prioritize planned steps and features.
+
== Strategy ==
 +
This section describes goals and strategy that keeps Firebug a competitive in-browser tool and leader in space of in-browser developer tools.
-
* Provide any feedback on Firebug [https://groups.google.com/forum/#!forum/firebug newsgroup]
+
* Improve memory footprint & performance
 +
* Reuse built-in dev-tools API and components
 +
* Innovate features that only Firebug can deliver
 +
* Extension compatibility
 +
* Faster release cycle
 +
== Version Numbering ==
 +
The next planned version number is: '''1.11'''
-
== Status ==
+
Development happens on [http://getfirebug.com/releases/firebug/1.11/ Firebug 1.11] branch (currently alpha).
-
Current status of Firebug development.
+
-
=== Firebug 1.8 ===
+
If a significant new feature (or set of features) is introduced in new release the version numbering can move into 2.* scheme. An example of such feature can be support for remote debugging.
-
Development frozen on this branch.
+
-
=== Firebug 1.9 ===
+
== Schedule ==
-
[https://addons.mozilla.org/en-US/firefox/addon/firebug/ Firebug 1.9] is the last released version (available on AMO and getfirebug.com) compatible with Firefox 5-13. Selected patches will be back-ported from 1.10.
+
The goal is to introduce new Firebug release till the end of 2012
-
=== Firebug 1.10 ===
+
{| class="wikitable" style=""
-
Development happens on [http://getfirebug.com/releases/firebug/1.10/ Firebug 1.10] branch (currently alpha).
+
|-
 +
! style="width:200px" | Phase || style="width:200px" | Start Date
 +
|-
 +
| Alpha || Started
 +
|-
 +
| Beta || 10th of November
 +
|-
 +
| Final Release || 10th of December
 +
|}
 +
* The entire release cycle (from the first alpha to the final release) should target 4-5 months
 +
* The beta phase should be at least 4 weeks
 +
* The new release should introduce 8-10 new features (or significant bug fixes)
-
== Goals for Firebug.next ==
+
== Suggested Features ==
 +
Use this section to suggest any feature you'd like to see in Firebug.next.
-
* Improve memory footprint & performance
+
* JSD2 Adoption
-
* Reuse built-in dev-tools API and components
+
* Remote Debugging
-
* Innovate features that only Firebug can deliver
+
-
== Summary ==
+
== Planned Features ==
 +
This section summarizes all features that are planned for Firebug.next. Every feature in this section must have an owner.
-
See the following table that summarizes list of features and dev folks working on them.
+
Regular Tasks:
-
Append yourself as a developer to features you are interested in to participate.
+
* [http://code.google.com/p/fbug/issues/list?can=2&q=label%3Ablocks-1.10&colspec=ID+Type+Status+Owner+Test+Summary+Reporter&cells=tiles Firebug 1.10 blockers] (not fixed)
 +
* [http://code.google.com/p/fbug/issues/list?can=2&q=label%3Ablocks-1.11&colspec=ID+Type+Status+Owner+Test+Summary+Reporter&cells=tiles Firebug 1.11 blockers]
{| class="wikitable" style="width: 100%;"
{| class="wikitable" style="width: 100%;"
Line 36: Line 53:
! style="width:200px" | Feature || style="width:120px" | Developers || Related Issues || Status
! style="width:200px" | Feature || style="width:120px" | Developers || Related Issues || Status
|-  
|-  
-
| Delayed Firebug Load || Honza, Harutyun || [http://code.google.com/p/fbug/issues/detail?id=4989 Issue 4989]: Separate global UI (browser.xul) from Firebug UI (firebugFrame.xul) || style="background-color:#00B400; font-weight:bold; color:white;" | done
+
| Adopt JSD2 || Honza, Sebastian, Farshid || [http://code.google.com/p/fbug/issues/detail?id=5421 Issue 5421]: Adopt JSD2 || style="background-color:gold; font-weight:bold;" | started
-
|-
+
-
| Orion Text View || Honza || [http://code.google.com/p/fbug/issues/detail?id=5219 Issue 5219]: Use SourceEditor (Orion) for Command Editor<br/>[http://code.google.com/p/fbug/issues/detail?id=5175 Issue 5175]: Integrate Orion as replacement for the Script panel UI || style="background-color:gold;" | started
+
|-
|-
-
| Firecookie || Honza || [http://code.google.com/p/fbug/issues/detail?id=5422 Issue 5422]: Integrate Firecookie into Firebug || style="background-color:#00B400; font-weight:bold; color:white;" | done
+
| Group Console Messages || Sebastian || [http://code.google.com/p/fbug/issues/detail?id=4979 Issue 4979]: Group console messages || style="background-color:gold; font-weight:bold;" | started
|-
|-
-
| Remote HTTP Monitor || Honza || [http://code.google.com/p/fbug/issues/detail?id=5423 Issue 5423]: Integrate HTTP Monitor into Firebug || style="background-color:gold;" | started
+
| SPDY Support || Bharath || [http://code.google.com/p/fbug/issues/detail?id=5696 Issue 5696]: SPDY support in the Net panel || style="background-color:#00B400; font-weight:bold; color:white;" | done
 +
|-
 +
| Support for PerformanceTiming || Honza || [http://code.google.com/p/fbug/issues/detail?id=5843 Issue 5843]: Support for PerformanceTiming spec || style="background-color:lightgrey; font-weight:bold; color:black;" |  
|-
|-
-
| Restart-less Firebug Extensions || Honza || TODO || style="background-color:#00B400; font-weight:bold; color:white;" | done
 
-
|-
 
-
| JSD2 || Honza || [http://code.google.com/p/fbug/issues/detail?id=5421 Issue 5421]: Implement JSD2 || style="background-color:#C8C8C8;" | not started
 
-
|-
 
-
| Review Internal File Structure || Honza, Sebastian || [http://code.google.com/p/fbug/issues/detail?id=4960 Issue 4960]: Review internal file structure || style="background-color:gold;" | started
 
-
|-
 
-
| Style Tracing || Sebastian || [http://code.google.com/p/fbug/issues/detail?id=2916 Issue 2916]: Trace Styles Feature || style="background-color:#00B400; font-weight:bold; color:white;" | done
 
-
|-
 
-
| New Inspector || - || [http://code.google.com/p/fbug/issues/detail?id=4848 Issue 4848]: Create new SVG inspector || style="background-color:#C8C8C8;" | not started
 
-
|-
 
-
| Net Panel Improvements || - || [http://code.google.com/p/fbug/issues/detail?id=2617 Issue 2617]: Net panel header should be fixed on top instead of scrolling with the content || style="background-color:#C8C8C8;" | not started
 
-
|-
 
-
| HTML Entities || Sebastian || [http://code.google.com/p/fbug/issues/detail?id=3159 Issue 3159]: Show numeric character reference of MathML || style="background-color:#00B400; font-weight:bold; color:white;" | done
 
-
|-
 
-
| Breakpoint Improvements || - || [http://code.google.com/p/fbug/issues/detail?id=4378 Issue 4378]: Move editing of breakpoint conditions to Breakpoints Side Panel<br/>[http://code.google.com/p/fbug/issues/detail?id=2817 Issue 2817]: Hit counts for breakpoints || style="background-color:#C8C8C8;" | not started
 
-
|-
 
-
| Group Console Messages || Sebastian || [http://code.google.com/p/fbug/issues/detail?id=4979 Issue 4979]: Group console messages || style="background-color:gold;" | started
 
|}
|}
-
== New Features for 1.10 ==
+
* Feature planning should keep in mind the suggested release schedule above
-
This section lists of all suggested areas FWG should focus on in Firebug 1.10
+
-
Regular Tasks:
+
== Feature Description ==
-
* [http://code.google.com/p/fbug/issues/list?can=2&q=label%3Ablocks-1.10&colspec=ID+Type+Status+Owner+Test+Summary+Reporter&cells=tiles Firebug 1.10 blockers]
+
This section provides detailed description of all planned features.
-
* Memory leaks ([https://bugzilla.mozilla.org/show_bug.cgi?id=zombiehunter Zombie Hunter] is necessary)
+
-
** Fixing memory leaks is still the top Firebug priority.
+
-
=== Delayed Firebug Load ===
+
=== Adopt JSD2 ===
-
Firebug UI & Logic is mostly running inside an iframe (chrome://firebug/content/firebugFrame.xul). The goal here is to load the content of the iframe on demand at soon as the user needs Firebug the first time.
+
Firebug script debugger and all related features like BON (break on ...) should be based on new JSD2 API. Using JSD2 API will also enable remote debugging.
-
However there are some pieces that are running within the global Firefox UI (browser.xul) and must be loaded immediately after the browser window is loaded.
+
Part of this task is also internal Firebug architecture refactoring so it's ready for remote debugging features. Note that adopting JSD2 doesn't automatically mean that Firebug is remote-debugging-ready. This is covered by [http://code.google.com/p/fbug/issues/detail?id=5837 issue 5837]
-
* Page context menu (inspector, open with editor)
+
Note that this task doesn't have to make it into Firebug.next, but it could be possible (if useful) to at least merge code changes.
-
* Firebug global menu (tool, view, web developer, ...)
+
-
* Firebug start button (Firefox toolbar)
+
-
* Firebug iframe and a splitter
+
-
 
+
-
Firebug iframe content should be automatically loaded when the user presses F12 or uses any command available through an existing menu or a keyboard shortcut. Such functionality requires all global parts to be clearly separated and independent for the Firebug UI itself (the one running in the iframe).
+
-
 
+
-
Tasks:
+
-
* Separate ''Firebug UI'' from ''Global UI'' (create separate directory for global parts)
+
-
* Create a command dispatcher for global commands that loads Firebug if necessary.
+
-
* Initialize global UI independently of Firebug availability (e.g. translations)
+
-
* Adapt to the current
+
-
 
+
-
=== Orion Text View Integration ===
+
-
The Script panel content (JavaScript text view) should be based on Orion Text View. The goal here is to have syntax coloring and improved performance for huge scripts.
+
-
 
+
-
Tasks:
+
-
* Remove all code related to Script panel content generation (firebug/js/sourceBox module)
+
-
* Integrate Orion Text View
+
-
* Create a new Orion breakpoint ruler
+
-
* Support for tooltips displaying result of and evaluated expressions under the mouse (based on Orion Text Styler)
+
-
* Part of the integration is also using SourceEditor (Firefox 8+) for multiline console (command editor).
+
-
 
+
-
=== Firecookie Integration ===
+
-
[http://www.softwareishard.com/blog/firecookie/ Firecookie] is a an extension for Firebug that makes possible to view and manage cookies in your browser.
+
-
 
+
-
It was required many times to have such functionality included in Firebug by default.
+
-
 
+
-
Tasks:
+
-
* Firecookie code base doesn't support AMD
+
-
* The code should be divided into more (AMD) modules
+
-
* Support for backward compatibility can be removed
+
-
* Blocking [http://code.google.com/p/firecookie/issues/list issues] should be fixed
+
-
* Firecookie automated tests should be merged into Firebug test list
+
-
 
+
-
=== Remote HTTP Monitor ===
+
-
The Net panel should use [https://wiki.mozilla.org/Remote_Debugging_Protocol Remote Debugging Protocol] (RDP) to communicate with the server side that is performing HTTP monitoring. This should enabled remote HTTP monitoring e.g. for mobile devices.
+
-
 
+
-
The server side script should be using the following interfaces (to monitor HTTP):
+
-
* nsIActivityDistributor
+
-
* nsIActivityObserver
+
-
* nsIWebProgressListener (monitors the file:/// protocol)
+
-
* nsIObserver (monitors ''http-on-*'' events to catch also [http://www.softwareishard.com/blog/firebug/firebug-16-tracking-also-bfcache-reads/ BFCache] responses)
+
-
* nsITraceableChannel (intercepts response bodies)
+
Resources:
Resources:
-
* [http://getfirebug.com/wiki/index.php/Net_Panel_Architecture_Review Net Panel Architecture Review]
+
* [https://getfirebug.com/wiki/index.php/Firebug_1.7:_Mozilla_Backend Firebug 1.7 BTI]
-
* [http://getfirebug.com/wiki/index.php/Net_Panel_Remoting Net Panel Remoting]
+
* [https://getfirebug.com/wiki/index.php/Script_Panel_Refactoring Script Panel Refactoring]
-
* [http://getfirebug.com/wiki/index.php/HTTP_Monitor HTTP Monitor]
+
* [https://getfirebug.com/wiki/index.php/Remoting_Prototype Remoting Prototype]
 +
* [https://getfirebug.com/wiki/index.php/Remoting_Architecture Remoting Architecture]
-
Tasks:
+
Source Repository:
-
* Define new actors and extend the RDP protocol
+
* Development happens on [https://github.com/firebug/firebug/commits/jsd2 JSD2 branch]
-
* Clean separation of the client and server parts
+
-
* Communication between client and server based on JSON packets
+
-
* Optimization
+
-
 
+
-
=== Restart-less Firebug Extensions ===
+
-
There should be a way how to install Firebug and extensions without Firefox restart. Some API related to dynamic registration are already available.
+
-
 
+
-
Tasks:
+
-
* Review API for dynamic adding/removal of panels
+
-
* Review API for dynamic adding/removal of modules
+
-
* Review extension example
+
-
* Update documentation/tutorial
+
-
 
+
-
Resources:
+
-
* http://code.google.com/p/fbug/issues/detail?id=4686
+
-
* https://github.com/cadorn/jetpack-firebug
+
-
 
+
-
=== JSD2 ===
+
-
JSD2 (also known as JSDBG2 or JSDBGAPI) represents new API for JS debugging in Firefox.
+
-
 
+
-
Jim Blandy and Jason Orendorff are working on a JS implementation of JSD built on top of the JSDBG2 API (a wrapper). This wrapper should be injected into Firebug and make it compatible with JSDBG2. Prototype implementation [http://hg.mozilla.org/users/jblandy_mozilla.com/firebug-on-jsdbg2/ is available] (Firebug 1.9 fork).
+
-
 
+
-
Work on this goal depends on how much ready JSD2 is.
+
-
 
+
-
TBD
+
-
 
+
-
Resources:
+
-
* [http://getfirebug.com/wiki/index.php/Script_Panel_Remoting Script Panel Remoting]
+
-
* [https://wiki.mozilla.org/Debugger Debugger]
+
-
* [https://wiki.mozilla.org/DevTools/Features/Debugger DevTools Debugger]
+
-
* [https://wiki.mozilla.org/Remote_Debugging_Protocol Remote Debugging Protocol]
+
-
 
+
-
=== Review Internal File Structure ===
+
-
If parts break extensions, they will go into 2.0.
+
-
 
+
-
Tasks:
+
-
* Convert last few files into (AMD) modules
+
-
* Split huge files into more modules
+
-
* Suggest places/modules that needs refactoring (e.g. TabWatcher)
+
-
 
+
-
=== Style tracing ===
+
-
The [[CSS Panel]] should offer a different view on CSS properties to allow to find out how a specific value was generated.
+
-
 
+
-
Tasks:
+
-
* Investigate [http://dxr.mozilla.org/mozilla/mozilla-central/browser/devtools/styleinspector/CssLogic.jsm.html built-in CSS API]
+
-
* Create a new property-based view for the CSS panel using the built-in CSS API
+
-
** <span style="text-decoration: line-through;">Add option to the CSS panel to toggle between the current view and the property-based view</span> &rArr; reused the [[Computed Side Panel]] for this
+
-
** Add display of assigned properties, which can be expanded to see the trace
+
-
** Allow disabling of single styles in the trace and the complete style trace &rArr; put into [http://code.google.com/p/fbug/issues/detail?id=5527 issue 5527].
+
-
 
+
-
=== New Inspector ===
+
-
Firebug should reuse the existing built-in Inspector to avoid conflicts with the page styles.
+
-
 
+
-
Tasks:
+
-
* Investigate [http://dxr.mozilla.org/mozilla/mozilla-central/browser/devtools/styleinspector/StyleInspector.jsm.html built-in Inspector API]
+
-
* Investigate related [http://code.google.com/p/fbug/source/browse/branches/firebug1.10/content/firebug/html/inspector.js Firebug API]
+
-
* Replace Firebug Inspector
+
-
 
+
-
=== Net Panel Improvements ===
+
-
Proposed Net panel improvements
+
-
 
+
-
* Net panel header should not scroll.
+
-
 
+
-
=== HTML entities ===
+
-
The [[HTML Panel]] needs different options how entities are displayed.
+
-
 
+
-
There should be three display options inside the HTML panel's options menu:
+
-
* Show Entities as Symbols
+
-
* Show Entities as Names
+
-
* Show Entities as Unicode
+
-
 
+
-
Resources:
+
-
* [http://code.google.com/p/fbug/issues/detail?id=3159#c23 Undocumented API].
+
-
 
+
-
Tasks:
+
-
* Find out how the API is working exactly
+
-
* Implement new mapping function in <code>lib/string.js</code> including the API
+
-
* Implement the new options
+
-
 
+
-
=== Breakpoint Improvements ===
+
-
Several new features related to breakpoints should be introduced.
+
-
It should be possible to specify how many times a breakpoint should be hit before it breaks the script execution as well as to create and edit breakpoint conditions in the [[Breakpoints Side Panel]].
+
-
 
+
-
Tasks:
+
-
* Change the Breakpoints side panel to allow inline editing (required for the other tasks)
+
-
 
+
-
* Hit count for breakpoints
+
-
** Implement hit count into debugger
+
-
** Add hit count to Breakpoints side panel
+
-
 
+
-
* Move breakpoint condition editing to the Breakpoints side panel
+
-
** Add breakpoint condition to Breakpoints side panel
+
-
** Add context menu to Breakpoint Column containing option to edit the condition
+
=== Group Console Messages ===
=== Group Console Messages ===
Line 228: Line 90:
* Group error messages
* Group error messages
* Group messages produced by the 'console' object
* Group messages produced by the 'console' object
-
 
-
== Further Suggestions ==
 
-
Please append further suggestions for new 1.10 features in this section so. We'll yet discuss all these suggestions.
 
-
 
-
=== Better user feedback ===
 
-
This has been already discussed before. It could be useful to have more feedback from Firebug users and use it for targeted improvements. The feedback should be collected using Testpilot and its related infrustructure and/or through a Firebug extension.
 
-
 
-
Questions:
 
-
* What specific data should be collected?
 
-
* What kind of knowledge we can get from the collected data?
 
-
 
-
Resources:
 
-
* [http://code.google.com/p/fbug/issues/detail?id=2633 Issue 2633]: Instrumentation for Firebug aka "Help Improve Firebug"
 
-
* [http://code.google.com/p/fbug/source/browse/#svn%2Fextensions%2Fbugpilot BugPilot]
 
-
 
-
=== Mapping of URLs to file system paths ===
 
-
Firebug currently doesn't have any connection to the server files. Many people don't understand that and they are asking how to achieve that.
 
-
This change would at least allow mapping between local server URLs and the file system.
 
-
 
-
Questions:
 
-
* How is this related to Firediff?
 
-
 
-
Resources:
 
-
* [http://code.google.com/p/fbug/issues/detail?id=5035 issue 5035]
 
-
 
-
=== Integrate more extensions into Firebug ===
 
-
Apart from Firecookie integration, [http://code.google.com/p/fbug/issues/detail?id=5440 EventBug was asked to be integrated into Firebug].
 
-
Question was also if further extensions should be integrated:
 
-
* FireStarter: No, because it just enhances the current activation model.
 
-
* NetExport: No, export functionality probably won't be used that often.
 
-
* ConsoleExport: No, export functionality probably won't be used that often.
 
-
 
-
Instead [[Swarms]] should be pushed, so users will install the extensions they need.
 
-
 
-
=== Integrate more web dev tools APIs/Components ===
 
-
Firebug should share more APIs with the web dev tools team.
 
-
 
-
[https://hg.mozilla.org/mozilla-central/file/654ac86492e8/browser/devtools Available APIs]
 
-
 
-
Possible candidates:
 
-
* [https://hg.mozilla.org/mozilla-central/file/654ac86492e8/browser/devtools/webconsole Web Console APIs]
 
-
* [https://hg.mozilla.org/mozilla-central/file/654ac86492e8/browser/devtools/styleeditor Style Editor APIs]
 
-
* [https://hg.mozilla.org/mozilla-central/file/654ac86492e8/browser/devtools/debugger Debugger APIs]
 

Revision as of 08:05, 21 August 2012

  • This page is intended to summarize plans and directions for Firebug.next
  • Provide any feedback on Firebug newsgroup

Contents

Strategy

This section describes goals and strategy that keeps Firebug a competitive in-browser tool and leader in space of in-browser developer tools.

  • Improve memory footprint & performance
  • Reuse built-in dev-tools API and components
  • Innovate features that only Firebug can deliver
  • Extension compatibility
  • Faster release cycle

Version Numbering

The next planned version number is: 1.11

Development happens on Firebug 1.11 branch (currently alpha).

If a significant new feature (or set of features) is introduced in new release the version numbering can move into 2.* scheme. An example of such feature can be support for remote debugging.

Schedule

The goal is to introduce new Firebug release till the end of 2012

Phase Start Date
Alpha Started
Beta 10th of November
Final Release 10th of December
  • The entire release cycle (from the first alpha to the final release) should target 4-5 months
  • The beta phase should be at least 4 weeks
  • The new release should introduce 8-10 new features (or significant bug fixes)

Suggested Features

Use this section to suggest any feature you'd like to see in Firebug.next.

  • JSD2 Adoption
  • Remote Debugging

Planned Features

This section summarizes all features that are planned for Firebug.next. Every feature in this section must have an owner.

Regular Tasks:

Feature Developers Related Issues Status
Adopt JSD2 Honza, Sebastian, Farshid Issue 5421: Adopt JSD2 started
Group Console Messages Sebastian Issue 4979: Group console messages started
SPDY Support Bharath Issue 5696: SPDY support in the Net panel done
Support for PerformanceTiming Honza Issue 5843: Support for PerformanceTiming spec
  • Feature planning should keep in mind the suggested release schedule above

Feature Description

This section provides detailed description of all planned features.

Adopt JSD2

Firebug script debugger and all related features like BON (break on ...) should be based on new JSD2 API. Using JSD2 API will also enable remote debugging.

Part of this task is also internal Firebug architecture refactoring so it's ready for remote debugging features. Note that adopting JSD2 doesn't automatically mean that Firebug is remote-debugging-ready. This is covered by issue 5837

Note that this task doesn't have to make it into Firebug.next, but it could be possible (if useful) to at least merge code changes.

Resources:

Source Repository:

Group Console Messages

Console messages optionally need to be grouped to avoid spamming the Console Panel.

Tasks:

  • Group error messages
  • Group messages produced by the 'console' object
Personal tools