I've also done some thinking on this, though I've never had the time to actually sit down and code my "solution".
I think the best compromise is to have a paster command (say, "restart") that would generate a diff (or set of diffs) between a newly quickstarted project and your current one. This is most obvious as a paster command, but might be easier/simpler to implement as a stand-alone script. so: 1) identify the current project (either by being inside the directory or from a parameter to the "restart" command 2) create a new quickstarted project 3) diff the two (my preference would be for one diff for each file in a parallel directory structure, but others may disagree) 4) [very hard to get right!] automatically merge the two (this may not be feasible, in fact it probably isn't...but you MIGHT be able to get at least some of the files merged together) 5) [assuming you can get 4 to work] Run tests on the merged project I think the first 3 are do-able, at the very least, and I think it would be a very helpful addition to the TG ecosystem. After all, part of the joy of working with TG is the removal of so much "scut-work" so you can think about your actual problem domain. Kevin Horn On Fri, Sep 12, 2008 at 4:17 PM, Jorge Vargas <[EMAIL PROTECTED]>wrote: > > On Fri, Sep 12, 2008 at 9:30 AM, Lukasz Szybalski <[EMAIL PROTECTED]> > wrote: > > > > On Thu, Sep 11, 2008 at 11:32 PM, Mark Ramm <[EMAIL PROTECTED]> > wrote: > >> > >> Looks like this is based on an old quickstart. > >> > >> I would try adding the demo code to a newly quickstarted project and > >> see if this does not just magically go away. > > > > I'll try it. > > > > Just out of curiosity, are there any plans for some kind of paster > > upgrade command that would do this for me? (aka bring my quickstart > > code to a latest version) > > > In theory it's really simple but in practice this is almost a no go. > There have been some attempts but nothing is 100% usable, if I recall > correctly the old quickstart command (pre-1.0), had this option and it > broke a lot of people's code (some even lost work). So it was removed, > as quickstart grew more complex.... > > The biggest problem is that there is no way to know where to insert > the new code. And with complex things that put code in different parts > of the templates, for example identity, it's just a ton of work... > > I have been thinking of this for a long time, as the base project > template is one of the biggest migrations issues, as you almost 100% > of the time need to diff a newly quickstarted project against the > older code. So far I have come up with nothing, except documenting the > changes. > > > Lucas > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
