Touch UI dialog fields - Side by Side ? | Community
Skip to main content
U
user00725
Level 4
September 5, 2016

Touch UI dialog fields - Side by Side ?

  • September 5, 2016
  • 1 reply
  • 2059 views

Hello All,

        We have the following issues on Touch UI dialog.

  1. There are 2 fields ( first one is a drop down and second one is a  text field) should appear side by side as shown in the attachment.
  2. The drop down has 3 possible values "None","Greater Than" and "Less Than". When we select "None", the second input field should be disabled. When we select either "Greater Than" or "Less Than" it should be enabled.

It will be great, if you could provide some quick inputs on above issues.

 

Regards

Sreeni

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
September 6, 2016

Hi 

All the CSS of the Touch UI Dialog can be located at /etc/clientlibs/granite/coralui2.

You can change the CSS as per your need.

Note:- This is not the best practice to make changes in /etc/clientlibs/.

 

To make changes in /etc/clientlibs....

1) Create your own client library "mylib" in /etc/designs or /etc/clientlib
2) Embed all required client libs
3) Add the <cq:includeClientLib categories="mylib" /> at the beginning of
the page rendering process.
4) Check the generated HTML for inclusion of clientlibs. If there are more
clientlibs loaded as this "mylib", modify your embed definition and go to
step 2.

 

I hope this would help you.

 

Thanks and Regards

Kautuk Sahni

Kautuk Sahni
U
user00725Author
Level 4
September 6, 2016

Thanks Kautuk Sahni for your quick response.

It will be much more helpful, if you can provide some similar sample helpx documents or web links( due to tight time constraints that we have)

Regards

Sreeni

smacdonald2008
smacdonald2008
Level 10
September 6, 2016

There is no docs or community helpx article on this use case. I have never seen anyone ask this before. However - as Kautuk points out - this is all driven by CSS. 

Terms & ConditionsAccessibility statement

Loading footer...