Firebug Roadmap

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
m (Added issue 6430 to UI for using objects in Command Line)
(Prepared roadmap for Firebug 3.0)
 
(26 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.12'''
+
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 feature can be support for 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 || Started
+
| 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.11 Firebug 1.11 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.12 Firebug 1.12 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
+
| colspan="4" style="text-align:center;" | TBD
-
|-
+
-
| [[#Group console messages|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
+
-
|-
+
-
| [[#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
+
-
|-
+
-
| [[#Closure Inspector|Closure Inspector]] || Simon || [http://code.google.com/p/fbug/issues/detail?id=5873 Issue 5873]: Integrate FireClosure<br/>[http://code.google.com/p/fbug/issues/detail?id=6183 Issue 6183]: Closure Inspector: some variables are treated as DOM properties<br/>[http://code.google.com/p/fbug/issues/detail?id=6184 Issue 6184]: Closure Inspector: named function expression scopes are duplicated<br/>[http://code.google.com/p/fbug/issues/detail?id=6185 Issue 6185]: Closure Inspector: .% syntax doesn't work when execution is stopped in frame || style="background-color:#00B400; font-weight:bold; color:white;" | done
+
-
|-
+
-
| [[#Event types filter|Event types filter]] || Sebastian, Honza || [http://code.google.com/p/fbug/issues/detail?id=229 Issue 229]: Allow event types to be filtered with "Log Events" || style="background-color:#00B400; font-weight:bold; color:white;" | done
+
-
|-
+
-
| [[#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:lightgrey; font-weight:bold; color:black;" | not started
+
-
|-
+
-
| [[#UI for using objects in Command Line|UI for using objects in Command Line]] || Simon, Honza || [http://code.google.com/p/fbug/issues/detail?id=6422 Issue 6422]: Add a right click option for accessing objects in the Command Line<br/>[http://code.google.com/p/fbug/issues/detail?id=6430 Issue 6430]: Use in command line support for the Net and Cookies panel || style="background-color:#00B400; font-weight:bold; color:white;" | done
+
|}
|}
Line 69: Line 47:
=== Feature Description ===
=== Feature Description ===
This section provides detailed description of all planned features.
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 [http://code.google.com/p/fbug/issues/detail?id=5837 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:'''
 
-
* [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]
 
-
* [https://getfirebug.com/wiki/index.php/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
 
-
 
-
==== 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
 
-
 
-
==== 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
 
-
 
-
==== Closure Inspector ====
 
-
Closure variables should be displayed inside the [[DOM Panel]] and be accesssible via the [[Command Line]].
 
-
 
-
'''Tasks:'''
 
-
* Integrate FireClosure
 
-
* Improve UI
 
-
* Fix issues of FireClosure
 
-
 
-
'''Resources:'''
 
-
* [https://github.com/simonlindholm/fireclosure FireClosure repository]
 
-
 
-
==== 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>.
 
-
 
-
==== 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 ==
== Resources ==
-
* [https://getfirebug.com/wiki/index.php/Firebug_Roadmap_1.11 Firebug 1.11 Roadmap]
+
* [[Firebug 2.0 Roadmap]]
-
 
+
-
==== UI for using objects in Command Line ====
+
-
There should be a context menu option for objects, functions, strings and numbers to use them within the [[Command Line]].
+
-
'''Tasks:'''
+
[[Category:Firebug]]
-
* Add the context menu option
+
[[Category:Firebug Development]]
-
* Deactivate the option and give a descriptive hint when the [[Console Panel]] is disabled
+

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