Merge branch 'master' into boost_filesystem

Conflicts:
	tests/CMakeLists.txt

2 files changed, 13 insertions, 0 deletions

diff --git a/doc/TODO.txt b/doc/TODO.txt
index 6bb3a15..4fac889 100644
--- a/doc/TODO.txt
+++ b/doc/TODO.txt
@@ -98,6 +98,7 @@ o Error reporting/debugging
     o Provide some interaction for debug walk-through?
   - Provide visual highlighting of geometry corresponding to code
     -> could aid debugging a lot
+  - Optionally output console log to a file
 o Computation
   - Run CGAL rendering in a background thread
   - Enable viewing/editing while rendering
@@ -165,6 +166,9 @@ o Mesh optimization on STL export
   - Remove super small triangles (all sides are short)
   - Replace super thin triangles (one h is short)
 o Misc
+  - center as default: Very often, center=true is used everywhere.
+    Make a global variable ($center?) control this to beautify code
+    and the avoid typical errors when forgetting to specify center
   - Go through default values of parameters (e.g. cube() has x,y,z=1 while linear_extrude() has height=100)
   - Add support for symbolic names to child() statement 
   - Add 'lines' object type for non-solid 2d drawings
@@ -189,6 +193,7 @@ IDEAS FOR LANGUAGE CHANGES
 --------------------------
 o More strict checking of module parameters to make e.g. this fail:
   module test(a,b) { a=1; b=2; echo(a,b,c); } test(c=3);
+  (also for built-in modules)
 
 CODE
 ----
@@ -222,8 +227,10 @@ o Use a logging framework to get debugging/info output more under control?
 
 DOCUMENTATION
 -------------
+o Auto-generate API documentation instead of, in addition to or combined with, the wikibooks docs.
 o Write checklists for typical extension work (add new module, add new function)
   -> make sure new test files are added
+o Clarify include/use better in the wikibook docs (e.g. that use'd modules have to be self-contained)
 
 TESTING
 -------
diff --git a/doc/testing.txt b/doc/testing.txt
index 67d14ba..4623a96 100644
--- a/doc/testing.txt
+++ b/doc/testing.txt
@@ -96,3 +96,9 @@ log as well as your sysinfo.txt file, as well as running 'ldd' against
 your binaries, to make sure that the proper versions of libraries are
 getting compiled and linked with the test binaries. 
 
+7. Other issues
+
+The OpenSCAD User Manual has a section on buildling. Check there for updates:
+
+http://en.wikibooks.org/wiki/OpenSCAD_User_Manual
+