This might sound very dumb question but I am just confused. I am quite new in Google Maps and I had gone through two different types of mapping object namely GMap2 and google.maps.Map. What is the difference and which is better?
Thanks in advance!
GMap2 is from previous version of google maps framework (version 2.x). Google has completely rewritten its maps javascript library, making it more lightweight and compatible with mobile devices. It's version 3.
If you are a beginner, start with version 3 (google.maps.Map)
Related
I have a LibGDX project which I can run on all platforms that are supported by LibGDX. Recently I started integrating the Google Nearby Messages API. I got it working on Android through platform-specific code, pretty much like the description on Google says it should be done. Now I want to integrate it in the iOS project, which uses RoboVM, but according to their documentation (https://developers.google.com/nearby/messages/ios/get-started) I should use CocoaPods, which doesn't seem so straightforward for integration, especially in a LibGDX project. I hope someone with some experience in doing this can help me out, or point me to a project in which that's already done. Thanks!
As far as I know, with RoboVM you use their available RoboPods supporting the most popular 3rd party intgrations, but not all.
Popular Google tools are listed there but I did not see Google Nearby Messages API, more info here:
https://github.com/MobiVM/robovm-robopods
What version of the Google Maps API is used if you don't specify a version number? The latest release version perhaps? The documentation about versioning doesn't say.
The documentation does recommend that production apps specify a minor version number. But it also says "all API changes will be backwards-compatible," so is there any reason I should specify a version number if I'm not using any experimental features?
English is not my first language, so I might be reading this part wrong (from the versioning doc you linked)
You can indicate which version of the API to load within your application by specifying it using the v parameter ... The nightly (development) version, specified with v=3 or by omitting the v parameter.
Further down, there's a mention of 3.9 being nightly.
Documentation of Versions
Version 3.9 Reference (Nightly)
So, sounds like leaving out the v (which I do) will load the nightly, version 3.9.
<script type="text/javascript" src="http://maps.googleapis.com/maps/api/js?sensor=false"></script>
About part two of your question: I can think of a very good reason to specify a version:
Consistency, predictability, reliability
You might want to keep the same look-and-feel while working on a update for the latest release of the Maps API. For example, the labels or map controls may move around.
On the other hand, it's good to keep track of the latest versions, too. By lagging too far behind your application might stop working when it becomes unsupported.
I'm sure there are better reasons. I'm not a professional Maps developer.
I've been building extensive Google Maps based applications and according to my experience it's better to specify API version for a long term projects. For example an issue I was facing recently:
The system was built and tested along with v3.6 but Google released an experimental version
Which is loaded by default but from the other hand not recommended for business or professional development.
Therefore to avoid some malfunction that appeared suddenly I had to specify API version:
<script src="http://maps.google.com/maps/api/js?sensor=false&v=3.16" type="text/javascript"></script>
Then after that everything came back to normal. You may quickly consult API version by typing in the browser console google.maps.version.
I hope someone may find it useful.
i'm need to develop and web application that uses maps, and i have two option in my to reach the goal. Google maps or bing maps, my concern it's witch it's better about
Documentation it's very important
Implementation with a Web application develop in .net
Fast learning curve
i need recommendations because for my point of view both are a completed tools for solve my problem. Thanks
I strongly recommend Google Maps.
Fabulous documentation
Code Playground
Very fast learning curve
With the new v3 api you don't need a api key
Cheers
take a look at our series of articles comparing aspects of both, and Ill admit up front I like bing more but have tried to be as impartial as possible:
http://www.earthware.co.uk/blog/index.php/2011/02/ajax-mapping-apis-google-maps-vs-bing-maps-update-pushpin-display-performance/
http://www.earthware.co.uk/blog/index.php/2010/12/mapping-apis-google-maps-vs-bing-maps-update-api-download-sizes/
and the original posts:
http://www.earthware.co.uk/blog/index.php/2009/12/mapping-apis-google-maps-vs-bing-maps-part-1-introduction/
http://www.earthware.co.uk/blog/index.php/2009/12/mapping-apis-google-maps-vs-bing-maps-part-2-licensing/
http://www.earthware.co.uk/blog/index.php/2010/01/mapping-apis-google-maps-vs-bing-maps-part-4-developer-support-community/
I'm searching for complete explanations about how to use geokit-rails3. I've found loads for rails2 but not for rails3. Does any of you have a simple and complete tutorial about how to display a google map on Rails3, from A to Z ?
Thanks a lot for your help !
Geokit (and geokit-rails3) can be thought of as geocoding utility libraries, useful for finding and storing the locations of model instances and for performing location-based searches, but they do not include mapping support.
For Google Maps mapping in rails 3 there are a few choices, but no clear winner. At the moment, most end up just using the Google Maps javascript API version 3 directly. I found Google's Maps API documentation very clear and easy to use.
Is it possible to convert a standard PHP based widget integrated with google maps API to a flash based widget? If yes, what are the ways?
I expect it will generally be a manual process, because the code styles are so different, code-to-code conversion would be likely to be difficult/fragile/error-prone. The only automatic way that I could conceive of is a html-to-flash-ui conversion, which would get you a static look or prototype to start with, but wouldn't help you in the creation of the active/reactive/dynamic elements of the new flash widget.
A quick google search brings up a few paid references to html to flash conversion, as well as a few pages mentioning some libraries that might be worth pursuing, if just as a shortcut to creating a prototype that you would have to refine:
http://drawlogic.com/2008/01/11/as3-flash-to-html-conversion-library-htmlwrapper/
and here:
http://osflash.org/flashml
Since there is one free library, there may quite likely be others as well.