Re: Combo box or DropDown for a dynamic set of inputs

Thanks both Dan and Stephen for helping me out. It certainly did help. Using a value type seems to be more applicable in my scenario since I do not want to make my code over complex with additional classes. But both methods are working perfectly. On 3/8/2016 12:02 PM, Dan Haywood wrote: ...

Re: Combo box or DropDown for a dynamic set of inputs

... but if you did want to follow Stephen's suggestion and use an object (rather than a value type), then that object can be annotated either with @DomainObject(bounded=true) ... for a simple drop-down or @DomainObject(autoCompleteRepository=..., autoCompleteAction=...) ... for an

Re: Combo box or DropDown for a dynamic set of inputs

There is a sample in the documentation [1] with a list of integers. Would work equally with strings. [1] http://isis.apache.org/guides/rgcms.html#_rgcms_methods_prefixes_choices On 8 March 2016 at 06:10, Stephen Cameron wrote: > yes, make the property of

Re: Combo box or DropDown for a dynamic set of inputs

yes, make the property of interest an object (not an enum) but hide the getter and setter of that property, then define a separate getter and setter that makes it appear as if that property is a string, you'll need a choiceXXX() for the setter to make it into a drop down, and maybe another action

Combo box or DropDown for a dynamic set of inputs

Hi all, I have used enumerated classes for drop down inputs in isis. The issue I have is I need the input data sets to be dynamic. More precisely I need the inputs to be generated at the run time, not the compile time. Using enumerated classes restricts me to the compile time which make me