When it comes to CVS, it will attempt to merge their changes, using some sort of line-by-line analysis of their code. If they each manipulated different functions, for example, they are in the clear. If their changes overlap, they end up having to reconcile, they curse each other out, and learn to do a better job of checkin / checkout. There are a bunch of options in different systems, but in the end none of them replace good project management, and nothing can do a magical merge.
Your system worked down to an object/script level might not be all that far away from rudimentary CVS.
99% of VC is more intimidating than complicated, IMO.
If nothing else, if one of the goals here (which I'm on the fence about, actually) is to win over the enterprise / "professional" market, adding a per-object / per-script versioning tool natively into the IDE might impress a few people.
Is there any RAD tool out there that does version control now???
- Brian
For a VC system, I'm unclear on whether you allow multiple people to edit
the same object at the same time. If yes, how do you account for the
revisions being posted for the same object by different developers? If Judy
and John want to check out/edit the script of btn A, and both provide
*different* script options, how do you determine the version for each edit,
especially if the scripts are then re-edited later? What would the desired
behavior be here?
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
