[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [eclipse-incubator-e4-dev] Agenda for the e4 Summit
|
How about writing plugins in C++? ;)
Cheers,
Doug.
-----Original Message-----
From: eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx
[mailto:eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx] On Behalf Of Boris
Bokowski
Sent: Friday, April 11, 2008 9:28 AM
To: E4 developer list
Subject: Re: [eclipse-incubator-e4-dev] Agenda for the e4 Summit
Kim, I am open to changes like this. How about we wait a little and then
talk about consolidating work areas next week? At this point, I would
rather see more work areas in the hope that this makes it easier to
define them clearly.
Tom, I split "Driving Eclipse from other languages" into "Make it easy
to script Eclipse (e.g., expose DOMs)" and "Support for plug-ins
implemented in other languages (JavaScript, JRuby, Groovy, ...)". Does
this help?
Boris
Kim Horne wrote:
> Boris,
> I'm not sure if you intended the work areas you mentioned to be hard
> lines for any potential break out session. If you did, I can't help
> but think the architecture item and the client/server split items are
> one and the same. Getting the listener model just right is probably
> the majority of the client/server work. Perhaps we could add the
> client/server problem under the architectural heading?
Tom Schindl wrote:
> Could we add a 3rd column where a short sub-project description is
> given. E.g. I'm not sure what the subproject "Driving Eclipse from
> other languages" means. Does it mean makeing the Workbench-Scripable
> using (JavaScript, Groovy, JRuby, ...)?
_______________________________________________
eclipse-incubator-e4-dev mailing list
eclipse-incubator-e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
