Patrick Lewis wrote: > 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).
Not really. The big issue is that it adds a lot of code to your project that you didn't write, and makes it difficult to perform upgrades to the component itself. > 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. Well, it seems to me that you'd issue a command the very first time that you wanted to use a component, and you could tell it whether you wanted the entire component's source spit into your project, or if you'd prefer to use the defaults. Either way, I think code should be added to your project, but the default would be placeholders that import from the component, aliasing the classes/functions from the component itself into your project's namespace. If you wanted to later tweak things, you could issue another command, which could selectively start replacing those placeholders (model, templates, API, etc) with the actual generated code/templates, which you could then edit to your heart's content. This is what I meant by a "hybrid" approach. -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
