Opened 8 years ago

Closed 7 years ago

Last modified 7 years ago

#12579 closed enhancement (wontfix)

New Unified Geo Mapping API

Reported by: Chris Mitchell Owned by: Tom Trenka
Priority: high Milestone: future
Component: Dojox Version: 1.6.0
Keywords: 1.8-mobile Cc: vvoovv.projects@…, etissandier@…, peller@…, dylan@…, Eugene Lazutkin, durocher.marc@…, eaullas@…
Blocked By: Blocking:

Description (last modified by Chris Mitchell)

See more details at https://docs.google.com/document/pub?id=1rIepBZ1YZWKFwPuZEhNIWDkmBkhNcAottXmGZ97gpOI

The proposal is to add a new unified geo mapping API under namespace dojox.geo that can have different map engine realizations (similar to how gfx works).

One initial proposed map engine implementation being worked on will be based on the OpenLayers? library under namespace dojox.geo.openlayers. OpenLayers? is a free, Open Source JavaScript? library for displaying map data in web browsers. See more details about OpenLayers? at http://www.openlayers.org

The other proposed map engine being worked on will be based on dojox.gfx and will take full advantage of its advanced functionalities like animation.

Other potential engine implementations have been proposed for future proof of concepts, including: Google Earth Javascript API ESRI WebGL (as far as geo-applications are concerned) (Well, let's wait till it's there)

Change History (15)

comment:1 Changed 8 years ago by Chris Mitchell

Cc: vvoovv.projects@… etissandier@… peller@… dylan@… eugene@… durocher.marc@… eaullas@… added

comment:2 Changed 8 years ago by Chris Mitchell

Description: modified (diff)

comment:3 Changed 8 years ago by Eugene Lazutkin

Cc: Eugene Lazutkin added; eugene@… removed

comment:4 Changed 8 years ago by Tom Trenka

Status: newassigned

comment:5 Changed 8 years ago by Chris Mitchell

Keywords: 1.8-mobile added; 1.7-mobile removed
Milestone: 1.71.8

comment:6 Changed 8 years ago by Chris Mitchell

This feature will need much more work, and since we're near the 1.7 release shutdown, we're deferring to 1.8 release (3Q'11).

comment:7 Changed 7 years ago by Tom Trenka

Just adding a comment to show that this ticket is still active.

comment:8 Changed 7 years ago by cjolif

Component: ChartingDojox
Milestone: 1.8future

This won't be integrated into 1.8 in Dojo. Work is on going as a side project see djeo.

comment:9 Changed 7 years ago by Adam Peller

I suggest providing a link to djeo and closing as 'wontfix'

comment:10 Changed 7 years ago by vvoovv

Last edited 7 years ago by Tom Trenka (previous) (diff)

comment:11 Changed 7 years ago by Tom Trenka

Fixing the linkage for vvoovv. Depending on the shape of djeo, perhaps we target 1.9?

comment:12 Changed 7 years ago by Adam Peller

part of a larger question of how we assemble distributions from external components. we're trying to kick 'future' items. any point to leaving this one around, if the code is currently hosted?

comment:13 Changed 7 years ago by cjolif

We need to decide at some point to not accept anymore new components and stabilize the 1.x releases and manage new components separately as "2.0" style components. In my opinion 1.8 was a bit early for that but 1.9 seems like the right target. So I second Adam we should probably close that one (which by the way won't prevent reverting our decision if needed...).

comment:14 Changed 7 years ago by Tom Trenka

Resolution: wontfix
Status: assignedclosed

OK, works for me. vvoovv, hope you don't mind.

comment:15 Changed 7 years ago by vvoovv

djeo is clearly "2.0" style component. I don't think it makes sense to release it under dojox.

Note: See TracTickets for help on using tickets.