I would rather have Massimo (for example) looking at code with me, and catching that parameter that needs to be a dict, not a list... (and - w/o voice - just being able to see his cursor go, and fix it - "Oh! Thanks!"). This is the essence of team programming for me. And this is faster than posting to the group "why am I getting this erro" to get a response (even if seemingly pretty fast most of the time) "I think you meant 'this' here..."
Pair programming... what a concept! We do it "low tech" on the group - I'd guess that's what 1/2 the traffic is about! On Thu, Nov 20, 2008 at 5:34 PM, achipa <[EMAIL PROTECTED]> wrote: > > With docs and sketches, I understand (and embrace) the concept. But > with code, I think the situation is different. The way you described > it it almost sounded better to work collaboratively through a remote > desktop. Then you see what the other guy is doing, can jump in to type > in things (esp if you have voice contact too). Sounds better than > change/save/oops/reload/merge/save/run to me. And then there are the > guys with the bad habit of pressing save (typing :w actually :) from > time to time even if they're not ready to run it :) So, IMHO it's good > to have such a feature when you *accidentally* trip over someone > else's change, but I'm not nearly as convinced that it's that useful > for peer programming. > > On Nov 20, 10:27 pm, "Yarko Tymciurak" <[EMAIL PROTECTED]> wrote: > > relax ... think pair programming; implemented over the net. try a > > spreadsheet on google docs - 2 or 3 people; each w/ a different color > cursor > > - editing together; open up your options. > > This isn't that... yet... it's just a 'try this"; > > > > On Thu, Nov 20, 2008 at 3:24 PM, achipa <[EMAIL PROTECTED]> wrote: > > > > > If you ask me (and you don't :) remotely concurrently developing a > > > *single* app is a bad idea, as your edits have no guarantee of > > > atomicity/transactions, so you *will* be tripping over each other on > > > more changes than you would probably care. Working on two+ copies of > > > the same application (on the same server) that can be merged through > > > diffs/patchsets, yes, but a single app is just a mess (and the more > > > people work on it at the same time, the bigger mess it will become). > > > This is the reason why people do checkouts and don't just share disks > > > with code (well they do, but then you start the 'quit the XYZ file !' > > > shouting routine). Just my 2ec. > > > > > On Nov 20, 9:44 pm, mdipierro <[EMAIL PROTECTED]> wrote: > > > > Hi People, > > > > > > please give this a try: > > > > > >http://groups.google.com/group/web2py/web/web2py.app.admin.tar > > > > > > you can call it admin2 > > > > > > when you save a file it saved the .bak and if the .bak is there you > > > > can restore using the button at the bottom > > > > > > Moreover if two people edit the same file and user A saves first, > when > > > > user B tries save, web2py goes in "conflict resolution mode", runs > > > > diff and let you merge the file. Please check the code. Perhaps you > > > > can help me make it better with some jquery effects. Moreover there > is > > > > still the unlikely scenario of two concurrent merge. Can you help fix > > > > it? > > > > > > This means different people can now develop together concurrently > > > > remotely. > > > > > > Massimo > > > > > > On Nov 20, 2:06 pm, "Yarko Tymciurak" <[EMAIL PROTECTED]> wrote: > > > > > > > also, it's simple... and "it's done!". > > > > > > > On Thu, Nov 20, 2008 at 2:05 PM, Yarko Tymciurak < > [EMAIL PROTECTED]> > > > wrote: > > > > > > try the "Its All Text" plugin for Firefox - just toggle the > editor > > > when it > > > > > > comes up in the browser, and you'll have the little chicklet > "edit" > > > button > > > > > > on the bottom right of the form. > > > > > > That's fast, and already solved. > > > > > > > > It works sort of like this: > > > > > > > > Session-form encoded filename created. You edit that. "IAT" > watches > > > it - > > > > > > if it changes, it fills in the form for you. > > > > > > > > If you loose power, leave the screen, come back to the same page > - > > > you can > > > > > > still "write" that file from your editor (when the form is > present) > > > and it > > > > > > will get transfered to the browser for you. > > > > > > > > Of course, you can save the file as many times as you want, as > any > > > > > > alternate name as you want (locally). > > > > > > > > Try it - it's fun! > > > > > > > > On Thu, Nov 20, 2008 at 1:57 PM, mr.freeze <[EMAIL PROTECTED]> > > > wrote: > > > > > > > >> Hitting back in Firefox didn't work for me. Maybe because the > file > > > is > > > > > >> re-read on each page load. The method I am working on saves the > 3 > > > > > >> most recent versions as backups and adds a Restore button (next > to > > > > > >> Save) and select that lets you choose which file to restore. > Not > > > very > > > > > >> elegant but functional. > > > > > > > >> On Nov 20, 1:39 pm, "Yarko Tymciurak" <[EMAIL PROTECTED]> > wrote: > > > > > >> > 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).- Hide quoted text - > > > > > > > >> > - Show quoted text - > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---