Changes between Version 171 and Version 172 of PakistanDevelopers

Timestamp:

09/03/10 10:49:58 (14 years ago)

Author:

Fran Boon

Comment:

--

PakistanDevelopers

@@ -95 +95 @@
    * This is partially-working: clicking the button on enables the crosshair, clicking it off disables, but currently it's not being set on 1st load
   * See nearby locations (Feature Markers) & be able to select them as an alternative to placing a new Marker (nice message saying 'Do you mean...)
-===== Hierarchical Autocomplete for Locations: #502 =====
+===== Hierarchical Autocomplete for Locations =====
+ * #502
  * If an Lx is selected in Autocomplete then load the appropriate dropdown (& any above it) & put this in there
   * freeing up the Name field again for a sub-location
@@ -102 +103 @@
  * A user might wish to select an existing location & then amend the hierarchy!
    * make people do this via the 'Locations' menu? (Give them Help on this?)
- * Changing things in higher levels should clear lower levels?
  * Check whether fields are readable/writable (e.g. addr_street may need to be hidden from some modules)
  * Add robustness by checking L0 isSelectBox()
@@ -110 +110 @@
  * Download hierarchy levels to a Store in the background to improve performance?
  * shn_read/shn_list - replace existing system in read/list? (consistency & ease of maintenance)
- * ~~~Update form: Hierarchy needs populating from old record~~~
- * ~~~Include a Search box underneath the hierarchy which is an Autocomplete filtered to the appropriate level that we've already selected~~~
-   * ~~~Format of results should include the hierarchy of missing steps to help resolve duplicate names~~~
- * ~~~Add a visible field for location name beside address (defaults to being populated by the name of the resource, but can be overridden)~~~
- * ~~~The extra 'Save Location' button shouldn't be required (Auto-Save when main form is submitted. Does this make code simpler as only need to update location_id at the end?)~~~
- * ~~~Handle the case where we link to a general Lx Location record & which we now refine to add a Street Address or Lat/Lon~~~
-  * ~~~we have a UUID but the 1st update should be either just changing location_id (if using the hierarchy) or creating a new record (if using lat/lon or addr_street)~~~
+ * ~~Update form: Hierarchy needs populating from old record~~
+ * ~~Include a Search box underneath the hierarchy which is an Autocomplete filtered to the appropriate level that we've already selected~~
+   * ~~Format of results should include the hierarchy of missing steps to help resolve duplicate names~~
+ * ~~Add a visible field for location name beside address (defaults to being populated by the name of the resource, but can be overridden)~~
+ * ~~The extra 'Save Location' button shouldn't be required (Auto-Save when main form is submitted. Does this make code simpler as only need to update location_id at the end?)~~
+ * ~~Changing things in higher levels should clear lower levels?~~
+ * ~~Handle the case where we link to a general Lx Location record & which we now refine to add a Street Address or Lat/Lon~~
+  * ~~we have a UUID but the 1st update should be either just changing location_id (if using the hierarchy) or creating a new record (if using lat/lon or addr_street)~~
  * Don't display Lat/Lon for Admin levels (Lx)?
  * ~~if shn_has_role(!MapAdmin): Provide an 'Add Location' option next to each level of hierarchy~~