> 1. Wondering if our migration strategy should align with availability of your support. What I mean to ask you is when is the complete HTML5 based front end coming out from VMWare web client?
You mean the new HTML5 client? It's already available as a "Fling" at vSphere HTML5 Web Client, we update it weekly with new features. Support for HTML plugins is not quite finished there but coming soon. GA will be later this year.
> 2. I understand that we need not wait for that and can use HTML5 bridge way of migration. In that case how would you advice us to start with? We are planning to start off so we need not wait for a new feature implementation to pop up and we then pursue the HTML way rather we can start migrating gradually right away. please throw some lights on this...
I am not sure I get that question but I would start migrating the simple views while you are learning JS and a new framework.
> 3. Another technical question on the Service layer. If I understand correctly We have to end up changes on the service layer to support the UI layer migration for sure. Am I right?
No. The service layer is largely unchanged. The only additions necessary for a HTML plugin are the Spring controllers that handle http requests, see how it works in the SDK samples.
> 4. Any hard recommendations on the JS framework that should be used?
We like and use Google's Angular JS becomes it's powerful and is now the most popular JS framework out there. (If you start now you should go straight to the new Angular 2)
But any other framework will work as well since plugin views are sandboxed.
> 5. Please provide pointers to some documentation links available within the community or outside.
Our documentation is included in the SDK 6.0 bits, along with samples.
To learn Javascript or a particular framework I would use online resources available everywhere, tutorials, code samples, etc.
