Firebug Roadmap

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
m (Syntax highlighting is not completely done yet.)
(Prepared roadmap for Firebug 3.0)
 
(46 intermediate revisions not shown)
Line 3: Line 3:
== Strategy ==
== Strategy ==
-
This section describes goals and strategy that keeps Firebug a competitive in-browser tool and leader in space of in-browser developer tools.
+
This section describes the strategy and goals for the upcoming releases of Firebug.
-
 
+
-
* 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 ==
== Version Numbering ==
-
The next planned version number is: '''1.11'''
+
The next planned version number is '''3.0'''.
-
Development happens on [http://getfirebug.com/releases/firebug/1.11/ Firebug 1.11] branch (currently alpha).
+
Development happens on the <code>master</code> branch of the [https://github.com/firebug/firebug.next <code>firebug.next</code>] repository.
-
 
+
-
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 ==
== Schedule ==
-
The goal is to introduce new Firebug release till the end of 2012
 
-
 
{| class="wikitable" style=""
{| class="wikitable" style=""
|-  
|-  
! style="width:200px" | Phase || style="width:200px" | Start Date
! style="width:200px" | Phase || style="width:200px" | Start Date
|-  
|-  
-
| Alpha || Started
+
| Alpha || 2014-06-10
|-
|-
-
| Beta || 10th of November
+
| Beta || ?
|-
|-
-
| Final Release || 10th of December
+
| Final release || ?
|}
|}
-
* The entire release cycle (from the first alpha to the final release) should target 4-5 months
+
* The entire release cycle (from the first alpha to the final release) should target 6 months
* The beta phase should be at least 4 weeks
* The beta phase should be at least 4 weeks
* The new release should introduce 8-10 new features (or significant bug fixes)
* The new release should introduce 8-10 new features (or significant bug fixes)
Line 38: Line 28:
== Suggested Features ==
== Suggested Features ==
Use this section to suggest any feature you'd like to see in Firebug.next.
Use this section to suggest any feature you'd like to see in Firebug.next.
-
 
-
* JSD2 Adoption
 
-
* Remote Debugging
 
-
* Integrating FireClosure
 
== Planned Features / Changes ==
== Planned Features / Changes ==
Line 47: Line 33:
=== Regular Tasks ===
=== Regular Tasks ===
-
* [http://code.google.com/p/fbug/issues/list?can=2&q=blocks%3A1.10 Firebug 1.10 blockers] (not fixed)
+
* [https://code.google.com/p/fbug/issues/list?can=2&q=blocks%3D2.0 Firebug 2.0 blockers]
-
* [http://code.google.com/p/fbug/issues/list?can=2&q=blocks%3A1.11 Firebug 1.11 blockers]
+
=== Feature Overview ===
=== Feature Overview ===
{| class="wikitable" style="width: 100%;"
{| class="wikitable" style="width: 100%;"
|- bgcolor=lightgrey
|- bgcolor=lightgrey
-
! style="width:200px" | Feature || style="width:120px" | Developers || Related Issues || Status
+
! style="width:220px" | Feature || style="width:120px" | Developers || Related Issues || Status
-
|-
+
-
| 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
+
-
|-
+
-
| 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
+
-
|-
+
-
| 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 <code>PerformanceTiming</code> || 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;" | not started
+
-
|-
+
-
| Integrate SelectBug || Honza || [http://code.google.com/p/fbug/issues/detail?id=5931 Issue 5843]: Integrate SelectBug extension into Firebug || style="background-color:#00B400; font-weight:bold; color:white;" | done
+
-
|-
+
-
| Improve <code>$x()</code> || Sebastian || [http://code.google.com/p/fbug/issues/detail?id=18 Issue 18]: Beef up $x || style="background-color:#00B400; font-weight:bold; color:white;" | done
+
-
|-
+
-
| Auto-completion for [[Command Line|Command Editor]] || Simon || [http://code.google.com/p/fbug/issues/detail?id=55 Issue 55]: Auto-completion for Command Editor<br/>[http://code.google.com/p/fbug/issues/detail?id=5741 issue 5741]: Auto-completion within expression in Command Line || style="background-color:lightgrey; font-weight:bold; color:black;" | not started
+
-
|-
+
-
| Event types filter || Sebastian || [http://code.google.com/p/fbug/issues/detail?id=229 Issue 229]: Allow event types to be filtered with "Log Events" || style="background-color:gold; font-weight:bold;" | started
+
-
|-
+
-
| Syntax highlighting for JavaScript || Honza || [http://code.google.com/p/fbug/issues/detail?id=4823 Issue 4823]: Native javascript code color/highlight (without FireRainbow extension)<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; font-weight:bold;" | started
+
-
|-
+
-
| &nbsp; ||  ||  ||  |
+
|-
|-
 +
| colspan="4" style="text-align:center;" | TBD
|}
|}
-
* Feature planning should keep in mind the suggested release schedule above
+
Feature planning should keep in mind the suggested release schedule above
=== Feature Description ===
=== Feature Description ===
This section provides detailed description of all planned features.
This section provides detailed description of all planned features.
-
==== Adopt JSD2 ====
+
== Resources ==
-
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.
+
* [[Firebug 2.0 Roadmap]]
-
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]
+
[[Category:Firebug]]
-
 
+
[[Category:Firebug Development]]
-
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:'''
+
-
* [https://getfirebug.com/wiki/index.php/Firebug_1.7:_Mozilla_Backend Firebug 1.7 BTI]
+
-
* [https://getfirebug.com/wiki/index.php/Script_Panel_Refactoring Script Panel Refactoring]
+
-
* [https://getfirebug.com/wiki/index.php/Remoting_Prototype Remoting Prototype]
+
-
* [https://getfirebug.com/wiki/index.php/Remoting_Architecture Remoting Architecture]
+
-
 
+
-
'''Source Repository:'''
+
-
Development happens on [https://github.com/firebug/firebug/commits/jsd2 JSD2 branch]
+
-
 
+
-
==== SPDY Support ====
+
-
'''Tasks:'''
+
-
* Display use of SPDY protocol for requests inside [[Net Panel]]
+
-
 
+
-
==== 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 <code>console</code> object
+
-
 
+
-
==== Support for <code>PerformanceTiming</code> ====
+
-
Performance timing data accessible through <code>window.performance.timing</code> should be displayed.
+
-
 
+
-
'''Tasks:'''
+
-
* Decide where and how to display the data (probably inside [[Console Panel]])
+
-
* Create the graphical display
+
-
 
+
-
==== Integrate SelectBug ====
+
-
'''Tasks:'''
+
-
* Integrate SelectBug
+
-
* Fix any occurring errors
+
-
 
+
-
==== Improve <code>$x()</code> ====
+
-
The [[Command Line API]] <code>[[$x()]]</code> should cover all functionality of <code>[https://developer.mozilla.org/en-US/docs/DOM/document.evaluate document.evaluate()]</code>.
+
-
 
+
-
'''Tasks:'''
+
-
* Let <code>$x()</code> return arrays, strings, integers and booleans
+
-
* Add a parameter to specify the root element
+
-
* Add a parameter to specify the return type
+
-
 
+
-
==== Auto-completion for Command Editor ====
+
-
Add the [[Command Line]] auto-completion to the (multi-line) [[Command Line|Command Editor]] inside the [[Console Panel]].
+
-
 
+
-
'''Tasks:'''
+
-
* Allow auto-completion within an expression
+
-
* Add auto-completion to the Command Editor
+
-
* Enhance positioning of the Completion List Popup
+
-
 
+
-
==== Event types filter ====
+
-
The user should have the possibility to choose certain event types to be logged to the [[Console Panel]].
+
-
 
+
-
'''Tasks:'''
+
-
* Create menu items for the different event groups
+
-
* Refactor setting the event types to work together with the ones set via <code>[[monitorEvents()]]</code>.
+
-
 
+
-
==== Syntax highlighting for JavaScript ====
+
-
The [[Script Panel]] should have syntax highlighting enabled for the displayed JavaScript code.
+
-
 
+
-
'''Tasks:'''
+
-
* Replace <code>SourceBox</code> code by Orion
+
-
* Re-add context menu options
+
-
* Adjust CSS to match the Firebug UI
+
-
 
+
-
== Resources ==
+
-
* [https://getfirebug.com/wiki/index.php/Firebug_Roadmap_1.10 Firebug 1.10 Roadmap]
+

Latest revision as of 16:49, 11 June 2014

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

Contents

[edit] Strategy

This section describes the strategy and goals for the upcoming releases of Firebug.

[edit] Version Numbering

The next planned version number is 3.0.

Development happens on the master branch of the firebug.next repository.

[edit] Schedule

Phase Start Date
Alpha 2014-06-10
Beta  ?
Final release  ?
  • The entire release cycle (from the first alpha to the final release) should target 6 months
  • The beta phase should be at least 4 weeks
  • The new release should introduce 8-10 new features (or significant bug fixes)

[edit] Suggested Features

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

[edit] Planned Features / Changes

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

[edit] Regular Tasks

[edit] Feature Overview

Feature Developers Related Issues Status
TBD

Feature planning should keep in mind the suggested release schedule above

[edit] Feature Description

This section provides detailed description of all planned features.

[edit] Resources

Personal tools