Firebug Roadmap

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
(Planned Features)
(Added display of pseudo-elements to suggestions and some reasons for the suggestions)
(30 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 that keep 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 ==
== Version Numbering ==
-
The next planned version number is: '''1.11'''
+
The next planned version number is '''1.13'''.
-
Development happens on [http://getfirebug.com/releases/firebug/1.11/ Firebug 1.11] branch (currently alpha).
+
Development happens on [https://github.com/firebug/firebug <code>master</code>] 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.
+
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 ==
-
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 || 2013-08-14
|-
|-
-
| 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 39: Line 31:
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 (reason: allows debugging on mobile devices; built-in dev tools already have this)
-
* 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]; reason: people should be able to easily undo mistakes; built-in dev tools already have this)
 +
* Cut option in HTML panel ([http://code.google.com/p/fbug/issues/detail?id=6217 issue 6217]; reason: we already allow to copy HTML, OS conformity)
 +
* Ignoring scripts while debugging (aka "black boxing", [http://code.google.com/p/fbug/issues/detail?id=4888 issue 4888]; reason: makes debugging easier; built-in dev tools already [https://bugzilla.mozilla.org/show_bug.cgi?id=875034 have this])
 +
* Script pretty printing ([http://code.google.com/p/fbug/issues/detail?id=1238 issue 1238]; reason: people want to be able to debug compressed JavaScript)
 +
* New inspector ([http://code.google.com/p/fbug/issues/detail?id=4848 issue 4848]; would fix a bunch of problems; built-in dev tools already use [https://bugzilla.mozilla.org/show_bug.cgi?id=724507 a better approach])
 +
* Folding for shorthand properties ([http://code.google.com/p/fbug/issues/detail?id=5523 issue 5523]; better UI)
 +
* Display of pseudo-elements inside [[HTML Panel]] ([http://code.google.com/p/fbug/issues/detail?id=5785 issue 5785]; reason: better UI and [http://code.google.com/p/fbug/issues/detail?id=6456 fixes issues]; built-in dev tools [https://bugzilla.mozilla.org/show_bug.cgi?id=694019 have this] now)
 +
* Linux theme ([http://code.google.com/p/fbug/issues/detail?id=471 issue 471]; reason: better integrated UI for Linux users)
-
== Planned Features ==
+
* New screencasts! ([http://code.google.com/p/fbug/issues/detail?id=4508 issue 4508]; reason: current screencasts are completely outdated, new features need to be described)
 +
* User statistics collector ([http://code.google.com/p/fbug/issues/detail?id=2633 2633]; reason: get info about Firebug usage to get a clue how to improve the UX)
 +
 
 +
== Planned Features / Changes ==
This section summarizes all features that are planned for Firebug.next. Every feature in this section must have an owner.
This section summarizes all features that are planned for Firebug.next. Every feature in this section must have an owner.
-
Regular Tasks:
+
=== Regular Tasks ===
-
* [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=blocks%3A1.12 Firebug 1.12 blockers]
-
* [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]
+
 +
=== 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:200px" | 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
+
| [[#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
|-
|-
-
| 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
+
| [[#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
|-
|-
-
| 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
+
| [[#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
-
|-
+
-
| 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;" | not started
+
-
|-
+
-
| &nbsp; ||  ||  ||  |
+
-
|-
+
-
| &nbsp; ||  ||  ||  |
+
-
|-
+
-
| &nbsp; ||  ||  ||  |
+
-
|-
+
-
| &nbsp; ||  ||  ||  |
+
-
|-
+
-
| &nbsp; ||  ||  ||  |
+
-
|-
+
-
| &nbsp; ||  ||  ||  |
+
-
|-
+
-
| &nbsp; ||  ||  ||  |
+
|-
|-
 +
| [[#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
|}
|}
-
* 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 ===
+
==== 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.
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.
Line 89: Line 76:
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.
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:
+
'''Resources:'''
-
* [https://getfirebug.com/wiki/index.php/Firebug_1.7:_Mozilla_Backend Firebug 1.7 BTI]
+
* [[Firebug 1.7: Mozilla Backend|Firebug 1.7 BTI]]
-
* [https://getfirebug.com/wiki/index.php/Script_Panel_Refactoring Script Panel Refactoring]
+
* [[Script Panel Refactoring]]
-
* [https://getfirebug.com/wiki/index.php/Remoting_Prototype Remoting Prototype]
+
* [[Remoting Prototype]]
-
* [https://getfirebug.com/wiki/index.php/Remoting_Architecture Remoting Architecture]
+
* [[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
-
Source Repository:
+
==== Line numbers in CSS Edit Mode ====
-
* Development happens on [https://github.com/firebug/firebug/commits/jsd2 JSD2 branch]
+
The Source Edit Mode of the [[CSS Panel]] should have line numbers for easier navigation.
-
=== Group Console Messages ===
+
'''Tasks:'''
-
Console messages optionally need to be grouped to avoid spamming the [[Console Panel]].
+
* Integrate Orion into the Source Edit Mode
 +
* Ajust the display to fit to the Firebug UI
-
Tasks:
+
== Resources ==
-
* Group error messages
+
* [[Firebug 1.12 Roadmap]]
-
* Group messages produced by the 'console' object
+

Revision as of 08:56, 5 September 2013

  • 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 that keep Firebug a competitive in-browser tool and leader in space of in-browser developer tools.

Version Numbering

The next planned version number is 1.13.

Development happens on master 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 a feature can be support for JSD2 or even remote debugging.

Schedule

Phase Start Date
Alpha 2013-08-14
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.

  • Remote Debugging (reason: allows debugging on mobile devices; built-in dev tools already have this)
  • Undo/redo option in HTML panel (+ CSS + DOM if possible) (issue 54, issue 2569; reason: people should be able to easily undo mistakes; built-in dev tools already have this)
  • Cut option in HTML panel (issue 6217; reason: we already allow to copy HTML, OS conformity)
  • Ignoring scripts while debugging (aka "black boxing", issue 4888; reason: makes debugging easier; built-in dev tools already have this)
  • Script pretty printing (issue 1238; reason: people want to be able to debug compressed JavaScript)
  • New inspector (issue 4848; would fix a bunch of problems; built-in dev tools already use a better approach)
  • Folding for shorthand properties (issue 5523; better UI)
  • Display of pseudo-elements inside HTML Panel (issue 5785; reason: better UI and fixes issues; built-in dev tools have this now)
  • Linux theme (issue 471; reason: better integrated UI for Linux users)
  • New screencasts! (issue 4508; reason: current screencasts are completely outdated, new features need to be described)
  • User statistics collector (2633; reason: get info about Firebug usage to get a clue how to improve the UX)

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
Adopt JSD2 Honza, Sebastian, Farshid Issue 5421: Adopt JSD2 started
Syntax highlighting for JavaScript Honza Issue 4823: Native javascript code color/highlight (without FireRainbow extension)
Issue 5175: Integrate Orion as replacement for the Script panel UI
Issue 5353: Integrate CodeMirror instead of Orion editor
started
Auto-completion for Command Editor Simon Issue 55: Auto-completion for Command Editor
issue 5741: Auto-completion within expression in Command Line
not started
Line numbers in CSS Edit Mode Farshid Issue 2153: Show line numbers in Edit mode started

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: Development happens on JSD2 branch

Syntax highlighting for JavaScript

The Script Panel should have syntax highlighting enabled for the displayed JavaScript code.

Tasks:

  • Replace SourceBox 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 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

Personal tools