#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: | [email protected]…, [email protected]…, [email protected]…, [email protected]…, Eugene Lazutkin, [email protected]…, [email protected]… |
Blocked By: | Blocking: |
Description (last modified by )
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 10 years ago by
comment:2 Changed 10 years ago by
Description: | modified (diff) |
---|
comment:3 Changed 10 years ago by
Cc: | Eugene Lazutkin added; [email protected]… removed |
---|
comment:4 Changed 10 years ago by
Status: | new → assigned |
---|
comment:5 Changed 10 years ago by
Keywords: | 1.8-mobile added; 1.7-mobile removed |
---|---|
Milestone: | 1.7 → 1.8 |
comment:6 Changed 10 years ago by
comment:8 Changed 9 years ago by
Component: | Charting → Dojox |
---|---|
Milestone: | 1.8 → future |
This won't be integrated into 1.8 in Dojo. Work is on going as a side project see djeo.
comment:10 Changed 9 years ago by
Here are the links: http://djeo.org redirects to https://github.com/vvoovv/djeo
See also https://github.com/vvoovv/djeo-demos https://github.com/vvoovv/djeo-gmaps https://github.com/vvoovv/djeo-ge https://github.com/vvoovv/djeo-ymaps
Those packages are also accessable from http://packages.dojofoundation.org : djeo djeo-demos djeo-gmaps djeo-ge djeo-ymaps
comment:11 Changed 9 years ago by
Fixing the linkage for vvoovv. Depending on the shape of djeo, perhaps we target 1.9?
comment:12 Changed 9 years ago by
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 9 years ago by
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 9 years ago by
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
OK, works for me. vvoovv, hope you don't mind.
comment:15 Changed 9 years ago by
djeo is clearly "2.0" style component. I don't think it makes sense to release it under dojox.
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).