Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Source control
Message
De
17/02/2017 12:39:11
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
 
 
À
17/02/2017 12:25:32
Information générale
Forum:
Visual FoxPro
Catégorie:
Source Safe Control
Titre:
Divers
Thread ID:
01648065
Message ID:
01648086
Vues:
30
>I agree with your general rule on the project manager. It must be considered that the PJX is a development file too, and should be included in the checkin as every other VFP file.
>There is the option, too, of working just with text versions and regenerating the binaries when needed, but this approeach have the inconvenience that in every checkout you must regenerate all the binaries, which can be something heavy when the project have too many files.
>
>About the problem of the modified VCX/SCX files because of compiling them, the apporach to solve it is really simple: you just generate the text versions, if the text files are generated then there are code changes, if the text files are not generated, then there are not code changes, so in this case in the Pending Changes View of your SCM/DVCS tool you see some binaries without their respective text files, so you need to "undo changes" on those binaries (because there are no code changes), so you keep your changed files at a minimum.
>
>I'm using Source Control with VFP since middle 90's, so I did have a lot of time for testing different approaches, techniques and tools. I even colaborated with some optimizations on ScctextX, which later I've used to consolidate on FoxBin2Prg, which is what our VFP teams use for diffing and merging code every day.
>
>Many of the problems you describe are now resolved and minimized, thankfully :)

Actually the space and time are not a problem nowadays - most of the time it's not the source that's slow to bring over the wire, it's the databases. So space is not a concern, it's that switching to/from text representations has to be done from day one (or the day you pronounce so) and then every check in/out goes with text versions only, but. The trouble is that then it needs to be done in an automated fashion or it's more trouble than the current way. And that means writing my own client for whichever backend I'm using. Or, rather, writing a plugin, in VFP, which would call FoxBin2Prg this way or other whenever one of the binaries is checked in or out. I don't even know if any of the source controls allows for such a plugin - if it would, it would be worth it.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform