The Persuit of PaperKing - Day 5 - Team Meeting

Today was the first time that we were able to sit down as a development team since we started.  We kept it to about a 30 minute meeting, since we are all working on other projects as well, and it limits our ability to get stuck on any one issue (if it isn't real clear in a minute or two then we can come back to it later - it is early enough that everything is flexible.)
The goal of today was to look at the specifications as we had them, and to do a little more brain storming about what this could be, and how it could be used as an actual tool
After a little discussion about the specifications about how it will work, and the technical details it became a little more apparent that we were on the right track (pun intended).  As the application is built up and a preliminary UI is put in then more discussion can be had about usability and intuitivity.
The meeting then turned to issues of educational application.  How will a learner be able to get value from "playing" the application.  We didn't come to any specific answer, but we came up with several related ideas that will become essential.  Most of the ideas and issues revolved around creating some constraints (like the amount of attempts allowed), and methods to force math and physics (like using stepper values to adjust the track height that use a step of 10, where the right value would have to be "keyed in" of 7 - so you can't just get it from trial and error, you have to calculate.)
On a technical note, we did end up switching out the Canvas3D class in Flex for a CanvasView3D class.  The Canvas3D was having difficulty actually showing the 3d objects we were using for testing.  It isn't clear if it is a branch of Papervision that is causing the problem, or the version of Canvas3D, comes with the territory of using pre-release code.