On May 30, 10:58 am, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > > 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. > > Perhaps there could be a balance here, where if you just want the > default behavior of the component, and don't care about making > any tweaks to its behavior, you don't have to have much of the > component's code injected into your project, but once you start to > override things, you can have the code for that particular aspect of > the component copied into your project tree, where you can override > the behavior directly? >
Other than upgrading, are there other issues with injection / templating? Is reuse in other projects / apps a concern? Are there other issues? From the standpoint of seeing what's going on and making changes though, injection is attractive (IMO). How would a hybrid approach work? I'm guessing the end developer would issue a command to spit the component into the project, but what then? Is it totally in the end-developer's hands? From a component writer's perspective, it seems like there would be more overhead, but maybe you could make tools to help out. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
