Having methods that takes a lot of arguments can be a real pain. You not only need to remember which arguments to pass but also in which order to supply them. Things gets even worse when you need to add more arguments to an existing method. This article will show you a better way of doing this by using only one argument.
As I mentioned in the article Extending Google Maps API 3 with libraries a couple of weeks ago, you can add functionality to the Google Maps API by using libraries. One of these libraries are the Geometry Library. In this article I will show how you can use the function of that library to calculate distances and areas. I will also explain some additional navigation functions that you might find useful.
In the latest version of Google Maps API 3 (version 3.4) a new exciting feature is introduced: 45° imagery in selected cities around the world. This feature will let you see the world from a whole new angle. This change also calls for new properties and controls for the Map Object which will all be explained in this article. As a bonus I will also introduce you to another new feature, the brand new Map Overview Control.
There’s a few methods used for traversing the DOM-tree in jQuery that is confusingly similar, well at least they were for me. This article will explain the difference between them and when you should use which one.
Using InfoWindows is a brilliant way to display information about a certain location. Since they provides you with a space to put text or whatever HTML you please, they can be used in very interesting ways. In this article, which is the fourth in a series about Google Maps API 3, I will show you how to make good use of this great feature.
Markers are the perfect way to put places of interest on a map and that’s probably one of the most used features in digital maps. In this article, which is the third in a series about Google Maps API 3, I will show you how to use them in Google Maps API 3.
It’s been a while since I last wrote on this blog and I thought I would get you up to speed why that is. The reason is that I’ve been occupied with writing a book about Google Maps.
I haven’t written a book before so this is new territory for me. What I’ve noticed so far is that it progresses far slower than I predicted, but at least it progresses steadily even if slower than anticipated. I’ve taken a few weeks off of my regular work to devote to writing this book but this time won’t suffice, so there will probably be quite a few late nights and weekends of writing as well.
The Google Maps API has evolved to version 3. This version is a complete rewrite and focuses primarily on speed. The new API also features new ways of using it. This article is the first in a series exploring version 3 of the Google Maps API. This first article will take a look on how to create a simple map and explain some differences from the previous version.
This article explains how to dynamically toggle the visibility of markers in Google Maps as well as how to deal with an annoying bug that occurs when trying to do this while using an utility library, like the MarkerManager.
Yesterday a new version of the ever so popular Google Maps API was released. In the new version the focus has been on improving speed, especially on mobile devices. I’ve been fortunate enough to be part of the beta testing and has been able to provide feeback directly to the developers. So far I think they’ve done a great job, even if there’s still more work to be done.
One of the shortcomings in the Google Maps API is that there’s no easy way to add tooltips to polylines and polygons. That’s why I felt inclined to build an extension to Google Maps that adds that functionality. MapTooltip makes it possible to add tooltips to any kind of overlay. It’s even possible to have HTML inside it and to style it to fit your design needs.
In circumstances where you want to notify the user of something, like for example that some information have been saved, a non-modal alert is an excellent solution. It gets your message across without being intrusive and without the need for uneccesary user interaction.
In this article I will describe how to create it with the help of jQuery
Global variables are evil. Although possibly nifty for very small programs it quickly clutters the global namespace and increase the risk for name collisions as are program grows larger. The risk for collisions are even greater when using different libraries and widgets.
Markers is one of the core features in Google Maps and an effective way of displaying places on a map. In this article I will show you how to add a basic marker to a map and also how to add some interactivity to it.
Normally when you initialize a new Google map you set the coordinates for the center of the map and manually specifies the initial zoom level. Sometimes, however, there’s a need to dynamically calculate the center point and zoom level for certain content to fit into the viewport.
Polylines are used to mark out roads, borders and other things that are made of lines in maps. The Google Maps API offers a class for drawing these lines on a Google Map called GPolyline. In this article I will show you how to use these and how to deal with potential performance issues when the polylines gets more complex.
In the ASP.NET MVC Framework, passing JSON from the server to the client script is almost too easy. In this article I will walk you through the code required to make it work.
I’m currently developing a web application that uses Google Maps and have lots of markers with custom icons to mark different things on the map. To administer all these different icons is quite a chore and it took me some time to find an effective way of working with them.
jQuery is going to be a part of Visual Studio. This is a great, and I must say, an unexpected development of things.
For me personally, who’s already using jQuery along with ASP.NET, the main difference will be the intellisense annotation support for jQuery. This will be a welcomed enhancement of my development environment. Needless to say the asp.net team at Microsoft will also build ready-to-use controls in the ASP.NET AJAX Control Toolkit that builds upon jQuery.
According to Scott Guthrie there will be a free download with the jQuery Intellisense support in a few weeks. The ASP.NET MVC download will also contain it and the jQuery library.
Imagemaps was very popular in the early days of webdesign but seem to have fallen out of grace. Probably due to accessibility problems and the rise of CSS based designs. I think that it still has it’s place when used properly and one being aware of it’s potential accessibility problems.
I thought that to actually code this solution would be pretty straightforward, but soon discovered some peculiar quirks. I also couldn’t find any information about this, so I thought that I’d share my experiences with you.