Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

E4/Meeting Minutes/Status 20080807


  • Boris Bokowski
  • Chris Aniszczyk
  • Dave Orme
  • Doug Schaefer
  • Ed Merks
  • Eric Moffat
  • John Arthorne
  • Kevin McGuire
  • Kim Horne
  • Martin Oberhuber
  • Steve Northover
  • Tom Schindl


  • Kevin
    • Investigation of CSS technologies (Batik, etc)
    • Looking at relationship of style sheets to modeled UI work
    • There will be a separate CSS technology roundup call (date to be determined on mailing list)
  • John
    • Not clear yet on Equinox relationship to e4. We may pursue various work in either 3.x stream or e4 depending on level of disruption.
    • There is some ongoing investigation of dependency injection technologies, specifically equinox declarative services (DS)
  • Kim
    • Investigation on how to evolve perspectives in e4
  • Steve
    • Getting EclipseCon prototype working again on GWT
    • Investigation of choosing a better Java class library for SWT to use
  • Eric
    • Looking at legacy code to see how it will work in modeled UI (Tom's EMF model)
  • Martin
    • Interest in many areas, still having discussions to decide where to participate
  • Ed
    • Interested in helping other people with their investigations
    • Willing to contribute to anything where modeling will help
  • Chris
    • DS tooling going into 3.5 M2
    • Planning to participate in tooling for self-hosting in e4 when that starts
  • Doug
    • Plan to have separate call to kick off resources work
  • Tom
    • Looking at changes made by Eric
  • Boris
    • Looking at using dependency injection in the modeled UI
    • Working on demo application as proof of concept
      • Non-IDE to demonstrate we're not just about tooling
      • Photo viewing, managing application
      • Could use e4 resource model

Discussion Topics

  • Team communication - how can we effectively communicate across the wider team?
    • Hope to organically evolve into small teams that communicate closely amongst themselves
    • Project is too big to have all discussions across all participants
    • Use status calls and mailing list to maintain awareness of what sub-teams are doing
    • Meeting minutes on wiki and posted on mailing list

Back to the top