Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [eclipse-incubator-e4-dev] Meeting notes from today'sE4/Connectivity Frameworks discussion

Thanks Brian for setting this up.
I guess the next question is, where do we go from here?
  • Are there any interested parties that would want to make additional demos of their stuff?
  • What should be the goals of unification: common UI across the board? An EMF model of connection properties? Common persistence? We'll need to think about backward compatibilitity layers when it comes to products adopting any new framework.
  • McQ raised the concern that a single UI for all kinds of connections is not necessarily desirable. Re-using common widgets may be desireable, though.
I'd propose the next step to be starting a Wiki page with Requirements for a new E4 connection framework - requirements, constraints and possible use-cases perhaps.
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member

From: eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx [mailto:eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx] On Behalf Of brian.fitzpatrick@xxxxxxxxxx
Sent: Thursday, September 11, 2008 8:32 PM
To: E4 developer list
Subject: [eclipse-incubator-e4-dev] Meeting notes from today'sE4/Connectivity Frameworks discussion

Hi all,

Just wanted to let you know I've posted some (very rough) notes on the Wiki about today's discussion about E4 and Connectivity Frameworks here on the wiki:

I want to thank everybody who attended. I thought it was a great exchange of ideas and highlighted a number of common areas to focus on.

A special thanks to Martin O & Scott Lewis for presenting their bits on RSE & ECF.

Please feel free to edit the notes if I forgot something or was just incorrect about something.

I hope this is just the first of these discussions!


Brian Fitzpatrick
Eclipse Data Tools Platform PMC Chair
Eclipse Data Tools Platform Connectivity Team Lead
Staff Software Engineer, Sybase, Inc.

Back to the top