History of GmapPackage
!!Goal
The goal of this project is to create a package that lets you edit a [http://maps.google.com|Google Map] like a wiki, with some Flickr integration thrown in for spice.
This will take the best features of sites like [http://www.wikyblog.com|WikyBlog-Maps], [http://www.pixeldevelopment.com/virtualgoogleearth.asp|VirtualGoogleEarth], and [http://geobloggers.com|GeoBloggers] and merge them in to a package for hosting your own wikimap rather than having to use the existing services which are limited to their hosting, their feature implementation, and their look and feel.
A Road Map for the package is well underway. You can find it below. The engine will have to make extensive use of AJAX.
If you want to join in I'm not a professional programmer, but have faith, this is going to be sweet. If you do want to help out, well I guess you can email me wjames5 -at - nyc.rr.com or find me on irc #bitweaver.
!!Google Map Hacks to Include
*[http://xmaps.busmonster.com/documentation.html|XMap Library]
*[http://groups-beta.google.com/group/Google-Maps-API/search?hl=en&group=Google-Maps-API&q=GxMarker&qt_g=1&searchnow=Search+this+group|GxMarkers] Tools
*[http://gmaps.tommangan.us/tlabel.html|T-Labels]
*[http://www.pixeldevelopment.com/pdmarker.asp|PdMarker]
*Custom Map Tiles
*Geocoding
!!References
[http://mapki.com]
[http://www.flickr.com/services/api/|Flickr API]
[http://www.flickr.com/services/api/key.gne|Flickr API Key Application]
!!Some Other Useful Stuff
*[http://81.138.11.136:8080/bitweaverdocs/ric_NEWS.html|Bitweaver Class Tree]
*[http://digir.sourceforge.net/nightly/DiGIRprov/lib/adodb/docs-datadict.htm|ADODB Data Dictionary for PHP]
*[http://www.bitweaver.org/wiki/TP-Structures|List of BW tables and structures]
*[http://www.howtocreate.co.uk/tutorials/index.php?tut=0&part=25|Javascript and Navigating the Dom Tree]
!!Puzzles
!!!Caching Styles
Markers will have to have a way to track back to maps using their content and styles for caching purposes.
----
!!Loose Bits
These are loose ends created that will eventually need to hook up with other parts of the package:
!!!Permission variables referenced but not created yet:
home_bitmap
* default page when no map_id posted
* REF IN
**index.php
bit_p_read_bitmap
* created based on SamplePackage - not clear that it is needed
* REF IN
**index.php
bit_p_view_bitmap
* intended for alowing viewing of map page
* REF IN
**bit_setup_inc.php
!!!Templates referenced but not created yet:
menu_bitmap.tpl
* not sure what it is for
* SAME AS menu_blogs.tpl
* REF IN
**bit_setup_inc.php
!!!Files from Wiki edited for bitMapki:
package root bitmapki
* bit_setup_inc.php
* BitMapPage.php
admin
* schema_inc.php
----
!!Basic Page Request Set by Step Outline
this is what must happen when a map page is requested.
!!!Get page id via $_REQUEST
(Look up page id and get map page)
*Title
*Description
*Javascript
*Init Marker Set
*Init Polyline Set
*Init Polygon Set
*Marker Sets
*Polyline Sets
*Polygon Sets
*Comments (?)
*Get Marker Styles
*Get Icon Styles
*Get Polyline Styles
*Get Polygon Styles
!!!Look up marker sets by id
*Create Set Arrays
*Get Marker ids per set
!!!Look up markers by id
*Append Set Arrays
*Get Marker Data
**name
**javascript
**icon style id
**marker style id
!!!Look up icons by id
(maybe there is a faster way to handle this...like maintain a list of icons in use for a map. Probably should do this for all styles.)
*Check if icon id is already available
*register id to Icon Style Array
*Get javascript
!!!Look up polyline sets by id
*Create Set Arrays
*Get Polyine ids per set
!!!Look up polylines by id
*Javascript
*Style id
!!!Look up polygon sets by id
*Create Set Arrays
*Get polygon ids per set
!!!Look up polygons by id
*Javascript
*Style id
----
The goal of this project is to create a package that lets you edit a [http://maps.google.com|Google Map] like a wiki, with some Flickr integration thrown in for spice.
This will take the best features of sites like [http://www.wikyblog.com|WikyBlog-Maps], [http://www.pixeldevelopment.com/virtualgoogleearth.asp|VirtualGoogleEarth], and [http://geobloggers.com|GeoBloggers] and merge them in to a package for hosting your own wikimap rather than having to use the existing services which are limited to their hosting, their feature implementation, and their look and feel.
A Road Map for the package is well underway. You can find it below. The engine will have to make extensive use of AJAX.
If you want to join in I'm not a professional programmer, but have faith, this is going to be sweet. If you do want to help out, well I guess you can email me wjames5 -at - nyc.rr.com or find me on irc #bitweaver.
!!Google Map Hacks to Include
*[http://xmaps.busmonster.com/documentation.html|XMap Library]
*[http://groups-beta.google.com/group/Google-Maps-API/search?hl=en&group=Google-Maps-API&q=GxMarker&qt_g=1&searchnow=Search+this+group|GxMarkers] Tools
*[http://gmaps.tommangan.us/tlabel.html|T-Labels]
*[http://www.pixeldevelopment.com/pdmarker.asp|PdMarker]
*Custom Map Tiles
*Geocoding
!!References
[http://mapki.com]
[http://www.flickr.com/services/api/|Flickr API]
[http://www.flickr.com/services/api/key.gne|Flickr API Key Application]
!!Some Other Useful Stuff
*[http://81.138.11.136:8080/bitweaverdocs/ric_NEWS.html|Bitweaver Class Tree]
*[http://digir.sourceforge.net/nightly/DiGIRprov/lib/adodb/docs-datadict.htm|ADODB Data Dictionary for PHP]
*[http://www.bitweaver.org/wiki/TP-Structures|List of BW tables and structures]
*[http://www.howtocreate.co.uk/tutorials/index.php?tut=0&part=25|Javascript and Navigating the Dom Tree]
!!Puzzles
!!!Caching Styles
Markers will have to have a way to track back to maps using their content and styles for caching purposes.
----
!!Loose Bits
These are loose ends created that will eventually need to hook up with other parts of the package:
!!!Permission variables referenced but not created yet:
home_bitmap
* default page when no map_id posted
* REF IN
**index.php
bit_p_read_bitmap
* created based on SamplePackage - not clear that it is needed
* REF IN
**index.php
bit_p_view_bitmap
* intended for alowing viewing of map page
* REF IN
**bit_setup_inc.php
!!!Templates referenced but not created yet:
menu_bitmap.tpl
* not sure what it is for
* SAME AS menu_blogs.tpl
* REF IN
**bit_setup_inc.php
!!!Files from Wiki edited for bitMapki:
package root bitmapki
* bit_setup_inc.php
* BitMapPage.php
admin
* schema_inc.php
----
!!Basic Page Request Set by Step Outline
this is what must happen when a map page is requested.
!!!Get page id via $_REQUEST
(Look up page id and get map page)
*Title
*Description
*Javascript
*Init Marker Set
*Init Polyline Set
*Init Polygon Set
*Marker Sets
*Polyline Sets
*Polygon Sets
*Comments (?)
*Get Marker Styles
*Get Icon Styles
*Get Polyline Styles
*Get Polygon Styles
!!!Look up marker sets by id
*Create Set Arrays
*Get Marker ids per set
!!!Look up markers by id
*Append Set Arrays
*Get Marker Data
**name
**javascript
**icon style id
**marker style id
!!!Look up icons by id
(maybe there is a faster way to handle this...like maintain a list of icons in use for a map. Probably should do this for all styles.)
*Check if icon id is already available
*register id to Icon Style Array
*Get javascript
!!!Look up polyline sets by id
*Create Set Arrays
*Get Polyine ids per set
!!!Look up polylines by id
*Javascript
*Style id
!!!Look up polygon sets by id
*Create Set Arrays
*Get polygon ids per set
!!!Look up polygons by id
*Javascript
*Style id
----