Nice response - i was going to suggest that this ATCE session be watched.

WHen this article was written (which was submitted from one of our super users) a while back, we tested it. I do not recall seeing the situation that you are describing. I will look at this again in AEM 6.1 and see if i can reproduce your issue.

This is not an ootb feature. There is no configuration setting that controls which modes are displayed in the Touch UI. Therefore to attempt to do this, you will need to modify AEM product code.

Only related doc i found is - Change the minification engine for client libraries in AEM This suggests that you have to swap one for another.

Most third party integration done at component level (displayed in a component that is then visible in a web site) or dialog level. I have never seen an example for metadata schema.

This works perfectly when using 2 com.adobe.granite.ui.components.ds.DataSource  objects to populate 2 Select fields. See this video that shows 2 different Select Fields being populated:We updated this AEM Community artilce to add a new section to show this use case -- see the section titled:Use mul...

Another thing to try - i am going to test this as well. Try using a DataSource to populate the Select - as discussed here: Adobe Experience Manager Help | Using an WCMUsePojo class to populate an Experience Manager Touch UI Select Field You can try to setup two WCMUsePojo classes. Bind the first to ...

Are you using AEM Forms for J2EE for AEM Forms for OSGi?

To learn how to create and understand editable templates - see this HELPX community artilce:Adobe Experience Manager Help | Creating an Adobe Experience Manager 6.4 website using Editable TemplatesAlso a Guided Journey here (which is a series of related video content):Scott's Digital Community: Guid...

Yes - you can do that (reuse values from another dialog) or build  your component dialog that lets an author set all values required for for that component.I personally prefer the 1-1 approach. While its true, you are setting more nodes in the JCR dialog branch, its cleaner! In the end, the componen...