On Oct 11, 3:59 pm, Tim G <[email protected]> wrote: > Thanks Larry, I appreciate the help. I never imagined porting > something from v2 to v3 would be so incredibly difficult. Thankfully > I am managing to find ways around all the road blocks I keep running > into but man, what a pain! :) > > If v2 wasn't depreciated I'd highly consider just sticking with it and > I still might although now I'm on a masochistic mission to see if I > can get this thing converted successfully.
My personal take is that v3 still isn't quite ready for prime time. Yes, v2 is deprecated, but it still has a few years of life. I don't think the time is quite right to port a working mature applicaiton from v2 to v3. v3 is less developer friendly and more difficult to use; the event driven model is hard for developers to understand. I understand the google engineers desire to keep v3 light, but many of the features are not anywhere near as mature as they are with v2. And those developers that are jumping in with v3 are really breaking ground. You can find the functionality implemented in v2, but then you need to port what you need to v3, and develop the pieces that don't exist (yet). -- Larry > > On Oct 11, 6:38 pm, "[email protected]" <[email protected]> > wrote: > > > > > On Oct 11, 3:27 pm, Tim G <[email protected]> wrote: > > > > Is there an example you could point me to of plotting a route without > > > the renderer? I'm guessing you use getDirections() rather than > > > setDirections() and just plot a polyline yourself? > > > I have a few brute force examples posted to the group and > > athttp://www.geocodezip.comhttp://www.geocodezip.com/v3_directions_cust... > > > They aren't particularly pretty, more proof of concept. > > > -- Larry > > > > On Oct 11, 6:02 pm, JKurtock <[email protected]> wrote: > > > > > Directions are transitive; New York to Boston to Baltimore is the same > > > > as New York to Boston, then Boston to Baltimore. > > > > > All you need to do is break up your string of 20 waypoint-cities into > > > > strings with no more than 8 internal (via) waypoints. Run those > > > > directionsRequests and string together the results. > > > > > You will probably want to write your own display of the results > > > > (rather than a Google directionsRender), but that is not difficult. > > > > > On Oct 11, 12:46 pm, Tim G <[email protected]> wrote: > > > > > > It seems the old "New York, NY to:Boston, MA to:Baltimore, MD > > > > > to:Albany, NY" method is limited to 23 plus origin/destination. So to > > > > > rephrase my question, is there a way to get similar functionality out > > > > > of v3 or am I stuck with waypoints and the measly 8 maximum?- Hide > > > > > quoted text - > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - -- 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 [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-js-api-v3?hl=en.
