Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "E4/Meeting Minutes/Status 20090416"

(New page: == Agenda == == Attendees == == Minutes ==)
 
Line 1: Line 1:
 
== Agenda ==
 
== Agenda ==
 +
 +
* Status
  
 
== Attendees ==
 
== Attendees ==
 +
 +
* Boris Bokowski
 +
* Eric Moffatt
 +
* Doug Schaeffer
 +
* John Arthorne
 +
* Kevin McGuire
 +
* McQ
 +
* Oleg Besedin
 +
* Paul Webster
 +
* Simon Kaegi
 +
* Steve Northover
 +
  
 
== Minutes ==
 
== Minutes ==
 +
 +
* Writing new tests for e4
 +
* Need to identify subset of 3.x tests that we can run against the e4 compatibility layer to verify API conformance
 +
* Common approach to listener
 +
* Action sets, menu contributions, workbench action builder working in e4 compatibility layer
 +
** Working through actions/handlers that were reaching into internals
 +
* Removing references to org.eclipse.core.runtime
 +
* Create bundle for annotations so we can use injection throught e4 workbench
 +
* Working on different architecture for CSS styling with different styling classes per widget. Hopefully cleaner and easier to manage

Revision as of 11:23, 16 April 2009

Agenda

  • Status

Attendees

  • Boris Bokowski
  • Eric Moffatt
  • Doug Schaeffer
  • John Arthorne
  • Kevin McGuire
  • McQ
  • Oleg Besedin
  • Paul Webster
  • Simon Kaegi
  • Steve Northover


Minutes

  • Writing new tests for e4
  • Need to identify subset of 3.x tests that we can run against the e4 compatibility layer to verify API conformance
  • Common approach to listener
  • Action sets, menu contributions, workbench action builder working in e4 compatibility layer
    • Working through actions/handlers that were reaching into internals
  • Removing references to org.eclipse.core.runtime
  • Create bundle for annotations so we can use injection throught e4 workbench
  • Working on different architecture for CSS styling with different styling classes per widget. Hopefully cleaner and easier to manage

Back to the top