|
| Re: best practice displaying EMF-elements in tables [message #1708273 is a reply to message #1708195] |
Tue, 15 September 2015 07:12  |
 Ed Merks
Messages: 30559
Registered: July 2009 |
Senior Member |
|
|
Patric,
For binding to Eclipse Viewers, notifications are processed by
org.eclipse.emf.edit.ui.provider.AdapterFactoryContentProvider.notifyChanged(Notification),
i.e., by the content provider that is used to provide content for the
views. It tries to update the Viewer with minimal effort depending the
type Viewer and what kind of updates it support efficiently...
On 14/09/2015 9:01 PM, Patric Bayer wrote:
> Hi,
>
> I came into a project which uses EMF for modeling and Vaadin for
> creating the UI. For displaying the data in tables the developers
> chose GlazedLists. Some of the columns are editable, a change in one
> of those fields leads to changes in other (non-editable) fields. The
> values are stored in an vector, which is basically just a List of
> Doubles.
> What I expected is this:
>
> When changing a value in the editable fields there starts a
> notification chain and all derived values refresh. I already managed
> to do that. My problem is, that they are not displayed in the table
> without having refreshRowCache called by any method (.setValue,
> .set(i,.get(i)) [like recommended in GlazeLists FAQ], ...). But using
> refreshRowCache makes everything quite slow and I am not sure if that
> is really necessary for only displaying some changed values (without
> adding/removing anything).
>
> So what I want to know is, what is Your best practice to display data
> from Your EMF-models in tables.
>
> Thanks in advance
>
> Patric
|
|
|
Powered by
FUDForum. Page generated in 0.01454 seconds
Search
Help
Register
Login
Home
