|
| Re: [EEF] Widgets not using property descriptors? [message #622406 is a reply to message #622320] |
Tue, 30 March 2010 17:11   |
 Miles Parker
Messages: 1341
Registered: July 2009 |
Senior Member |
|
|
Hi guys, I'm bumping this with perhaps a more helpful concrete example. In EMF, you can provide custom logic for the values that can be used as input for a feature within a given eObject. For example, if I have a "Evaluate" object representing a mathematical evaluation where I can specify a function and inputs, and then I select a function that only accepts Integer value inputs, then for the input values I would only want to show integer values in the choices for input. This is all managed by the:
[code]
class EvaluateItemProvider
...
public List<IItemPropertyDescriptor> getPropertyDescriptors(Object object) {[/quote]
and associated:
[code] protected void add[Input]PropertyDescriptor(Object object) {[/quote]
methods.
But EEF ignores those and just uses the whole set of inputs for the entire model instance. It seems like those should be populated from the property descriptors instead of from the entire object tree. (Would be more efficient as well.)
Miles Parker wrote on Mon, 15 March 2010 18:49
> Hi,
>
> It seems that none of the generated controls in the EEF forms use the EMF Item Providers to get a set of appropriate input, but instead get all objects in the resource set that match that feature? If this is correct, do you have plans to implement such support in the near future?
>
> thanks,
>
> Miles
|
|
|
| Re: [EEF] Widgets not using property descriptors? [message #622409 is a reply to message #622406] |
Wed, 31 March 2010 07:37 |
Goulwen Le Fur
Messages: 125
Registered: July 2009 |
Senior Member |
|
|
Hi miles, sorry for the lag, I was at Econ ;)
You're right xwe don't use EMF.edit facilities (and logic) to populate
our widget. We plan to fix this to the next releases.
Regards,
--
Goulwen
Miles Parker a écrit :
>
>
> Hi guys, I'm bumping this with perhaps a more helpful concrete example.
> In EMF, you can provide custom logic for the values that can be used as
> input for a feature within a given eObject. For example, if I have a
> "Evaluate" object representing a mathematical evaluation where I can
> specify a function and inputs, and then I select a function that only
> accepts Integer value inputs, then for the input values I would only
> want to show integer values in the choices for input. This is all
> managed by the:
>
> [code]
> class EvaluateItemProvider
> ..
> public List<IItemPropertyDescriptor> getPropertyDescriptors(Object
> object) {[/quote]
>
> and associated:
>
> [code] protected void add[Input]PropertyDescriptor(Object object)
> {[/quote]
>
> methods.
>
> But EEF ignores those and just uses the whole set of inputs for the
> entire model instance. It seems like those should be populated from the
> property descriptors instead of from the entire object tree. (Would be
> more efficient as well.)
>
> Miles Parker wrote on Mon, 15 March 2010 18:49
>> Hi,
>>
>> It seems that none of the generated controls in the EEF forms use the
>> EMF Item Providers to get a set of appropriate input, but instead get
>> all objects in the resource set that match that feature? If this is
>> correct, do you have plans to implement such support in the near future?
>>
>> thanks,
>>
>> Miles
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.02295 seconds
] 
Search
Help
Register
Login
Home
