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

OAW developer telco 2008-01-07

oAW developer meeting 2008-01-07 20:00 CEST

Via Skype (host's skype name 'svenefftinge')

Attendees

Arno Haase

Bernd Kolb

Dieter Moroff

Markus Voelter

Peter Friese

Sven Efftinge

Karsten Thoms

Ueli Brawand

Agenda

  1. oAW 4.2.1 maintenance / oAW 5.0
  2. New Backend

Minutes

  1. oAW 4.2.1 maintenance / oAW 5.0
    • There will be no oAW 4.2.1 release. However, fixes and minor features can be developed within the 4.2 branch on our SF.net CVS
    • All Eclipse related stuff will be developed on the Eclipse CVS
    • All non-Eclipse related stuff will be stay on the SF.net CVS.
    • Thus, we will have a new module oaw_v5
    • Added value can be put into the oaw_integration module (e.g. oAW perspective, etc.)
    • The various modules will be developed and released separately
    • Each module will have a module owener. Sven will start a Wiki page with a list of modules and owners.
    • naming conventions: Projects (and thus CVS modules) will be named exactly like the plug-in they contain
  2. New Backend
    • Arno is working on a new backend, which will require some changes to the existing frontends
    • Question: when / how to perform those changes?
      • Peer review: Bernd and Sven (Arno sends code by email)
      • Affected frontends: languages, debugger, profiler (can be implemented afterwards), tracing (not yet available publicly)
    • Current status:
      • Process can be started using ANT - ready this week
    • Mode of operation:
      • Arno to finish work
      • Bernd and Sven to review work
      • detach debugger
      • check-in backend
      • attach languages
      • re-attach debugger
  3. different call syntax among Xtend / Xpand
    • Should be restructured, but how?
    • Fulfill the Java model?
    • Name Mangling = one flat namespace in backend, while in Xpand (where it is important), inject mangled names
    • Frontend: Xtend / Xpand call semantics stay the same
    • Backend: functions can be called by their fully qualified names. However, polymorphism will then be limited to functions with the same parameters
  1. Additional features
    • Polish for Xtext:
      • Enhanced Outline (Sorting / Labelling / Icons)
      • Builder to scan all Xtext files and construct an import index to facilitate importing in the editor
  2. Patrick
    • Paid by itemis, available full-time for oAW
    • As always, we want to see some work before granting committer rights
    • As usual, a voting will take place

Actions

  1. one
  2. two

Other Decisions

  1. one

Back to the top