> I'm tempted to suggest code generation as a solution for this, but I > think that also provides issues when you want to upgrade a component > for example.
The django way is pure code generation. There are 2 problems with code-generation: 1) putting not-well understood code inside your project can create problems 2) updating generated code gets complicated The Django people handle 1 by having reasonably simple "apps" which aren't hard to understand, and which are reasonably well documented. And they don't handle 2 at all. I think documentation is actually a "good enough" answer to the first problem. And if provide some sort of update tool that does a 3 way merge that helps reduce the update pain, we'll be in very good shape. So, I'm not opposed to code-generation on principe. Particularly if we can help ameliorate the problems that have traditionally made code-generation hard to handle. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
