I see in the legacy there is a Radio component available, but where as its missing in the new version of Granite, have only Radiogroup. ?
Legacy : RadioGroup — Granite UI 1.0 documentation
New Granite : Granite UI Foundation Server-side — Granite UI 1.0 documentation
Can any one suggest where is the radio component properties will be belonging to when am upgrading the components dialog to AEM 6.4 .?
i.e
--> " granite/ui/components/foundation/form/radiogroup " to "granite/ui/components/coral/foundation/form/radiogroup" and
--> "granite/ui/components/foundation/form/radio" to "There is no component available"
Also what will happens to the properties like below from old radiogroup will be belongs to when i upgrade.
Old dialog
<myoldradiogroup
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/form/radiogroup"
fieldLabel="Select myoldradiogroup Type"
name="./myoldradiogroup"
text="Select myoldradiogroup Type"
value="manage-radios">
<items jcr:primaryType="nt:unstructured">
<option1
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/form/radio"
cq-msm-lockable="radiostype"
renderReadOnly="{Boolean}true"
text="Manage radios"
checked = "{Boolean}true"
value="manage-radios"/>
<option2
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/form/radio"
cq-msm-lockable="radiostype"
renderReadOnly="{Boolean}true"
text="My Signup"
value="my-signup"/>
<option3
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/form/radio"
cq-msm-lockable="radiostype"
renderReadOnly="{Boolean}true"
text="My Settings"
value="my settings"/>
</items>
</myoldradiogroup>
New dialog
<mynewradiogroup
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/form/radiogroup"
fieldLabel="Select myoldradiogroup Type"
name="./myoldradiogroup"
text="Select myoldradiogroup Type"
value="manage-radios">
<items jcr:primaryType="nt:unstructured">
<option1
/>
<option2
/>
<option3
/>
</items>
</mynewradiogroup>
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
For Granite you don't need to specify resource type radio unlike Coral2. you can create options without using sling:resourceType but below properties are required.
RadioGroup — Granite UI 1.0 documentation
And to add cq-msm-lockable="radiostype"you need to add granite:data node as child node of option and need specify this property.
The value of the field.
Indicates if the field is in disabled state.
Indicates if the radio is checked when the form values don’t have a match by name
property.
e.g. Given a radiogroup with name
= name1
Form Values has named1 ? | Its value match? | checked | Checked? |
---|---|---|---|
true | true | n/a | true |
true | false | n/a | false |
false | n/a | true | true |
false | n/a | false | false |
The text of the radio.
Views
Replies
Total Likes
Hi,
For Granite you don't need to specify resource type radio unlike Coral2. you can create options without using sling:resourceType but below properties are required.
RadioGroup — Granite UI 1.0 documentation
And to add cq-msm-lockable="radiostype"you need to add granite:data node as child node of option and need specify this property.
The value of the field.
Indicates if the field is in disabled state.
Indicates if the radio is checked when the form values don’t have a match by name
property.
e.g. Given a radiogroup with name
= name1
Form Values has named1 ? | Its value match? | checked | Checked? |
---|---|---|---|
true | true | n/a | true |
true | false | n/a | false |
false | n/a | true | true |
false | n/a | false | false |
The text of the radio.
Views
Replies
Total Likes
Arun is correct - see the reference docs here -- RadioGroup — Granite UI 1.0 documentation
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies