Collision detection/introspection

[GoogleCodeExporter]

We need to be able to know where we are drawing stuff, instead of relying 
on fire-and-forget.

This would be tremendously helpful in order to be able to both avoid undue 
overlapping, and fill the areas properly, without resorting to manual 
tweaking and ad-hockery.

Original issue reported on code.google.com by a...@nvg.org on 14 Oct 2008 at 12:37

[GoogleCodeExporter]

I suggest putting the definitions for ordinaries and charges in a separate 
script so that, in addition, new charges can be tacked on quite easily. Also we 
need to really decouple the parser from the class definitions so either can be 
reworked more easily without bumping in to each other.

Original comment by robb1701 on 27 Sep 2010 at 8:28

• Changed state: Accepted
• Added labels: Maintainability