By Kevin Schreiner on
4/17/2008
After an extremely long wait, and an audience of patient users, the DotNetNuke Map module has been released! I'd like to first thank everyone who offered their time and ideas during the beta period - all 80 of you provided an excellent structure for the Map module to run through a variety of DNN versions, server environments, and user skill levels. We have a variety of new enhancements already coming in the next month - so be on the lookout for the next version release now that we finally made it through the tracker.
Without further ado, the Map module provides the ability for you to plot your custom data points onto a Map, currently supporting only the interface provided by the Google Map API. Four interfaces come out of the box with the Map module
Read More »
|
By Kevin Schreiner on
2/21/2008
Map made a wonderful debut at the Capital Area DotNetNuke Users group on Wednesday. The incoming reviews were very positive, and I thank everyone for the wait. Version 01.00.08 is still in the release tracker. The documentation is completed, and will be available when I am able to get the permissions to upload it to the project page. In any case - I'd like to get the module some heavier testing, as it is already in use in a number of places.
Anyone interested in a beta test, and a copy of the documentation,...
Read More »
|
By Kevin Schreiner on
12/21/2007
The map project has made its way into testing with much better responses on this round. There were a few hiccups with localization that needed to be corrected before proper release. We are now in version 1.0.7, so obviously there have been a few beta challenges. A bunch of new enhancements are in the queue and will be ready for the next release, but I have held of on inclusion until the download is available to the masses.
Happy Holidays!
|
By Kevin Schreiner on
11/28/2007
The package has now been released back into the tracker. It's odd how certain things crop up that you wouldn't have expected. So - our friends across the pond (from my perspective) have a different way of handling decimal points than myself. This came as no shock to me, but when running your code as a combination of JS from a remote server (in our case google), JS from the local server, SQL from the local server and VB.net on the local server, somehow it becomes as annoying as trying to handle the exchange rates...
Read More »
|
By Kevin Schreiner on
11/16/2007
Well I can say simply, OpenForce -07 was a great show! I'd like to start off by thanking everyone who attended, and especially to the team in control of the DNN portion of the conference. It was fun to finally meet everyone face to face - and well worth the trip. It was a huge success from the corporate sense also, and I've been working diligently to keep up with the traffic that has risen from the show.
As for the Map project - we made it a great way through the release tracker on the first go, but there...
Read More »
|
By Kevin Schreiner on
10/12/2007
Yes, as you have all seen - the map module is now in the release tracker. I had a minor issue with the Source PA and Vault label, but that was easily corrected and the package was resubmitted last evening.
A minor note must be made, for all persons who have followed the 'progress' of the map module. Unlike its cousing "GoMap", Dotnetnuke Map will only be DNN 4.x compliant. There were a few issues with the existing layer of DNN for 3.x, and it was apparent that I would have to make the switch. In any case - it's moving through....
Read More »
|
By Kevin Schreiner on
10/4/2007
I completed my development and testing efforts as of Monday, and started today with the help of sebastian in getting the module into the Release Tracker. I ran into a few troubles over the last few weeks with issues in both the ClientAPI which I was able to provide a fix for and work around, as well as the UrlControl (Which is a documented and corrected issue do to postbacks). The UrlControl Issue I have resolved by checking the 4.x version number, and if less than the fixed version, using a textbox rather than...
Read More »
|
By Kevin Schreiner on
6/26/2007
During the last phase of development the most recent Project Lead chat provided a couple items that need to be modified before release into the tracker. The Geocoding services available in a multide of flavors generally require at a minimum a web service, or HTTP base API connection to send a receive the address and location result. Google's API is the geocoder of choice for this initial release of Map, and requires exactly the same structure. There is a problem, however, in that HTTP connections from Server...
Read More »
|
By Kevin Schreiner on
6/19/2007
Alright! A quick heads up for everyone. We have the front-end points loading with the ClientAPI, and all is a go on that side of the module. The final peice of the puzzle is the ClientAPI integration changes to the javascript for the Edit form (Adding and Editing points) in the control panel, and the callback to the GeoCoder provider. I'll be diligently knocking out that task when my day breaks free today.
The GeoCoder for this release will be specifically built from the Google API which supports 50,000...
Read More »
|
By Kevin Schreiner on
6/17/2007
After getting some help from Jon (thanks for that btw), I have switched the data incorporation over to the ClientAPI rather than the older AJAX library which was employed. This took a fair amount of the weekend as a few logical issues needed to be addressed. I finally have all the peices in place, and at this point we are finalizing the javascript changes required for the switch - which simply means instead of transmitting the entire form and request querystring to the back end (as happened with the original...
Read More »
|