PDA

View Full Version : Google Map Panel



michaeld
Nov 25, 2013, 3:10 AM
Just occurred to me, and I realize that a lot of developers have integrated their own solution for this since there are forum threads going back to 2009, but why doesn't Ext.Net have a built in GoogleMapPanel with a few apis like adding markers with clickable tooltips?

http://www.sencha.com/blog/integrating-google-maps-api-with-ext-js/ (http://www.sencha.com/blog/integrating-google-maps-api-with-ext-js/)
https://github.com/VinylFox/ExtJS.ux.GMapPanel/

geoffrey.mcgill
Nov 25, 2013, 12:29 PM
Hi,

We actually supported the GMapPanel all through Ext.NET v1.x, although there was a few reasons I remember why it was dropped from Ext.NET 2.x. Maybe Daniil or Vladimir remember more:

#1. Shea did a great job on the original Ext JS UX version, but the component needed a good overhaul by the time Ext.NET 2 rolled around. I'm not sure the original code was ported to Ext JS 4.x either. I did contemplate taking on the updates and contributing back to Shea, but (see next)

#2. There was very little demand for the component. Even though there were some issues and limited functionality with the component, we received very few support requests, or feature requests. Since dropping the component, I think you were the first to bring up the topic.

It's something we could certainly support in the future, and I would love to build a robust Mapping component. I will review the idea.

Thanks for taking the time to post your comments.

michaeld
Nov 26, 2013, 2:36 AM
#1. Shea did a great job on the original Ext JS UX version, but the component needed a good overhaul by the time Ext.NET 2 rolled around. I'm not sure the original code was ported to Ext JS 4.x either. I did contemplate taking on the updates and contributing back to Shea, but (see next)


The link I shared seems to suggest that it has been updated to extjs 4 and supports both static and dynamic (which is GREAT). I haven't tried it though and I'm still not too sure how to use general extjs extensions in extnet or else I'd confirm.


#2. There was very little demand for the component. Even though there were some issues and limited functionality with the component, we received very few support requests, or feature requests. Since dropping the component, I think you were the first to bring up the topic.

I'm pretty confident there is demand. There seem to be plenty of users on the forums who've mentioned it at least, though as stated, I think the reason it might be light is most of us have already rolled our own. I know I did before it was available in v1.x and because of that didn't need it when I upgraded to v2. I'd have had to mention it sooner for sure if I had used the one in v1 when upgrading.

The only reason I thought about it again is because I'm building a totally new mapping page and thought it would be nice to try the built in one, then realized there wasn't one. It sure would be nice to have one that resizes with Flex in panels as that was my primary consideration to look. The problem though is that the mapping source from google does require a height and a width as part of the initialization. I'm not sure how well that translates into resize updates or even if it can. I'll keep you posted if you're interested, but that was my biggest reason for wishing for the implementation. That, and markers, as I'm about to have to roll my own again that supports more than one.


It's something we could certainly support in the future, and I would love to build a robust Mapping component. I will review the idea.

Keep me posted. From a marketing standpoint, I think it would just enrich the robustness perception of the toolkit, especially with an example in the explorer. It's one of those components that users considering the kit might think, "nice, and now I know that if we move in that direction, we have that too." But its true, it is still sort of specialized, though in my opinion, no more specialized than say the calendar control is.

geoffrey.mcgill
Nov 26, 2013, 3:45 AM
Yes, it does appear the library was updated to Ext JS 4. That's good news.

After the Ext.NET 2.4 release we will review the idea of creating a new Mapping component.

ADV
Jun 25, 2015, 9:01 AM
Hello, have you given up the idea?

Alessandro

Daniil
Jul 03, 2015, 1:15 PM
Yes, unfortunately, there is no built-in Mapping component in Ext.NET 2 and 3.