Firebug Roadmap

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
m (Removed release dates)
(Prepared roadmap for Firebug 3.0)
(7 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 || ?
|}
|}
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.
-
 
-
* 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) ([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])
 
-
* 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)
 
-
* Request auto-responder in the [[Net Panel]] ([http://code.google.com/p/fbug/issues/detail?id=6459 issue 6459]; reason: makes much easier to debug response headers and JS files in a production environment).
 
-
* Integrate EventBug into Firebug ([http://code.google.com/p/fbug/issues/detail?id=5440 issue 5440]; reason: simplifies debugging of event listeners)
 
-
 
-
* 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)
 
-
* Edit Javascript on-the-fly in the Script panel ([http://code.google.com/p/fbug/issues/detail?id=5083 5083]; reason: provide a powerful tool to test changes in the scripts)
 
== Planned Features / Changes ==
== Planned Features / Changes ==
Line 50: 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 || <strike>[http://code.google.com/p/fbug/issues/detail?id=4823 Issue 4823]: Native javascript code color/highlight (without FireRainbow extension)</strike><br/><strike>[http://code.google.com/p/fbug/issues/detail?id=5175 Issue 5175]: Integrate Orion as replacement for the Script panel UI</strike><br/>[http://code.google.com/p/fbug/issues/detail?id=5353 Issue 5353]: Integrate CodeMirror || style="background-color:gold; font-weight:bold;" | started
+
-
|-
+
-
| [[#Auto-completion for Command Editor|Auto-completion for Command Editor]] || Simon || <strike>[http://code.google.com/p/fbug/issues/detail?id=55 Issue 55]: Auto-completion for Command Editor</strike><br/>[http://code.google.com/p/fbug/issues/detail?id=5741 issue 5741]: Auto-completion within expression in Command Line<br/>[http://code.google.com/p/fbug/issues/detail?id=6968 issue 6968]: Improve UI of Command Editor auto-completion popup || style="background-color:gold; font-weight:bold;" | started
+
-
|-
+
-
| [[#Line numbers in CSS Edit Mode|Line numbers in CSS Edit Mode]] || Farshid || <strike>[http://code.google.com/p/fbug/issues/detail?id=2153 Issue 2153]: Show line numbers in Edit mode</strike> || style="background-color:#00B400; font-weight:bold; color:white;" | done
+
-
|-
+
-
| [[#Folding for shorthand properties|Folding for shorthand properties]] || Sebastian || [http://code.google.com/p/fbug/issues/detail?id=5523 Issue 5523]: Folding for shorthand properties || style="background-color:lightgrey; font-weight:bold; color:black;" | not started
+
-
|-
+
-
| [[#Sniff WebSocket traffic|Sniff WebSocket traffic]] || Florent || [http://code.google.com/p/fbug/issues/detail?id=6330 Issue 6330]: Sniff WebSocket traffic || style="background-color:lightgrey; font-weight:bold; color:black;" | not started
+
-
|-
+
-
| [[#Display the return value and the exception thrown|Display the return value and the exception thrown]] || Florent || <strike>[http://code.google.com/p/fbug/issues/detail?id=6855 Issue 6855]:  Display the returned value or the exception thrown </strike><br />[http://code.google.com/p/fbug/issues/detail?id=6857 Issue 6857]:  Give the ability to modify the returned value (blocked by platform [https://bugzilla.mozilla.org/show_bug.cgi?id=736733 bug 736733]) || style="background-color:gold; font-weight:bold;" | started
+
|-
|-
-
| [[#Display authored CSS color values|Display authored CSS color values]] || Sebastian || [http://code.google.com/p/fbug/issues/detail?id=5507 Issue 5507]: Allow displaying original color values (blocked by platform [https://bugzilla.mozilla.org/show_bug.cgi?id=731271 bug 731271]) || style="background-color:gold; font-weight:bold;" | started
+
| colspan="4" style="text-align:center;" | TBD
|}
|}
Line 78: 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:'''
 
-
* [[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
 
-
 
-
==== Folding for shorthand properties ====
 
-
For shorthand CSS properties it should be possible to expand them to see the longhand properties that make them up.
 
-
 
-
'''Tasks:'''
 
-
* Save the longhand properties to every shorthand property
 
-
* Create a twisty and allow toggling the display of the longhand properties
 
-
* Remove the ''Expand Shorthand Properties'' option
 
-
 
-
==== Sniff WebSocket traffic ====
 
-
WebSocket requests should be displayed to the user.
 
-
 
-
'''Tasks:'''
 
-
* Create new tab for WebSocket requests
 
-
* Listen to WebSocket traffic
 
-
* Dynamically output the WebSocket messages
 
-
 
-
==== Display the return value and the exception thrown ====
 
-
The value being returned or the exception being thrown should be displayed to the user.
 
-
 
-
'''Tasks:'''
 
-
* Display a special "scope" row in the watch panel with these values
 
-
* Change the background color for this row
 
-
* Give the ability to edit the return value (future plan)
 
-
* Prevent the user from editing the exception thrown or the return value (for now)
 
-
 
-
==== Display authored CSS color values ====
 
-
There should be an option allowing the user to display the CSS color values as they were defined.
 
-
 
-
'''Tasks:'''
 
-
* Add the option to the options menu
 
-
* Implement the functionality for displaying the authored values
 
-
* Adjust the tooltip code to handle authored values
 
== Resources ==
== Resources ==
-
* [[Firebug 1.12 Roadmap]]
+
* [[Firebug 2.0 Roadmap]]
[[Category:Firebug]]
[[Category:Firebug]]
[[Category:Firebug Development]]
[[Category:Firebug Development]]

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