Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

ATF/APIs

< ATF
Revision as of 23:02, 27 November 2006 by Goodmanr.us.ibm.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Proposed ATF APIs

Browser Tooling

  • An Extension point to add new views to the Browser Tooling. A based class will be provided that handles selections, listeners and changes to the view. Since all views of the Browser tools are updated for changes and selections done in any other view, the base class will make implementing this easier.
  • An Extension Point to add right click context menus to the DOM Inspector. A base class will be provided to support updating/retrieving DOM information.
  • An extension point to add filters to the Browser tooling views.
  • An extension point to add items to the Browser Tool bar.

Non-faceted projects

  • An Extension point for providing and API define, so that a personality can support projects that are not facet enabled. Today ATF special cases PHP project, since a PHP project doesn't support a facets. The intent is to generalized this support.

Personality Builder

  • Extensions points and APIs for declaring a new runtime. This will provide the information needed for ATF to populate it views and wizards.
  • Extension point for defining a runtime handler. This handler will processing complex Ajax Toolkit runtime layouts to the layout that is to be used by ATF.
  • Base classes to support implementing the above APIs/extension points.
  • Extension Points and XML definitions for creating the personality wizards and snippets.

Multi-browser support

  • APIs defined for the Browser Editor to that hides the differences between browsers and allows new browser to be plug in to the browser editor.
  • A DOM abstraction layer.
  • Abstract the source look-up resolution.

Back to the top