Changeset 3058


Ignore:
Timestamp:
Jun 2, 2006, 3:42:45 PM (18 years ago)
Author:
duncan
Message:

geo_ref thoughts

File:
1 edited

Legend:

Unmodified
Added
Removed
  • documentation/requirements/thoughts.txt

    r2771 r3058  
    7272See also work program ideas 2005-2006
    7373
    74 How to get the same amount of smoothly from a large mesh to a small mesh. How does the alpha value get scaled?
     74How to get the same amount of smoothly from a large mesh to a small
     75mesh. How does the alpha value get scaled?
    7576
    7677
     78
     79SCRIPTING INTERFACE DESIGN PRINCIPALS (2/6/6) -as agreed to by Duncan and Ole
     80(This is regarding the API that people use when writing run_??.py
     81files)
     82
     83- The API's don't have geo_reference as a keyword.
     84- When points are entered, a geo_spatial instance can also be entered.
     85
     86- Current API's that have geo_reference as a keyword don't have to be
     87  changed as a matter of priority, but don't document this 'feature'
     88  in the user manual.  If you are refactoring an API, then plase
     89  remove geo_reference as a keyword.
Note: See TracChangeset for help on using the changeset viewer.