Landis Utility Library
To-do list for Landis Utility library
NOTE: This list is no longer active; instead, see the project's issue tracker at Google Code.
Util
- Move this library to Google Code project hosting because the Spatial Modeling library depends upon it. (top priority) (Done)
- Change namespace to Landis.Util (or .Utility) for consistency with GeospatialModeling library's namespace. (Issue 3 at Google Code)
- Add copyright notices to the top of each source file (high) (Issue 1 at Google Code)
- Notice should include BSD license (same as Spatial Modeling Library). (Issue 2 at Google Code)
- Add System.IDisposable to FileLineReader (Issue 6 at Google Code)
- Move ListOfEditable class into this library (Issue 7 at Google Code)
- There is a copy of it in the core's main module
- Move Landis.Util.Testing class from Biomass Succession and harvest extensions into this lib (Issue 8 at Google Code)
- Consider creating a separate library (Landis.Testing?) that includes this class and the NUnitInfo class.
- Add variation of FineErrorMarker method(path, errorLineMarker, errorEofMarker)
- Change Percentage type to a struct (should be according to Value Type Usage Guidelines) (high) (Issue 9 at Google Code)
- Consider moving Percentage0to100 to Landis.Util (Cannot locate this data type)
- Write Unit tests for Percentage0to100 (particularly Parse method)
- Modify how to handle Registering Types for Input Values (high) (Issue 10 at Google Code)
- Problem: a type’s static ctor explicitly registers the type, but the use of the type as a generic parameter – InputValue -- does not result in the static ctor being called. As a result, a number of plug-ins have hacks (e.g., creating temporary values)
- Possible solution: Define a custom attribute that can be used with either the type’s static Register method or its Parse method
- Add unit test for Directory.EnsureExists method that actually creates several missing directories. (Issue 11 at Google Code)
- NUnitInfo.GetTextWriter should display exception message when it can't open output file - that may be due to file being locked by another process (e.g., NUnit GUI). (Issue 12 at Google Code)
- Fix problem in NUnitInfo.GetTextWriter because NUnit's GUI was renamed from "nunit.exe" to "nunit-gui.exe" in NUnit 2.4a1. (Issue 13 at Google Code)
- Merge changes that Victor made for documentation on 1.1-doc branch into trunk. (Branch never used)

