[news.eclipse.technology.ldt] Re: Beyond textual represenations...

[Guillaume Pothier <gpothier@xxxxxxxxx>]

Sorry to reply to a post that is not adressed to me, but:

> 1) Model Specification

Lets you specify the model of your language

> 2) Persistence/Interchange

Well... I'd rather save my work ;o)

> 3) Notification

It seems that the current ASP API of JDT uses a notification mechanism. 
When you change the source code in the editor, the outile view, package 
view etc. gets updated.

> 4) Undo/Redo

This is also desirable.

> 5) Rich Metadata API

Can hold source code formatting info for instance.

> What aspects of these (or other things that I've missed) do you see as 
> particularly useful in the mainline case of the JDT/CDT/WTP supported 
> languages?
>
> And, what languages and/or features do you think would be easier to support 
> using EMF?

Reasoning on a model rather than on a representation of it (its source 
code) is easier.