What I'd like to consider upfront WHAT EXACTLY do you want to use the versioning system for. If you want to cover all usage scenarios, you will end up writing a web front-end for versioning systems (that just happens to be used for a web2py application), which might be not what youre shooting for (no small task).
Just out of curiosity, have you looked at https://code.launchpad.net/~achipa/web2py/versioncontrol ? It's a bit broader approach, still rough around the edges, but does work for the most common workflow use cases. Don't let the default subversion module fool you, this is fully modular, you can plugin whatever VCS you want. It has been talked about a few times on the list. On Apr 29, 6:40 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > there is a new experimental feature in trunk. > > run from source > easy_install mercurial > > go to web2py admin and design an app > > you will notice a new menu item [mercurial] > > if you click on it it creates new mercurial repo associated to the > app. > if you write a comment and "commit" the current app gets committed in > the repo. > > This needs to be polished. we should add buttons to revers, get curret > status etc. > > I could use some help... anybody? > > I am using these APIs > > http://www.selenic.com/mercurial/wiki/index.cgi/MercurialApi#head-fee... --~--~---------~--~----~------------~-------~--~----~ 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 web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
