Kevin Dangoor <[EMAIL PROTECTED]> writes: > Though it's unlikely the implementation would look like this, this is > most definitely something that needs to appear in some form in First > Class. Being able to pick up templates off of a path is pretty > critical when it comes to customizing apps that you install.
It is also interesting for code reuse. I have a piece of code that I'm using in 6 applications now. This depends on model -- it is a common part of the model --, view (there are templates and custom templates for widgets there) and, of course, the controller to do the operation. Being able to pass each application's model *and* master.kid to this "common code" would allow me factoring it out and even reducing this to something more useful for other applications as well. This is a feature that would be very appreciated. (It can be done today with some hacks, but hacks aren't a good thing to have in code...) -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
