[Opal-commits] opal changelog.txt,1.9,1.10 todo.txt,1.45,1.46

[tylerstreeter <tyl...@us...>]

Update of /cvsroot/opal/opal
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27565

Modified Files:
	changelog.txt todo.txt 
Log Message:
finished overhauling xml loader

Index: changelog.txt
===================================================================
RCS file: /cvsroot/opal/opal/changelog.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** changelog.txt	23 Feb 2005 04:56:48 -0000	1.9
--- changelog.txt	26 Feb 2005 10:22:22 -0000	1.10
***************
*** 2,5 ****
--- 2,6 ----
  , 2005
  ------------------------------------------
+ 	* Overhauled XML loading system
  	* New additional object creation system: all objects can be created from/saved to a data structure
  	* Separate Joint types were combined into a single Joint class

Index: todo.txt
===================================================================
RCS file: /cvsroot/opal/opal/todo.txt,v
retrieving revision 1.45
retrieving revision 1.46
diff -C2 -d -r1.45 -r1.46
*** todo.txt	25 Feb 2005 06:40:26 -0000	1.45
--- todo.txt	26 Feb 2005 10:22:22 -0000	1.46
***************
*** 2,26 ****
  =================
  
! * make OPAL XML spec/sample file that includes everything; put on website
  
  * look at scons dylib-building problem on os x
  
  * fix memory allocation across dll boundary
  	- Blueprint
  	- BlueprintInstance
! 	- volume collision check results
! 
! * XML loader, manager
! 	- update parsing
! 	- update instantiation functions
! 
! * should spaces be stored in xml/blueprints?
! 	- probably not
! 
! * fix naming descrepancies
! 	- desiredPos, desiredPosition, getState, getVelocity, etc.
! 	- make it more unified
! 
! * search and replace existing assert() calls and std::cout calls
  
  * certain function calls (e.g. setStatic) during collision events crash the system
--- 2,15 ----
  =================
  
! * fix crashing problem when instantiate ball joint from example.xml
  
  * look at scons dylib-building problem on os x
  
+ * add offset transform to instantiateBlueprint
+ 
  * fix memory allocation across dll boundary
  	- Blueprint
  	- BlueprintInstance
! 	- volume collision check results -> put results in a specific class
  
  * certain function calls (e.g. setStatic) during collision events crash the system
***************
*** 29,35 ****
  	- replace 'garbage' system with delayed destroy events
  
- * separate Solid options for sleeping (setSleeping(true/false), setSleepingEnabled(true/false))
- 	- per-Solid sleepiness
- 
  * Add a boolean to Solid that determines if it generates contacts at all (the docking volume shouldn't collide with anything but should generate collision events still).
  	- maybe look at a more powerful solution with collide flags
--- 18,21 ----
***************
*** 37,51 ****
  * reenable collision detection for static-static, static-sleeping cases (or have an option)
  
- * change description (on website and sf project page) to highlight the main attractions
- 	- cross-platform
- 	- simple API
- 	- high-level objects (e.g. Solids, Joints, Motors, Sensors)
- 	- XML file serialization
- 	- uses existing collision detection/physics engines underneath
- 	- provides an abstract interface that can be extended to support other physics engines
  
  For Version 0.4.0
  =================
  
  * add 'web' and 'doc' modules to repos
  	- maybe just add 'web' module that contains docs
--- 23,34 ----
  * reenable collision detection for static-static, static-sleeping cases (or have an option)
  
  
  For Version 0.4.0
  =================
  
+ * search and replace existing assert() calls
+ 	- fatal errors print a message and assert
+ 	- non-fatal errors just print a warning
+ 
  * add 'web' and 'doc' modules to repos
  	- maybe just add 'web' module that contains docs
***************
*** 76,79 ****
--- 59,66 ----
  * should all modes with multiple options (e.g. spring motor, accel sensor) take bit flags?
  
+ * separate Joint into separate subclasses?
+ 
+ * separate Motors with different modes into separate types?
+ 
  Build System
  ============
***************
*** 149,152 ****
--- 136,140 ----
  * search code for TODOs
  
+ * blueprints could have a single boolean space parameter like "insert the whole bp into a space or not"
  
  Long-term Ideas