We need to develop or standardize a paradigm or approach to
using multiple frameworks within Exp. E.g., we historically had
used YUI, but are moving to Twitter Bootstrap and jQuery. However
in our move to Bootstrap under Twitter Bootstrap v2.3.x, that
framework was given a major revision by its moving to v3.x.
Therefore...we have three (3) distinctly different (theme)
frameworks we use within Exp based on the theme itself. This
approach works well so long as there is/was only ONE administrative
framework (slingbar & chrome & configuration views) which
until now had been YUI.
Since we are moving away from YUI as the primary framework, YET
want to maintain (some?) backwards compatibility, we'll have to
overcome some currently limitations. In a pure sense, we would NOT
want to FORCE users into a new admin UI simply because of an
Exponent upgrade (unless it is a major upgrade) In other words, you
should be able to get bug fixes without having to re-train your
site admins/editors.