> Sure, but we never came up with a good name :) The API team does not want to > have the utility libraries use the google.* namespace because it can cause > confusion as to what is a official library and what is not. I am totally > open to using a namespace once we have decided on what, feel free to offer > suggestions :)
I've been using "gmaps" cause it's simple and short. For bigger libs may have a sub namespace but the smaller ones just under it directly. > I did the RichMarkerPosition thing for improved readability of the code but > I am tempted to ditch it and just allow strings to be passed in instead, > what do you think? I do not have preference one way or the other. Using enum may have a remote benefit of having some IDE prompt a list, also reduce chance of typo, but not that big of a difference. What about the jsdoc util? I ran with the jsdoc tool in the project and it hit error and nothing get generated. Is there barriers to release your internal jsdoc tool to this project? I figure it's same tool just different template. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
