I'm not a EMF Binding expert at all, but it seems like you should
listen for selection changes on the table and then bind the model to
the text fields (since they are used for editing several entities, I
guess that the binding can not be statically defined).
This said... profiles are complex objects. I'm not sure if simple text
fields will be enough for editing them.
For instance, you can configure plug-ins in a profile, so the whole
plug-in editing UI already used on another page should be availlable?
Maybe we need a more dinamic UI? Using a tree (or tree-table) for
showing the nested structure, vary much like the PDE editor for
extension points? Maybe pop-up windows for reusing components?
Just my 2cents.
On Wed, Nov 26, 2008 at 7:35 AM, Korina Cordero <kcordero@xxxxxxxxx
<mailto:kcordero@xxxxxxxxx>> wrote:
Hi,
I've been trying to get EMF Binding to work on the Profiles. What
I thought of was having the list of Profile IDs, in a table, in
one component and the user would select one Profile ID and then
the text fields and the other tabs would then load the data
related to that selected profile ID.
Any suggestions on how to do the binding? I've been trying out
things lately and I'm not having much success.
If there are better suggestions on how to display the Profiles
data in the POM Editor than what I have outlined above, I'd also
welcome it.
thanks,
Korina
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx <mailto:iam-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/iam-dev
--
Abel Muiño - http://ramblingabout.wordpress.com/
------------------------------------------------------------------------
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/iam-dev