Changes between Version 12 and Version 13 of BluePrint/GIS/LocationSelector

Timestamp:

12/10/10 16:14:45 (14 years ago)

Author:

Fran Boon

Comment:

Works with Components now

BluePrint/GIS/LocationSelector

@@ -32 +32 @@
    * Work has started on this: {{{map_selector()}}} in {{{controllers/gis.py}}}
  * Increase Robustness (currently there are many bugs)
- * Make it work with components (see below)
  * Add an HTML5 !GeoLocation option ('Current Location')
   * we should use a 'nearby' algorithm (like gis.get_features_in_radius()) to re-use existing locations rather than adding a new one each time.
@@ -51 +50 @@
 This happens when you for example create a new hospital record without creating a new location, but just selecting one (just select a country, for example). When you submit, then a new location record is created with the same name as the selected one - this seems wrong. You can make it visible by uncommenting the show_status line. The reason for this behaviour is that S3.gis.uuid is empty in case there is no old_location, which triggers the creation of a new record. Thus, this does not happen in update, and not either when you create a new location (which creates a new location anyway :D).
 
-==== Use in Component Forms ====
-To be able to apply the location selector to components (e.g. person/presence, where it would be *very* useful), we need to go away from the 'request.controller + "_" + request_function' construction and instead use jr. 
-
-Perhaps this way:
-{{{
- {{try:}}
-   var location_id = '{{=jr.prefix + "_" + jr.target()[1] + "_location_id"}}';
- {{except:}}
-   var location_id = '{{=request.controller + "_" + request.function + "_location_id"}}';
- {{pass}}
-}}}
-
 ----
 PakistanDevelopers#LocationsSelector