[news.eclipse.tools.emf] emfforms incubator: When should an editor be an

["John J. Franey" <jjfraney@xxxxxxxxx>]

Not sure if this is the right news group for this question related to 
emf, emf validation, editors and PDE's incubation project: emfforms.  Its 
a start.

I'm still new to emf and pde development.  Really liking it though.


emfforms provides an editor that implements and registers as an 
IResourceChangeListener.  Its resourceChanged handler flushes the command 
stack.



Updating markers fire a resourceChange event, AFAICT after a painful 
debugging session this morning.

Can any emf-validation expert confirm?



This combination has this unfortunate side effect: validation of the 
model wipes out unsaved changes.  This is not a nice, I think.  
Validation should run against unsaved changes and regardless of the 
outcome leave them intact.


I checked two editors that came from the emf project: the editor that emf 
generated from my model, and the editor in the Library example.  Neither 
of these are IResourceChangeListeners.  So, I'm left to wonder what is 
behind the design decision for emfform's editor to be an 
IResourceChangeListener.

Anyway, I'm going to change emfform's editor so it is not a 
ResourceChangedListener, and see if I get a better user experience.  I 
will feed back to the emfform's originator (b. cabe, somehow, I guess 
maybe a bugzilla).


By the way, I tried to use emfform's builder example.  I could not get it 
to work.  Instead, I'm using the emf validation's library example.  This 
approach lets me implement and test a validation plugin in isolation from 
a builder.  Later, after I learn more, I'll build a builder plugin based 
on the example from emfforms.

Regards,
John