This content has been marked as final. Show 4 replies
Given ExtJS 4.1 is still beta, your taking a calculated risk working with an API that's not finalized.
The forum link with the work-around is a reasonable solution, though it would be better to use Ext overrides, or define your own custom components extending the ExtJS components.
The simplest approach is to have a plugin render a DIV instead of an input item, and then render the combo-box using contentEl.
Looking forward how the two products fit together is much more interesting, because for mobile templates the APEX team have eliminated the HTML tables they have always used for layout.
This greatly increases the potential to generate a complete page using ExtJS syntax generated by plugins.