Changeset 3058

Timestamp:

Jun 2, 2006, 3:42:45 PM (19 years ago)

Author:

duncan

Message:

geo_ref thoughts

File:

• documentation/requirements/thoughts.txt (modified) (1 diff)

documentation/requirements/thoughts.txt

@@ -72 +72 @@
 See also work program ideas 2005-2006
 
-How to get the same amount of smoothly from a large mesh to a small mesh. How does the alpha value get scaled?
+How to get the same amount of smoothly from a large mesh to a small
+mesh. How does the alpha value get scaled?
 
 
+
+SCRIPTING INTERFACE DESIGN PRINCIPALS (2/6/6) -as agreed to by Duncan and Ole
+(This is regarding the API that people use when writing run_??.py
+files)
+
+- The API's don't have geo_reference as a keyword.
+- When points are entered, a geo_spatial instance can also be entered. 
+
+- Current API's that have geo_reference as a keyword don't have to be
+  changed as a matter of priority, but don't document this 'feature'
+  in the user manual.  If you are refactoring an API, then plase
+  remove geo_reference as a keyword.