Hi Tim,
V3 is modular. We provide a few public classes (Map, Marker, etc) in the first JS download, but download the rest of the classes only as they are used. So v3 can scale to many features with little bloat for sites that don't use these features.
That said, there will be features from v2 which make sense as additional libraries for v3. These might include GLog (largely replaced by JS debuggers such as FireBug), GDownloadUrl and other functions provided by general JS libraries.
- Ben
On Oct 27, 2009 3:30 AM, "Saxan Sartar" <saxan....@gmail.com> wrote:
i am wondering how new functionality like this will be implemented. If the goal of v3 is to keep things lite and fast for mobile devices, it would seem adding more and more v2 features could undermine that goal.
My question to google would be, are you considering using an extensibility model or instead updating core components, for these types of features?
-tim
On Mon, Oct 26, 2009 at 9:38 AM, mattia berlusconi <ber...@gmail.com> wrote: > > Directions in v3...