Firebug Roadmap

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
(Updated roadmap for 1.13 (not finished yet))
(Prepared roadmap for Firebug 3.0)
(23 intermediate revisions not shown)
Line 3: Line 3:
== Strategy ==
== Strategy ==
-
This section describes the strategy and goals that keep 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.
== Version Numbering ==
== Version Numbering ==
-
The next planned version number is '''1.13'''.
+
The next planned version number is '''3.0'''.
-
Development happens on [https://github.com/firebug/firebug <code>master</code>] 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 a feature can be support for JSD2 or even remote debugging.
+
== Schedule ==
== Schedule ==
Line 17: Line 15:
! style="width:200px" | Phase || style="width:200px" | Start Date
! style="width:200px" | Phase || style="width:200px" | Start Date
|-  
|-  
-
| Alpha || 2013-08-14
+
| Alpha || 2014-06-10
|-
|-
-
| Beta || -
+
| Beta || ?
|-
|-
-
| Final release || -
+
| 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 30: 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
 
-
* Undo/redo option in HTML panel (+ CSS + DOM if possible) ([http://code.google.com/p/fbug/issues/detail?id=54 issue 54], [http://code.google.com/p/fbug/issues/detail?id=2569 issue 2569])
 
-
* Cut option in HTML panel ([http://code.google.com/p/fbug/issues/detail?id=6217 issue 6217])
 
== Planned Features / Changes ==
== Planned Features / Changes ==
Line 40: Line 33:
=== Regular Tasks ===
=== Regular Tasks ===
-
* [http://code.google.com/p/fbug/issues/list?can=2&q=blocks%3A1.12 Firebug 1.12 blockers]
+
* [https://code.google.com/p/fbug/issues/list?can=2&q=blocks%3D2.0 Firebug 2.0 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|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
+
-
|-
+
-
| [[#Syntax highlighting for JavaScript|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/><span style="text-decoration:line-through;">[http://code.google.com/p/fbug/issues/detail?id=5175 Issue 5175]: Integrate Orion as replacement for the Script panel UI</span><br/>[http://code.google.com/p/fbug/issues/detail?id=5175 Issue 5353]: Integrate CodeMirror instead of Orion editor || style="background-color:gold; font-weight:bold;" | started
+
-
|-
+
-
| [[#Auto-completion for Command Editor|Auto-completion for 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
+
|-
|-
-
| [[#Line numbers in CSS Edit Mode|Line numbers in CSS Edit Mode]] || Farshid || [http://code.google.com/p/fbug/issues/detail?id=2153 Issue 2153]: Show line numbers in Edit mode || style="background-color:gold; font-weight:bold;" | started
+
| colspan="4" style="text-align:center;" | TBD
|}
|}
Line 61: Line 48:
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:'''
+
-
* [[Firebug 1.7: Mozilla Backend|Firebug 1.7 BTI]]
+
-
* [[Script Panel Refactoring]]
+
-
* [[Remoting Prototype]]
+
-
* [[Remoting Architecture]]
+
-
* [[JSD2 Adoption||JSD2 List of tasks]]
+
-
 
+
-
'''Source Repository:'''
+
-
Development happens on [https://github.com/firebug/firebug/commits/jsd2 JSD2 branch]
+
-
 
+
-
==== 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
+
-
 
+
-
==== 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
+
-
 
+
-
==== Line numbers in CSS Edit Mode ====
+
-
The Source Edit Mode of the [[CSS Panel]] should have line numbers for easier navigation.
+
-
 
+
-
'''Tasks:'''
+
-
* Integrate Orion into the Source Edit Mode
+
-
* Ajust the display to fit to the Firebug UI
+
-
 
+
-
== Resources ==
+
-
* [[Firebug 1.12 Roadmap]]
+

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

Strategy

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

Version Numbering

The next planned version number is 3.0.

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

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)

Suggested Features

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

Planned Features / Changes

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

Regular Tasks

Feature Overview

Feature Developers Related Issues Status
TBD

Feature planning should keep in mind the suggested release schedule above

Feature Description

This section provides detailed description of all planned features.

Resources

Personal tools