History of GmapPackage
Version 41
GmapPackage
A Wikid Google Map Engine
Goal
The goal of this project is to create a package that lets you edit a Google Map like a wiki, with some Flickr integration thrown in for spice.This will take the best features of sites like WikyBlog-Maps, VirtualGoogleEarth, and 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 makes 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.
Code
You can get the latest stage of development by checking out _bit_map from CVS HEAD branch.Google Map Hacks to Include
- XMap Library
- GxMarkers Tools
- T-Labels
- PdMarker
- Custom Map Tiles
- Geocoding
References
- Official Google Maps API
- Google Maps API News Group on Google Groups
- http://mapki.com
- Flickr API
- Flickr API Key Application
Some Other Useful Stuff
Bitweaver Stuff
Programming Stuff
- ADODB Data Dictionary for PHP
- Javascript and Navigating the Dom Tree
- Using Javascript with Smarty and elegant solution.
- DB JOIN FAQ on Wikipedia
Concerns
Map loading function requires onload="onload()" in the BODY tagThe question is how can I get this into the BODY tag of the bitweaver template without changing the template.
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
Outline of Functions for map part storage and retrieval
(this is pretty close)get map
- get map by id- get map data (lat/lon/maptype etc)
- get sets ids
- get related style ids (get rid of duplicates)
- get icon and marker styles data
- get sets data
- render map
update/save map
- get map by id- save map values and data
- get map data
- update map
get marker/maptype/poly
- get object by id- get object data (lat/lon/label)
- get sets ids (list from set table)
update markers/maptypes/polys
- get object by id- save object values and data
- get object data
- update map object
- update sets data via object id
get styles
- get style by id- get style data (color/weight/type etc)
update styles
- get style by id- save style values and data
get sets
- get sets ids- get related style ids (get rid of duplicates)
- get icon and marker styles data
- get sets data
update sets
- get sets ids- save object values and data
How to set up your own custom package
This is stuff I have learned about creating packages for bitweaver while creating this GMap package.Download the "Sample Package" from this site
Setting up your database tables
Database (DB) Tables are defined in "schema_inc.php"This file goes in your admin folder. Each package has one of these.
Including tpl files in the page header
The bitweaver Kernel is set up to automatically include header information from all packages. Any information you want included in the HTML HEAD you put in a file named "header_inc.tpl" which goes in your package's _templates_ folder.To create conditional header includes simply nest tpl files in the header_inc.php file. You can do this by using the this include code:
include file="bitpackage:yourpackagename/subheader.tpl"
(note: put this in curly braces)
(note: put this in curly braces)