[Opal-commits] opal todo.txt,1.43,1.44

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

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

Modified Files:
	todo.txt 
Log Message:
minor fixes

Index: todo.txt
===================================================================
RCS file: /cvsroot/opal/opal/todo.txt,v
retrieving revision 1.43
retrieving revision 1.44
diff -C2 -d -r1.43 -r1.44
*** todo.txt	23 Feb 2005 03:58:24 -0000	1.43
--- todo.txt	23 Feb 2005 06:35:46 -0000	1.44
***************
*** 4,14 ****
  Joints, Solids, etc. -> JointData, SolidData, etc. -> Blueprint -> saveToXML(Blueprint, filename) ... loadFromXML(filename) -> Blueprint -> JointData, SolidData, etc. -> Joints, Solids, etc.
  
- * joints
- 	- one init function: takes separate params
- 	- other init: takes a bp
- 	- can be init'd more than once with different types
- 
- * all objects have an init function that takes a data object
- 
  * look at scons dylib-building problem on os x
  
--- 4,7 ----
***************
*** 28,41 ****
  * all modes with multiple options (e.g. spring motor, accel sensor) should take bit flags
  
- * "BP" (blueprint) structs/classes
- 	- all parameters use defaults from Defines.h
- 	- search and replace "blueprint" with "BP", except for the base Blueprint class
- 	- overloaded init functions (or "loadFromBP") can take these instead of individual params
- 	- objects each have "saveToBP(BP&)" functions
- 	- how do different BPs refer to other objects? by name? by int id?
- 	- shapes can be added to solids in two ways (or should we just do one?)
- 		- add a ShapeBP to a SolidBP, then create the Solid
- 		- create a Solid, then add a shape by passing it a ShapeBP
- 
  * XML loader, manager
  	- update parsing
--- 21,24 ----
***************
*** 46,51 ****
  		- BPs can be requested by name/ID
  
- * reenable collision detection for static-static, static-sleeping cases (or have an option)
- 
  * fix naming descrepancies
  	- desiredPos, desiredPosition, getState, getVelocity, etc.
--- 29,32 ----
***************
*** 60,63 ****
--- 41,47 ----
  
  * 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
+ 
+ * 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
***************
*** 84,88 ****
  * implement sensors
  	- RayCastSensor (i.e. "PSD (position sensitive detector)" or "rangefinder"): measures distance from sensor to first intersection (attach to a solid [be sure to ignore collisions with the attached solid] or nothing)
! 		- must be updated manually by user? (to keep raycasting from getting call every step)
  	- ContactSensor
  		- hold a queue of contact events (attach to a solid, to a single shape, or to nothing?)
--- 68,74 ----
  * implement sensors
  	- RayCastSensor (i.e. "PSD (position sensitive detector)" or "rangefinder"): measures distance from sensor to first intersection (attach to a solid [be sure to ignore collisions with the attached solid] or nothing)
! 		- not updated regularly; must be updated manually by user
! 	- VolumeSensor (i.e. "proximity sensor?"): similar to RayCastSensor, but for a volume; finds all Solids colliding with a given (attached) Solid
! 		- not updated regularly; must be updated manually by user
  	- ContactSensor
  		- hold a queue of contact events (attach to a solid, to a single shape, or to nothing?)
***************
*** 100,103 ****
--- 86,90 ----
  
  * look at (and maybe remove) mass ratio stuff
+ 	- there may be a problem when you have a tiny object between two massive objects; one massive object should affect the other but can't
  
  Build System
***************
*** 109,114 ****
  * add SConstructs to samples
  
- * put headers in separate dir from source?  (e.g. root contains src, include)
- 
  Possible Ideas
  ==============
--- 96,99 ----
***************
*** 270,273 ****
--- 255,267 ----
  		- custom Motors
  
+ * Most objects can be created in two ways
+ 	- create the object (automatically uses default values); change specific parameters
+ 	- setup a Data object and pass it into the object's init function
+ 	- some objects (e.g. Joints) must have init called before using them
+ 
+ * Shapes can be added to solids in two ways
+ 	- add a ShapeBP to a SolidBP, then create the Solid
+ 	- create a Solid, then add a shape by passing it a ShapeBP
+ 
  * custom motors cannot be saved to/loaded from an XML file