Yes - VCS calling interface is what I remember, and I think it is a good idea (if integrated well). For client-end editing "from the web" with some sort of reasonable undo that is more reliable than the browser, I suggest (ahem - hard to do, since I've been using Chrome the past few months) using Firefox, with the "its all text" plugin - that lets you edit any form "offline" in an editor of your choosing (e.g. vi).
Only problem w/ that - when editing w/ web2py, you have to constantly change to "text" mode for "its all text" to come up / work. Would be nice for those people if this default (what comes up when you edit) was configurable. On Thu, Nov 20, 2008 at 1:32 PM, achipa <[EMAIL PROTECTED]> wrote: > > Yarko, maybe including is the wrong word if Massimo is referring to my > VCS web2py patch. I'm providing a mechanism to call whatever > underlying VCS you are using in the project. It's just making web2py > smart enough to detect different VCS files, and putting a button or > two on some of the admin pages to do update/commit/revert (by calling > the adequate VCS modules or simply executing a shell command). I've > already done it for subversion and bazaar, and it's just a couple of > minutes of work to add anybody's favourite. It's very unwieldy (like > any VCS) to use for edit/save/run type of development. > > I personally think the back button is something that you should not > rely on (for whatever purpose). With any fairly recent web2.0 site it > will only wreak havoc as 'back' is not really the 'back' the user > might think it is. I'm generally not a great fan of using web-based > editors for serious work, but that's probably just my VI addiction > speaking. > > On Nov 20, 7:13 pm, "Yarko Tymciurak" <[EMAIL PROTECTED]> wrote: > > On Thu, Nov 20, 2008 at 7:52 AM, mdipierro <[EMAIL PROTECTED]> > wrote: > > > > > Let me think about. I thought we were going to include a real version > > > control system eventually. > > > > We've had this discussion in the past: it makes no sense to "include" a > VCS > > in web2py (too many people have favorites). > > > > It _can_ make sense to write a unified interface, so that you can "plug > in" > > your favorite VCS (and location of repository). > > > > Once that is in place, it would be nice to version projects - but even > so, I > > would do this on-demand ("checkin"). > > > > This kind of editing "undo" is probably another layer of behavior, > distinct > > and different from what a VCS is for. If you look (for example) at > > docs.google.com, when editing a file, auto-save is in effect for some > time > > period. If you look at your document's history, you can see a "session" > > might have 4 or 5 (or more) saves, and inspecting each, you can see that > > they grabbed something you were in the middle of. > > > > I'm not sure we want / need to get that elaborate (or do we?). > > > > Think about implementing a simple 'undo' mechanism first - something > beyond > > browser back, short of an auto-saved versioning system (which I think > would > > be too big a distraction for web2py). > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---