What is the output target architecture of WebMAP3?

[isanabria]

I can see a lot of great stuff in the Preview tab of my Migration Solutions.  However, I can see just a small part of the output code.

I would like to understand further the architecture of the output code.  Where can I find it?

Thanks!

[John Browne]

Great question. There's a short answer, and a longer one.

The short answer is: on the server side, we create an ASP.NET MVC single page application. We also use Unity framework from Microsoft for inversion of control (aka dependency injection) as part of our state management approach. We also use some JavaScript frameworks, such as KendoUI from Telerik, or AngularJS (with Bootstrap). On the client side we use HTML5 and CSS with either Kendo or Angular for MVVM. Our Angular target (you have to choose when migrating an app between targeting Kendo for a more Windows-like UX or Angular for a more Web-like UX) includes Bootstrap for responsive design. 

For the longer answer check the blog--I have one article that introduces our architecture and will be creating more soon.

[John Browne]

Here are two blog posts (so far) that drill down on our app architecture:

http://www.mobilize.net/blog/webmap-app-architecture-part-1

http://www.mobilize.net/blog/webmap-app-architecture-part-2

[Cyberops]

Hi John

Thanks for share.

Best regards

Cyberops