Based on questions we received let me clarify one part of our HTML SDK Fling announcement:
> If you already have an HTML plugin using a previous SDK please try out this new HTML SDK and let us know if you run into any problem. See the documentation included in the SDK for detailed upgrade steps.
This means that existing HTML plugins built with SDK 5.5.x, or 6.0.x, are compatible with the new HTML client, after some small upgrade steps related to webapp context paths. The HTML Bridge introduced over 3 years ago had two goals: first to allow you to build Web client plugins using HTML/Javascript instead of Flex, and second to make those plugins upward compatible with the future HTML client we were planning. The reason plugins are compatible is that the HTML SDK is using the same Javascript API as the Flex SDK's HTML bridge.
However if your existing plugin has a mix of Flex and HTML views, only the HTML views remain visible in the HTML client. The Flex views don't break anything, there are just not visible. Other extensions which don't involve a plugin specific views will work (actions, custom objects, etc.)
Hope that makes sense. Feel free to ask more questions here if you don't find what you need in the HTML SDK docs!
