Hi, As much as I love Torque on the front end, the more I work with the source, the more nervous I get. Specifically, the OM templates are a mess. Granted, they do complicated stuff, but I think it needs abstracted out into several base cases instead of always checking booleans all over the place and conditionally including code.
That being said, I'm not entirely sure the refactoring would work, but I'm willing to give it a shot someday in my free time. (Currently I'm trying to find the best way to get the Texen PropertiesUtil away from it's hardcoded uses of generator's template path). However, I'm afraid to even touch the templates because of the bugs that are posted fairly frequently concerning various combinations of tables/keys/properties that break the templates. It's great that people fix them and submit the patches, but the patches make the codebase even more complicated without having a way to verify we don't re-introduce the bugs later on. So, I don't know if the current test bed is setup for it, but I'd like to encourage that any patches to the templates get their own test case to ensure we don't break the patch sometime in the future. This would require the test bed having multiple project-schemas/build.properties as we'd have to test a variety of configurations and the OM code each spits out. However, with this kind of structure in place, I'd feel a lot more confident about cleaning up the templates and Torque in general. Does this sound like a good idea and something worth putting time into? Thanks, Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
