Hello,
We are a long-time user of the Desktop map component. Now I've been tasked with looking at what is involved with using the MVC (and I will probably check Web edition as well) for building a Web version of our app, perhaps targeted at devices such as iPads and Android tablets. After reviewing the documentation and videos, etc., it seems that the map component coding will be reasonably similar to what I wrote for desktop. I hope ThinkGeo does not mind if I ask to hear from those who have used either MVC or Web edition as to the experiences of coding the interface around the ThinkGeo map component, which is where I know the differences will come up. I have done some non-mapping ASP MVC and WebForms coding, so I know how they work and the differences between the two. Can all the interface "stuff" be done with my native .NET language, C#? I have never been a big JavaScript fan and I think my biggest concern is that most of the interface coding will need to use JavaScript. In our desktop app there are probably thousands of lines of code connecting the map with the interface (a fairly complex interface) and the thought of writing thousands of lines of JavaScript is not real appealing. How complex of an interface can we expect in a Web version? Do we have to resort to using jQuery, etc. to make this a manageable undertaking?
Thanks,
Allen
(And thanks again for letting me post something slightly off-topic.)