[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [ve-dev] Re: [Design] Init string parsing
|
Title: Message
From
what I can see, this looks reasonable. I have to get into it further to
say more though. But thanks for posting the proposals. Even if I
don't understand all of it yet, it helps me come up to speed faster to hear you
guys talking using your usual vocabulary that you use to describe parts of the
VE.
Thanks,
Dave
To sum it up, the AST Rich is proposing is a small generic
portion the JDT AST tree and comes to model VE expressions. Besides the
fact that these expressions need to be searlized to XMI, they may also include
references to EMF objects (IJavaObjectInstance). These AST nodes
would be used by the target VM (or any other remoting mechanism) to evaluate
and instantiate of the real thing. The target environment may or may not
have the means to access JDT's AST.
------------
Dr. Gili Mendel
IBM
Software
Development
RTP Raleigh, NC
(919)543 6408, tie: 441
6408
Rich
Kulp/Raleigh/IBM@IBMUS Sent
by: ve-dev-admin@xxxxxxxxxxx
01/16/2004 06:17 PM
|
To
| ve-dev@xxxxxxxxxxx
|
cc
|
|
Subject
| RE: [ve-dev] Re:
[Design] Init string parsing |
|
Ed,
The reason we are doing this is because we need to
be able to run without AST. The default editor is the java visual editor,
which will have AST available, but the VE itself has something called JBCF
which allows editing java models that come out of an XMI file and not from
code. Because of that we need a representation that can be serialized through
EMF to an XMI file.
Thanks,
Rich