We may decide to take that approach for some of the current features
that are in v2, but there will probably always be some parts that
cannot be open-sourced, for contractual reasons (e.g. we must make
sure that the correct attribution is displayed for our base map
types), and it will still take us some amount of time to open-source
bits of code. There are some developers here that are creating
open-source versions of v2 features on their own, as well, so keep an
eye out for those.
On Sat, Sep 19, 2009 at 7:19 PM, pi5701 <pist...@chello.at
> just some thought that came into my mind these days:
> why dont you just outsource parts of the current map.js and let people
> host the bits they need on their own server?
> so everyone is able to decide on his own setting glayers, custom
> maptypes, streetview aso on his map?
> What i got so far is that the only reason for v3 is make googlecode
> shorter to run on cellphones, am i right?
> Browsed a lot of googlemap applications whilst building my own map -
> every feature you implented in v2 is used all over the net.
> So why do we have to file a request for any feature that got added in
> v2 the last years for v3?
> excuse me if thats a silly question, but im just master in copy/
> Nevertheless i've put together some nice map the last year with all
> the features v2 offers which my team uses every day at work - missing
> some current features just cause googlemap should run smooth on
> cellphones would be a step back imho.
> Never experienced any unexceptable slowdown or unavailability the
> times we used your great application and bandwidth/ internetspeed
> grows year by year.
> Make a slim cellphone version and let developers take a rest and not
> force them changing code every couple of weeks (imho).
> my map:
> what i got so far with v3 (didnt notice much speed improvement so