Brian,
I haven’t added my 2 cents because my initial thoughts haven’t fallen within the scope of the EIM discussion to this point. The discussion concerning EIM’s future direction verses EITG’s future direction seems to now be crystalizing and I would like to comment.
I think it may be useful to start asking about EIM’s future in a new context, I don’t know how many users would be willing or excited about it’s development if it came at the expense of Animators development. It seems to me that the conversion of Animators base code to Xcode may have opened up an opportunity to make some fundemental changes that may provide a solution that fits everybody’s needs going forward. If Animator could provide a more robust and extensible architecture, many of the things that people are asking for from an EIM perspective may be able to be added in Animator itself.
The conversion to Xcode has likely made Animators base code as well organized as it’s been. If every part of the current version of Animator could be individually added to a new Animator design through an open and extensible architecture, future components could be added as needed including EIM and a more robust CA system.
It seems to me that EIM becoming Animator through the addition of animation/texturing/rendering will only make a bloated modeler that was never designed from the ground up to do it all.
I suggest that the time is right to make a whole new system based on Animators code reorganized into modules. Additional fully integrated modules can come from EITG or a 3rd party to address future needs while being able to access any part of any other module.
It may sound daunting at first but it seems to me the best way to truly offer a long term future for EITG.
Going forward from this point I would like to weigh the interest in the development of EIM verses the development of Animator, it seems unlikely that they can both be accomplished at the same time.
what think?
Peter Lehrack
