Changes between Version 9 and Version 10 of BluePrint/GIS/LocationSelector

Timestamp:

11/22/10 09:59:57 (14 years ago)

Author:

Fran Boon

Comment:

S3LocationSelector work-in-progress

BluePrint/GIS/LocationSelector

@@ -23 +23 @@
 
 == !ToDo ==
+ * Move the implementation to a server-side widget so that it applies automatically to all instances of the field (can then remove from custom view templates)
+  * Work has started on this: S3LocationSelector in {{{modules/widgets.py}}} & {{{static/scriptsS3/s3.locationselector.widget.js}}}.[[BR]]Enable by uncommenting in {{{models/03_gis.py}}} & comment the old autocomplete in a view to try it out (e.g. {{{views/cr/shelter_autocompletes.html}}}).
  * Increase Robustness (currently there are many bugs)
  * Redesign the Look/Feel to make it more usable
@@ -30 +32 @@
   * Don't load the Map within the page but do this as a separate server-side call
  * Make it work with components (see below)
- * Move the implementation to a server-side widget so that it applies automatically to all instances of the field (can then remove from custom view templates)
  * 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.
@@ -41 +42 @@
  * Experiment with downloading all Locations at startup (into a [http://api.jquery.com/data/ jQuery Data store]) & filtering client-side, or maybe downloading just the full next level of hierarchy proactively (e.g. we've got the L0 selected, we have the L1 dropdown populated accordingly...we could download *all* L2s within the L0 ready for when the L1 is selected & then filter the downloaded L2 data to those within the relevant L1 to populate the L2 dropdown with). This would also provide an automatic cache (within the page only).
  * Extend the location_id() API to support controlling which levels of hierarchy we're interested in for a resource (some may be only interested in the province, whereas others may need a precise location)
+
 === Known Issues ===
 There are various bugs in the current implementation, some of which are listed below.
@@ -48 +50 @@
 
 ==== 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. 
+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"}}';
+   var location_id = '{{=jr.prefix + "_" + jr.target()[1] + "_location_id"}}';
  {{except:}}
-   var location_id = '{{=request.controller+"_"+request.function+ "_location_id"}}';
+   var location_id = '{{=request.controller + "_" + request.function + "_location_id"}}';
  {{pass}}
 }}}