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

E4/Meeting Minutes/Status 20100311

Attendees

  • Boris Bokowski
  • Bogdan Gheorghe
  • Dan Rubel
  • Eric Moffatt
  • John Arthorne
  • McQ Wilson
  • Oleg Besedin
  • Paul Webster
  • Remy Suen
  • Simon Kaegi
  • Susan McCourt
  • Tom Schindl

Minutes

  • Checkpoint: are we on track to ship in July? Eric looking into summarizing current state of compatibility
    • Is there a very big value in moving release to September?
    • Should we consider shorter release cycle, i.e., 4.0.1 shortly after 4.0
  • Getting EclipseCon demo of CSS renderer ready
  • Eric reviewing current state of compatibility layer
    • Some blocking bugs
    • Slow performance
    • Most things are working
    • Overall looking pretty good
  • Changing internals of dependency injection
    • More consistent behavior and injection ordering
    • Fixing bugs in uninject, context reparenting
    • Looking at support for additional annotations for things like preferences
    • Extensibility for others to define injection-related annotations
  • Reworking the e4 key binding system
    • Make compatibility key bindings work
    • Couple of days away from having this working
  • Moved e4 debug work to JSDT, part of Helios release train
  • Looking at dependency injection performance problems
    • Some low hanging fruit in osgi context lookup strategy
  • Investigating setting up Eclipse SDK 4.0 build
  • Some recent model changes, improvements to model reconciler
  • Looking at changing UUIDs used in the model, getting help from EMF experts
  • Working on e4 rover client
    • Prototyped new e4 services such as preferences
  • Working on new sample applications
    • Need consistent identifiers to mark places where clients can contribute bits to the menus, so that they remain consistent over time
  • Should use model element ids, rather than xmi: model identifiers
  • Element ids are not globally unique so they need to be looked up contextually (same view in different windows has same id)
  • How to handle legacy perspectives that use geometric regions like "left, right, bottom", into e4 regions that have semantic naming (primary navigation, secondary navigation, etc)
  • Adapter service added
  • Visual design
    • Iterating visual design and appearance of search bar and other trim
  • Working on new workbench model tooling

Back to the top