Many physic code similarites could be merged

[GoogleCodeExporter]

Many physic related methods share same behaviours, with only small real
differences (or not realy justified)

I'm thinking of (and have started to) merging those methodes and
attributes, then moving them up to the newly created "Drawable" class.

=> then, behavioral differences (between files and persons) would be
managed only by parameters

Namly :
- update()
- freshen()
then
- relax()

Code now shows javadoc's @todo where appropriate.

Do I move on this track a bit more ?

Original issue reported on code.google.com by sebastie...@gmail.com on 6 Jul 2008 at 12:48

[GoogleCodeExporter]

makes sense to me.  how far along are ya?

Original comment by kld.crea...@gmail.com on 11 Jul 2008 at 1:02

[GoogleCodeExporter]

I have the easy part already done, so I would commit it soon, then only the core
complexity would remains.
This last part would take some time, to enable some kind of behavioral 
configuration.

Original comment by sebastie...@gmail.com on 11 Jul 2008 at 6:39

[GoogleCodeExporter]

Ya, I've been playing around with trying to keep the names from piling up in the
center.  My current attempt is to create an invisible person at the center that
doesn't move.  And then attach an edge between that guy and each person as they 
show
up.  Freshening that on each update.

So far, they still pile up, but they drift away.

http://lurch.homelinux.org/supertux2_codeswarm.avi for an example.

Original comment by nawglan on 12 Jul 2008 at 12:05

[GoogleCodeExporter]

Think this one can be closed.

Original comment by nawglan on 23 Jul 2008 at 12:16

• Changed state: Fixed