ATF Road Map

As it was stated previously, ATF plans to stay in incubation phase. For the project to make headway more active participation and committers are needed from the community. See items below for additional possible future enhancements


Milestone 5 planned for February 2008

For The next milestone ATF is planning to support debugging of code has been source using JavaScript Eval and moving to a simpler XULRunner feature layout and plugins. The XULRunner plugins will contain a new build of XULRunner that will have some changes needed to meet eclipse IP concerns.


  1. "eval source" debugger support
  2. XULRunner
    • New Feature Structure
    • XULRunner changes to meet eclipse IP requirements
  3. Latest JSDT code
  4. WTP 2.0 based


Future Possible Enhancements

At this time ATF is planning future Milestones. Following is a list of possible future enhancements.

  1. Browser Tooling Enhancements
    • Browser Tools add save/restore for settings/options
    • Browser editor add save/restore for settings/options
    • Allow nodes to be moved inside the DOM Inspector
    • Word wrap for request body in XHR monitor
    • Option to clear cookies in the Browser Editor

  2. Debugger Enhancements
    • "eval source" debugger support
    • conditional breakpoint
    • hit count on breakpoints
    • Hover Evaluation
    • Function entry/exit breakpoints
    • Breakpoint line verification
    • Debug variables view
      • option to hide functions
      • option to filter out internal JavaScript properties
      • option to flatten or show 'logical structure' for JS objects
    • ScriptView
      • option to organized the displayed script elements

  3. I.E support
    • Write I.E debugger
    • Refactor ATF Code to support multiple browsers
    • Browser Tools
    • Support DOM Level 3 API for DOM inspector.
    • Move Mozilla DOM inspector to DOM Level 3 API.
    • Support adapter interfaces for specifying console/monitor
    • Support common code for debugger when possible
      • Not sure there is much code to share between an IE debugger and the Mozilla debugger. The existing eclipse debug APIs seen to be a good point to make the separation.
    • Generic Run/Debug launch code.
    • Extension point definitions
    • Resolve legal issues
      • No rights to ship the needed Microsoft dlls.
      • User required to install Microsoft® Windows® Script debugger
    • Resolve quality question
      • What we have heard is that the quality of the debug support for I.E is very poor.

  4. PHP support (This requires changes by the PHP IDE team)
    • Simple debugging from the Debugger to the PHP Debugger.
      • ATF JavaScript debugger changes
      • PHP Debug changes
      • Common Application launch code
    • Support for both Zend and xdebug debugger
    • Markup generation for lines numbers (This probably requires changes by the PHP engine on the server)
      • The PHP engine support generation of markup information to determination of line numbers of client side.
      • Client side/Server side markers
      • PHP Debugger changes
      • ATF JavaScript debugger changes.

  5. JavaScript Code Profiler
    • Provide/borrow UI for profiling, tie to Mozilla's jsdIScript profiling hooks
    • I.E. support

  6. ATF's Move out of Incubation Phase Task list
    • NLS
    • Determine internal/external classes. Rename packages.
    • Remove unneeded dependencies, General cleanup of code
    • Formalize APIs and Extension points
    • Resolve XULRunner build/maintenance issue for eclipse
    • Test plans and JUnit test.
    • Formalize build/test cycle
    • Conform to next release milestone release plan
    • Graduation Review/Requirements
    • Documentation
    • Review bug reports and determine which ones need to be fix for a release 1.
Incubation
Incubation
Project Links