Firebug 1.12 Roadmap

From FirebugWiki

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

[edit] Version Numbering

The next planned version number is: 1.12

Development happens on master branch (currently beta).

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.

[edit] Schedule

Phase Start Date
Alpha Started
Beta 2013-06-28
Final Release 2013-08
  • The entire release cycle (from the first alpha to the final release) should target 4-5 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.

  • JSD2 Adoption
  • Remote Debugging
  • Undo/redo option in HTML panel (+ CSS + DOM if possible) (issue 54, issue 2569)
  • Cut option in HTML panel (issue 6217)

[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
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
Group console messages Sebastian Issue 4979: Group console messages done
Auto-completion for Command Editor Simon Issue 55: Auto-completion for Command Editor
issue 5741: Auto-completion within expression in Command Line
not started
Closure Inspector Simon Issue 5873: Integrate FireClosure
Issue 6183: Closure Inspector: some variables are treated as DOM properties
Issue 6184: Closure Inspector: named function expression scopes are duplicated
Issue 6185: Closure Inspector: .% syntax doesn't work when execution is stopped in frame
done
Event types filter Sebastian, Honza Issue 229: Allow event types to be filtered with "Log Events" done
Line numbers in CSS Edit Mode Farshid Issue 2153: Show line numbers in Edit mode started
UI for using objects in Command Line Simon, Honza Issue 6422: Add a right click option for accessing objects in the Command Line
Issue 6430: Use in command line support for the Net and Cookies panel
done

Feature planning should keep in mind the suggested release schedule above

[edit] Feature Description

This section provides detailed description of all planned features.

[edit] 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

[edit] 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

[edit] 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 console object

[edit] 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

[edit] 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:

[edit] 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 monitorEvents().

[edit] 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

[edit] 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:

  • Add the context menu option
  • Deactivate the option and give a descriptive hint when the Console Panel is disabled

[edit] Resources

Personal tools