Wow Mike! I didn't know that Rick Borup published a PDF with all the info for configuring SourceTree/Mercurial/Git with FoxBin2Prg. It's really a great document, thanks por pointing it out!
http://www.ita-software.com/papers/Borup_GitVsHg_Published.pdf 2017-02-21 8:15 GMT+01:00 <[email protected]>: > I want to get setup with BitBucket asap, and I've already printed out Rick > Borup's session from 2015 as a reference guide. > > > > On 2017-02-20 18:12, Fernando D. Bozzo wrote: > >> Hi Mike: >> >> We are using it with PlasticSCM, the best DVCS I know of, compared with >> SourceSafe, CVS, SVN, and Git. >> Git is really good, but PlasticSCM have better GUI and algorithms that >> help >> a lot identifying differences. >> >> On VFPx, on the help pages of FoxBin2Prg I've dedicated a few pages >> explaning a basic workflow with it, but many of the concepts I explain >> there are applicable to other SCM/DVCSs. >> >> The nice thing about SCM/DVCS tools is that some of them allow configuring >> external tools using internal triggers or external GUIs or scripts that >> can >> be selected, in some cases from configurable internal menues. It's really >> easy to hook a converter like FoxBin2Prg on personal scripts to do >> conversions, and then use the SCM/DVCS to do it's stuff. >> >> One thing that every SCM/DVCS tool gives you is the possibility of viewing >> the files that have changed, this file can be obtained from command line >> (that means: automated from inside your scripts), so you can use this list >> of changed files to call the converter and do the convertion just for the >> changed files. Actually, this is what the 2 Git projects on VFPx do to >> generated the text files from binaries. >> >> Some people do not get the SCM/DVCS work correctly, and ends checking-in >> "every changed file".... so when compiling a project, you have all >> binaries >> changed!!... but really the compiled code have changed on 99% of them, and >> few files just have changed their code. This part is when FoxBin2Prg >> enters >> in action, because only generates the text files of the binaries who's >> code >> had really changed, so when you later see the changed files, you can undo >> the changes an all binaries that have not a regenerated text file, so at >> the end you left only with the changed ones. >> >> This may be sound a little complicated, but in practice a checkin is >> something like this (in PlasticSCM): >> >> - Show changed files on a panel (all binaries that where changed by hand >> or >> a recompilation) >> - Right-click and select "Regenerate all text files from changed binaries" >> and wait for the conversions >> - Show changed files on panel (again), now showing the previous files and >> the text files for the binaries that really changed code >> - Select all of the binaries that have not a text file showed as changed >> (so that text files are not showed) and undo their changes >> - The few files that remain are the binaries with their respective text >> version, so now you can checkin >> >> This way a typical changeset have little files, which makes Diffing >> between >> branches a breeze, or at least much more clean. >> >> To answer your final question: We do not use the VFP project hook, because >> the PJX is part of the project to, and must be checked-in if had changed, >> so all the diff/merge/checkin/checkout stuff are done on the SCM/DVCS tool >> side (with a GUI in our case, but can be done with explorer scripts or >> other ways). >> >> >> >> 2017-02-20 21:00 GMT+01:00 <[email protected]>: >> >> On 2017-02-07 18:27, Fernando D. Bozzo wrote: >>> >>> Hi Rick! >>>> <snipped> >>>> ...I think you should definetly take a look at FoxBin2Prg. It will make >>>> your team's (1 dev or more) life easier. >>>> >>>> We use it in 2 teams with 8+ people each one, and a LOT of merging of >>>> VCX >>>> and SCX every day, without problems. >>>> >>>> >>> >>> >>> Hi Fernando, >>> >>> Where do you hook this in? Are you integrating your VCS within the IDE >>> or >>> are you using the VCS's IDE to manually check in and out? >>> >>> Thanks, >>> --Mike >>> >>> [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cagq_jumfeidbm_cjvqcixe9b4ot8gsfcittyegyky3kooq7...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
