|
Re: [EEF] PropertiesEditingSemanticLister usage of setTarget [message #827651 is a reply to message #799301] |
Fri, 23 March 2012 16:00 |
Stephane Bouchet Messages: 280 Registered: July 2009 |
Senior Member |
|
|
Hi Mauricio,
I think your solution should work, but in case of managing EReference,
you should load all the model tree in order to propose all the available
object in the UI.
Le 15/02/2012 19:12, Mauricio Reyes a écrit :
> Hi, I'm using EEF in a Client-Server architecture where the client
> receives the unloaded ELists of an object (its eContents) when, for
> example, is going to be displayed in the EMF Editor Tree. When I added
> EEF to my app I founded that everytime I click on the root object, EEF
> triggers a search of all the Children up to the leaves through the use
> of EContentAdapter.setTarget(...) in the
> StandardPropertiesEditionComponent anonymous class
> PropertiesEditingSemanticLister.
>
> That makes my app extremely slow, as I can't show the properties of the
> root object without going over all the model objects (the same happens
> when using a local XML file, but has a good resolution time). The
> solution I'm trying is overriding setTarget and doing nothing there, so
> only the root eContents() are loaded from the server. That works ok as I
> can see the properties of the root object or any node without loading
> every single node until the leaves, just its eContents.
>
> My question is if that behavior is done for something in particular that
> I'm missing and my change can break the way EEF should work.
>
> Thanks in advance
> Mauricio
--
Cheers,
Stéphane Bouchet, OBEO
|
|
|
Powered by
FUDForum. Page generated in 0.03064 seconds