[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[ve-dev] Re: ve-dev Digest, Vol 31, Issue 12
|
Hi Cathy,
I'd love to see what you've done. It sounds like you already have a
pretty good feel for VE and your thinking parallels my own. I'd like to
see VE applied to a wider range of development than it currently
supports, though that will probably mean that it won't be tightly bound
to JEM anymore.
Over the past few months, I have basically finished (it's not done, but
it's usable in production) a code generation tool using EMF and M2T JET
(formerly JET2/EMFT JET) that generates code for 2 platforms from the
same source. Unfortunately, that tool is not open source, but I've been
looking at what it would take to apply M2T JET to VE. I can't really get
started on that until I get the regular builds restarted and we get a
handle on the bugs. However, it sounds like your work would tie in well
if you'd like to make it available. Any help you would like to provide
on both code and documentation would be much appreciated as well.
Thanks,
Steve Robenalt
ve-dev-request@xxxxxxxxxxx wrote:
Date: Fri, 21 Sep 2007 16:29:17 +0200
From: cathyscott@xxxxxxxxxx
Subject: [ve-dev] Re: Future of VE
To: ve-dev@xxxxxxxxxxx
Message-ID:
<20070921142917.PITG7338.viefep23-int.chello.at@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
I am interested in volunteering to help with VE. I have experience with GEF, EMF and in developing the CodeGen component of VE.
In fact I have recently finished a project that, if incorporated into the current VE would make it much easier for other plugin developers to extend VE for use with XML, C++ source code etc.
The original focus of my project involved analysing the CodeGen component of VE and the feasibility of extending this component so that it could parse Groovy source code.
Although the Eclipse VE homepage claims that it is a framework for visual editing for other languages in practice the current Codegen component is tightly bound to Java source code.
However VEs CodeGen component contains a great deal of code that can be reused for non-Java source. Hence I have redesigned this component to create a "Not Just Java Eclipse VE", that separates the Java specific code from the rest. This functions exactly as the current Eclipse VE, but with the Java specific CodeGen being a specific implementation of a CodeGen rather than an integral part of the VE itself. A new extension point defines a CodeGenFactory that defines the embedded source editor to be used, the ExpressionDecoderFactory, MethodGeneratorFactory etc. Each of these can then be specified for Java, Groovy, C++ etc.
It is not intended that this redesigned VE is an alternative to the existing Eclipse VE but rather that it demonstrates the possibilities for Eclipse VE to become a more general framework for building Visual Editors.
This redesigned VE was used as the basis for a Groovy VE. At present this Groovy VE only parses and generates a limited range of Groovy scripts that use the SwingBuilder class. However it can potentially be extended so that a wider range of Groovy scripts can be processed.
I am happy to send you a copy of the Not Just Java plugin so that you test it out, as well as the analysis and design paper.
I am also very happy to help with documentation for VE in general. I had to do a lot of delving into VE for this plugin and others and know my way around parts of it very well, particularly the Codegen.
Cathy Scott
