(i can't think of a good way to say this, so i'll just dive straight in.
i'm sure that people'll straighten me out when i go wrong...)
ecs2 is a new version of jakarta-ecs with a new internal structure.
there's a lot of repetitive leg-work involved in converting code from
the old structure to the new.
i've been working on using code generation with texen to (hopefully)
make this easier and quicker.
the idea is to generate elements and attributes from DTDs (via
xml-schema) and velocity templates.
i've been working on this for the last couple of weeks and i feel that
i've proved the concept and have stuff which'll do pretty much what's
needed :-)
what i need to do now is to tidy stuff up, document and make it
available so that other ecs people can take a look and use it. the
problem is that i have made general changes and enhancements.
i think that the best thing would be for me to take this code and give
it a home (for the moment) in the ecs project. that way, it can be used
over there without worrying.
i will post the design ideas in the code (and patches if they're wanted)
back to this list and take stuff from there. (i also have some nice
examples such as generating xml object-model parsers from xml-schema.)
(i'm pretty sure that the generation stuff won't make it into the ecs2
release so we can worry about where code should live to generate ecs
element models from DTDs later on.)
comments? is this a good plan?
- robert
