User: vauxia Branch: HEAD Date: Wed, 06 Aug 2008 07:05:46 +0000 Added files: /modules/geo/modules/geo_field geo_field.info geo_field.install Modified files: /modules/geo/db mysql_spatial.inc postgis.inc /modules/geo geo.info geo.module /modules/geo/modules/geo_field geo_field.module Log message: Cleanup and progress towards a working D6 field module: - Renamed CCK fields with geo_ namespace ( e.g. geo_point, geo_linestring ) to avoid collisions - Removed geo_backend_field functions. These were intended to outsource CCK's hook_field implementations so that the backend modules could take care of everything. Good idea, but it also created a lot of duplicate code. Meanwhile, I'd argue that the geo module itself - and its backends - should not be cognizant of CCK. That's what an API is, right? - Renamed API functions to geo_db_add_field, geo_db_drop_field from geo_add_geometry_column, geo_drop_geometry_column. - Removed geo_insert_geometry_data, and added geo_db_field_from_wkt to specify column insertions. We'll leave the rest of the inserting to the calling function. - Removing references to geo_field and its table tracking. This seemed like a really good idea when we created it, but seems like needless housekeeping now, as the field module is already keeping track of its geo fields. - Began updating and refactoring D5 to D6 code. Links: http://cvs.drupal.org/diff.php?path=contributions/modules/geo/modules/geo_fi... http://cvs.drupal.org/diff.php?path=contributions/modules/geo/modules/geo_fi... http://cvs.drupal.org/diff.php?path=contributions/modules/geo/db/mysql_spati... http://cvs.drupal.org/diff.php?path=contributions/modules/geo/db/postgis.inc... http://cvs.drupal.org/diff.php?path=contributions/modules/geo/geo.info&old=1... http://cvs.drupal.org/diff.php?path=contributions/modules/geo/geo.module&old... http://cvs.drupal.org/diff.php?path=contributions/modules/geo/modules/geo_fi...