Firebug Roadmap

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
m (Changed status of "UI for using objects in Command Line")
m (Updated feature status)
(20 intermediate revisions not shown)
Line 6: Line 6:
== Version Numbering ==
== Version Numbering ==
-
The next planned version number is: '''1.12'''
+
The next planned version number is '''1.13'''.
Development happens on [https://github.com/firebug/firebug <code>master</code>] 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 ==
Line 17: Line 17:
! 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 || -
| 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 31: 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)
-
* 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]; reason: we already allow to copy HTML, OS conformity)
-
* Cut option in HTML panel ([http://code.google.com/p/fbug/issues/detail?id=6217 issue 6217])
+
* 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 40: Line 50:
=== Regular Tasks ===
=== Regular Tasks ===
-
* [http://code.google.com/p/fbug/issues/list?can=2&q=blocks%3A1.11 Firebug 1.11 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=blocks%3A1.12 Firebug 1.12 blockers]
Line 50: Line 59:
| [[#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
| [[#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
+
| [[#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
|-
|-
-
| [[#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 || <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
|-
|-
-
| [[#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 || <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
|-
|-
-
| [[#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
+
| [[#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
|-
|-
-
| [[#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
+
| [[#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
|-
|-
-
| [[#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
+
| [[#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
|-
|-
-
| [[#UI for using objects in Command Line|UI for using objects in Command Line]] || Simon || [http://code.google.com/p/fbug/issues/detail?id=6422 Issue 6422]: Add a right click option for accessing objects in the Command Line || style="background-color:#00B400; font-weight:bold; color:white;" | done
+
| [[#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:#00B400; font-weight:bold; color:white;" | done
|}
|}
Line 78: Line 87:
'''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]]
-
* [https://getfirebug.com/wiki/index.php/JSD2_Adoption JSD2 List of tasks]
+
* [[JSD2 Adoption|JSD2 list of tasks]]
'''Source Repository:'''
'''Source Repository:'''
Line 94: Line 103:
* Re-add context menu options
* Re-add context menu options
* Adjust CSS to match the Firebug UI
* 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 ====
==== Auto-completion for Command Editor ====
Line 110: Line 112:
* Enhance positioning of the Completion List Popup
* Enhance positioning of the Completion List Popup
-
==== Closure Inspector ====
+
==== Line numbers in CSS Edit Mode ====
-
Closure variables should be displayed inside the [[DOM Panel]] and be accesssible via the [[Command Line]].
+
The Source Edit Mode of the [[CSS Panel]] should have line numbers for easier navigation.
'''Tasks:'''
'''Tasks:'''
-
* Integrate FireClosure
+
* Integrate Orion into the Source Edit Mode
-
* Improve UI
+
* Ajust the display to fit to the Firebug UI
-
* Fix issues of FireClosure
+
-
'''Resources:'''
+
==== Folding for shorthand properties ====
-
* [https://github.com/simonlindholm/fireclosure FireClosure repository]
+
For shorthand CSS properties it should be possible to expand them to see the longhand properties that make them up.
-
 
+
-
==== Event types filter ====
+
-
The user should have the possibility to choose certain event types to be logged to the [[Console Panel]].
+
'''Tasks:'''
'''Tasks:'''
-
* Create menu items for the different event groups
+
* Save the longhand properties to every shorthand property
-
* Refactor setting the event types to work together with the ones set via <code>[[monitorEvents()]]</code>.
+
* Create a twisty and allow toggling the display of the longhand properties
 +
* Remove the ''Expand Shorthand Properties'' option
-
==== Line numbers in CSS Edit Mode ====
+
==== Sniff WebSocket traffic ====
-
The Source Edit Mode of the [[CSS Panel]] should have line numbers for easier navigation.
+
WebSocket requests should be displayed to the user.
'''Tasks:'''
'''Tasks:'''
-
* Integrate Orion into the Source Edit Mode
+
* Create new tab for WebSocket requests
-
* Ajust the display to fit to the Firebug UI
+
* Listen to WebSocket traffic
 +
* Dynamically output the WebSocket messages
-
== Resources ==
+
==== Display the return value and the exception thrown ====
-
* [https://getfirebug.com/wiki/index.php/Firebug_Roadmap_1.11 Firebug 1.11 Roadmap]
+
The value being returned or the exception being thrown should be displayed to the user.
-
==== UI for using objects in Command Line ====
+
'''Tasks:'''
-
There should be a context menu option for objects, functions, strings and numbers to use them within the [[Command Line]].
+
* 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:'''
'''Tasks:'''
-
* Add the context menu option
+
* Add the option to the options menu
-
* Deactivate the option and give a descriptive hint when the [[Console Panel]] is disabled
+
* Implement the functionality for displaying the authored values
 +
* Adjust the tooltip code to handle authored values
 +
 
 +
== Resources ==
 +
* [[Firebug 1.12 Roadmap]]
 +
 
 +
[[Category:Firebug]]
 +
[[Category:Firebug Development]]

Revision as of 21:02, 26 January 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 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)
  • 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)
  • Request auto-responder in the Net Panel (issue 6459; reason: makes much easier to debug response headers and JS files in a production environment).
  • Integrate EventBug into Firebug (issue 5440; reason: simplifies debugging of event listeners)
  • 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)
  • Edit Javascript on-the-fly in the Script panel (5083; reason: provide a powerful tool to test changes in the scripts)

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
started
Auto-completion for Command Editor Simon Issue 55: Auto-completion for Command Editor
issue 5741: Auto-completion within expression in Command Line
issue 6968: Improve UI of Command Editor auto-completion popup
started
Line numbers in CSS Edit Mode Farshid Issue 2153: Show line numbers in Edit mode done
Folding for shorthand properties Sebastian Issue 5523: Folding for shorthand properties not started
Sniff WebSocket traffic Florent Issue 6330: Sniff WebSocket traffic not started
Display the return value and the exception thrown Florent Issue 6855: Display the returned value or the exception thrown
Issue 6857: Give the ability to modify the returned value (blocked by platform bug 736733)
started
Display authored CSS color values Sebastian Issue 5507: Allow displaying original color values (blocked by platform bug 731271) done

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

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

Personal tools