Hi Ross, thank you for reply and i really appreciate help and suggestions coming from you guys at this forum, but our opinions in this case differ, i disagree in general.
When something MUST be done before using an object, it is in competency of this object to check, if it is correctly initialized. So when gMap.setCenter MUST be called right after GMAP initialization before any use of GMAP object, why it is not a part of GMAP constructor? This is not about speed and reliability of the API, this is about good design imo. On the other side, you forgot to mention another important aspect, which is effectivity. There will be allways compromises between these requirements, but designers should allways keep them in mind. Yes, there will be allways problems related to technology (browsers, javascript, html etc.), but i don't want to fight with technology and framework problems at the same time. And i really don't want to debug API to inspect API problem... Just take a look on this forum and its structure, constantly repeating same questions and problems, wouldn't be better to analyze them and make appropriate changes in the api to prevent them? I hope, that my point of view is clear even my english:) Marek On 28 Bře, 02:09, Rossko <[email protected]> wrote: > > Finally got it! Huh, map MUST be centered before initialising > > opensource MarkerManager... No exceptions, no warnings nor any other > > alerts, but lot of frustration... Totally magic for me :/ > > Quoting from the documentation 'Map Basics', > http://code.google.com/apis/maps/documentation/introduction.html > "Once we've created a map via the GMap2 constructor, we need to > initialize it. This initialization is accomplished with use of the > map's setCenter() method. The setCenter() method requires a GLatLng > coordinate and a zoom level and this method MUST be sent before any > other operations are performed on the map" > > > I'm not sure that this is the right way how to effectively develop > > mashups :( So, final conclusion for me: MarkerManager is not > > compatible with GMarkerManager... > > Not sure what you mean ; they're not identical in behaviour or else > you wouldn't be changing over? > > > 2Google team: what about some variable checks and validations before > > trying to use them? > > No thanks, I'd like the API to stay fast and rely on good > programming :^) Look at any of the discussions around here; there are > a lot of apparently obscure errors caused by feeding poor data to the > API or doing things in the wrong order; if they checked for imaginary > points or invalid HTML or all the other possibilities we'd fall asleep > waiting for the maps. There's always a conflicting requirement > somewhere! > > cheers, Ross K --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
