a9CBKW0rWr3jhKabIlDkbG 2008-04-26T18:32:57+00:00 Make it possible for users to attach custom renderer classes false 38085 0 false 12808 36 3 a9CBKW0rWr3jhKabIlDkbG b6Webe9e8r3lKwabIlDkbG 1 0

User attachable drawing classes

2008-04-26T18:32:57+00:00 0.0 0.0 2008-04-27T00:39:30+00:00 Cleaning up the comments throughout the whole project :) - Add comments where necessary - Modify comments to explain better what that code is doing - If a comment is useless and it's not possible to enhance, deleting that comment false 38167 0 false 12808 37 3 a9CBKW0rWr3jhKabIlDkbG b6Webe9e8r3lKwabIlDkbG 0 0

Comment cleanup

2008-04-27T00:39:30+00:00 0.0 0.0 2008-04-27T00:43:10+00:00 If someone wants to play around with that ;) Could increase opengl speed. false 38169 0 false 12808 38 3 a9CBKW0rWr3jhKabIlDkbG b6Webe9e8r3lKwabIlDkbG 0 0

OpenGL Batch Processing

2008-04-27T00:43:10+00:00 0.0 0.0 2008-04-27T19:12:42+00:00 Implement the elasticity parameter for add.* false 38347 0 false 12808 39 3 a9CBKW0rWr3jhKabIlDkbG b6Webe9e8r3lKwabIlDkbG 0 0

Elasticity

2008-04-27T19:12:42+00:00 0.0 0.0 2008-05-02T09:08:35+00:00 <kne> i was thinking "semi-internal" functions that create shapes but don't add them, so you could modify them further, then call another function to add it to the world <kne> the current functions could them obviously call these "semi-internal" functions and the box2d createshape <crazy-chris> interesting... <kne> just if you wanted to mess with it further, you could get the shape def back and do with it as you please <crazy-chris> but that's kinda good idea really :) <kne> (body, shapedef) = _add_box(...) false 40770 0 false 12808 40 3 a9CBKW0rWr3jhKabIlDkbG b6Webe9e8r3lKwabIlDkbG 0 0

Semi-adding functions (only shape, no creating)

2008-05-02T09:08:35+00:00 0.0 0.0 2008-03-31T15:57:47+00:00 py2exe setup script for demos, ... false 23879 0 false 15631 20 3 a9CBKW0rWr3jhKabIlDkbG b6Webe9e8r3lKwabIlDkbG 0 0

py2exe setup script

2008-04-27T00:40:39+00:00 0.0 0.0 2008-03-31T15:58:20+00:00 similar to py2exe, a py2app setup script would be awesome http://undefined.org/python/py2app.html false 23880 0 false 15631 21 3 a9CBKW0rWr3jhKabIlDkbG b6Webe9e8r3lKwabIlDkbG 0 0

py2app setup script

2008-04-27T00:40:53+00:00 0.0 0.0 2008-04-03T21:22:00+00:00 we need nice logos. one for the project itself, and one smaller - icon like thing :) false 25657 0 false 15631 25 3 a9CBKW0rWr3jhKabIlDkbG b6Webe9e8r3lKwabIlDkbG 0 0

nice logo

2008-04-27T00:43:55+00:00 0.0 0.0 2008-04-03T21:55:11+00:00 Create video demos of Elements features to create interest in project and upload to Youtube. Would be nice if it were demoed on an XO, but for now a simple screencast would be nice. false 25671 0 false 15631 26 3 dlPxZ--38r3jCjabIlDkbG b6Webe9e8r3lKwabIlDkbG 0 0

Demo videos with narration

2008-04-27T00:43:44+00:00 0.0 0.0 2008-05-02T09:11:19+00:00 setup.py script which should be able to: (1) Install the Elements module pyBox2D will be separate, so installing anything related to Box2D is unnecessary. false 40777 0 false 15631 41 3 a9CBKW0rWr3jhKabIlDkbG b6Webe9e8r3lKwabIlDkbG 4 0

setup.py

2009-03-10T17:11:50+00:00 0.0 0.0 2008-03-23T20:56:20+00:00 Implement the kind of joints in the API we need for the on-screen drawing false 20969 0 false 15378 7 3 a9CBKW0rWr3jhKabIlDkbG b6Webe9e8r3lKwabIlDkbG 4 0

Joints: Basic Implementation in the API

2008-04-27T00:34:02+00:00 0.0 0.0 2008-03-30T16:59:28+00:00 If the user supplies wrong values -- eg pixels instead of meters, box2d will just crash. Catching and a message would be a nice thing :) false 23572 0 false 15378 18 3 a9CBKW0rWr3jhKabIlDkbG b6Webe9e8r3lKwabIlDkbG 0 0

Check for wrong parameters -- pixels vs meters

2008-04-24T19:28:30+00:00 0.0 0.0 2008-04-13T14:00:11+00:00 The game world is currently limited to what can be drawn on the extents of the window. For actual games, it's obvious that the screen needs to track various objects, the mouse, etc. So, my proposal is to have a sort of camera-class that is called on every physics update (or perhaps on every event, as for mouse movement). We can have several types of classes, these few immediately came to mind: "Track an object at the center, losely track an object at the center, always look at a certain point, and tracking a certain object at an offset on the screen (so you can have your 'mario' not in the middle, but somewhere near the ground or so), and then perhaps limits to how far down it'll go (wrt the bounds of the world), ... " These could be individual classes that implement: to_world/to_screen - coordinate conversions update() - to update the current object / set new mouse coordinates pause() - pause the camera at the current point set_focus() - set the focus on a new object (as supported, not for mouse) set_parameter() - for losely/lazily tracking objects, set the speed at which it does that and more as I think of it... It might also be nice to abstract the current world's ppm into this and allow for dynamic zooming. Though perhaps the ppm could stay as it is, and we just have another scaling factor for the camera. We'll see! false 29730 0 false 15378 31 3 aoRk8O-g4r3jarabIlDkbG b6Webe9e8r3lKwabIlDkbG 4 0

Cameras

2008-04-24T20:30:16+00:00 0.0 0.0