> 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.
Even if this isn't "automated" it's still worth considering. Providing insturctions on how to cut/paste is fine. But if we automate it, we can also keep the "origonal" version of the plugin (pre-modification) somewhere hidden to facilitate a three-way-merge when you need to update that particular component. The success of the Django component system seems to be based on the fact that people are willing to put up with pain later (difficult component updates) and some hand-editing up front, if they can get some thing working quickly. And I don't think we should ignore that. Sometimes the perfect is the enemy of the good. If we make the future of 3-way merges possible, we don't nessisarily need to make it work right now in order to be successful. --Mark --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
