hello again jerome
I spent a good deal of time looking through the 3d classes as you said thee is alot of functionality in those classes. the problem is that most of it is in the wrong place. in your base class (object) you just about everthing but the kitchen sink in there. this is going to cause alot of unnessary bloat. to give you a few examples let's say we have a machine gun and this gun shoots a lot of bullets. there's probable someone shooting back at you so there could be a good 200 bullets fling through the air. I'm pretty sure we aren't going to try to attach a camera to those bullets and yet we will have exacty two references to the camera at a cost of 4 bytes each and a total of 1600 bytes of wasted memory. if you take a good look at what's in there I'm sure you will see that most of it is of little use to a bullet and all adds up to wasted memory. I could rebuild your 3d engine make it more efficient add features to it that don't exist now and much needed documentation. of course there would be a couple of conditions. 1. if people really like my engine and you make alot of money then you would have to give me a job. 2. you won't let people bloat it all up again as I see happen to many opensource engines. I built a cad program in delphi years ago and while it is no blender it has some cool features like printing out templates that can be pasted to a board and cut out with a bandsaw. anyway I'm going to have to do the work either way. so think it over, dont see how you have much to loose if you don't like it then you wouldn't have to use it.