Changes between Version 167 and Version 168 of PakistanDevelopers


Ignore:
Timestamp:
09/01/10 00:29:54 (11 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PakistanDevelopers

    v167 v168  
    104104 * Changing things in higher levels should clear lower levels?
    105105 * Check whether fields are readable/writable (e.g. addr_street may need to be hidden from some modules)
    106   * Add Geocoder support
    107   * Add !DrawTool icon in help (like is already there in the Location Update form)
    108   * Use subheadings CSS instead of ASCII ----
    109   * Download hierarchy levels to a Store in the background to improve performance?
    110   * shn_read/shn_list - replace existing system in read/list? (consistency & ease of maintenance)
    111   * ~~~Update form: Hierarchy needs populating from old record~~~
    112   * ~~~Include a Search box underneath the hierarchy which is an Autocomplete filtered to the appropriate level that we've already selected~~~
     106 * Add robustness by checking L0 isSelectBox()
     107 * Add Geocoder support
     108 * Add !DrawTool icon in help (like is already there in the Location Update form)
     109 * Use subheadings CSS instead of ASCII ----
     110 * Download hierarchy levels to a Store in the background to improve performance?
     111 * shn_read/shn_list - replace existing system in read/list? (consistency & ease of maintenance)
     112 * ~~~Update form: Hierarchy needs populating from old record~~~
     113 * ~~~Include a Search box underneath the hierarchy which is an Autocomplete filtered to the appropriate level that we've already selected~~~
    113114   * ~~~Format of results should include the hierarchy of missing steps to help resolve duplicate names~~~
    114   * ~~~Add a visible field for location name beside address (defaults to being populated by the name of the resource, but can be overridden)~~~
    115   * ~~~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?)~~~
    116   * ~~~Handle the case where we link to a general Lx Location record & which we now refine to add a Street Address or Lat/Lon~~~
    117    * ~~~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)~~~
    118   * Don't display Lat/Lon for Admin levels (Lx)?
    119   * ~~if shn_has_role(!MapAdmin): Provide an 'Add Location' option next to each level of hierarchy~~
    120   * ~~L1-L2 Levels shouldn't be editable by non-!MapAdmins (& should be auto-selected by !MapAdmins)~~
    121   * Include the functionality in {{{views/gis/location_autocomplete.js}}} inside the definition of the 'location_id' reusable field
    122    * Although don't use get_location_id() as this slows down the model, instead make it a class instead of a function so you can manipulate the attributes and instantiate once in a lambda
     115 * ~~~Add a visible field for location name beside address (defaults to being populated by the name of the resource, but can be overridden)~~~
     116 * ~~~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?)~~~
     117 * ~~~Handle the case where we link to a general Lx Location record & which we now refine to add a Street Address or Lat/Lon~~~
     118  * ~~~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)~~~
     119 * Don't display Lat/Lon for Admin levels (Lx)?
     120 * ~~if shn_has_role(!MapAdmin): Provide an 'Add Location' option next to each level of hierarchy~~
     121 * ~~L1-L2 Levels shouldn't be editable by non-!MapAdmins (& should be auto-selected by !MapAdmins)~~
     122 * Include the functionality in {{{views/gis/location_autocomplete.js}}} inside the definition of the 'location_id' reusable field
     123  * Although don't use get_location_id() as this slows down the model, instead make it a class instead of a function so you can manipulate the attributes and instantiate once in a lambda
    123124   
    124125 * [wiki:BluePrintGISLocationsHierarchy]