Robert, I've been playing with this a little. Prety cool except if I put the $Log$ in the root comment tag of a taf, it corrupts the taf file with extra <Comment> tags. A way to get around this is to put in a blank line before the $Log$. Then it works no problem. What I think is useful about this, is that you can put these inside <@assign> tags and use them to display information from your application at runtime.
Mike "Robert S. Sfeir" wrote: > > Ok some might already know this, but I found this so useful today that I > thought I would post it. > > If you're using CVS, or Source Safe for that matter, there are variables > available to each of those repositories which you can use within the TCF and > TAF files to keep track of various things. > > Here is a list I find useful: > > $Author$ The login name of the user who checked in the revision. > > $Date$ The date and time (UTC) the revision was checked in. > > $Revision$ The revision number assigned to the revision. > > $Log$ The log message supplied during commit, preceded by a header > containing the RCS filename, the revision number, the author, and the > date (UTC). Existing log messages are not replaced. Instead, the new log > message is inserted after $Log:...$. Each new line is prefixed with the > same string which precedes the $Log keyword. > > To use this, simply put the variable where you find it appropriate in your > TAF and TCF files. For example, in the ROOT comment of the TAF and TCF file > name (all the way at the top of the TAF file there is an icon representing > the taf with the name of it. ) Get properties or info on that and switch to > the comment tab and type in $Log$. Then switch to the first tab and under > version type $Revision$, and under Author $Author$, but keep in mind that > the Author will changed based on who checked it in last. After you do this, > check your file in, and see what happens. You might have to close and open > the file to see the updated info. > > I always had an issue with the fact that these fields have been made > available to us for such a long time, but we never got a way to 'auto > update' at least the version number we had to do it manually, and come on > we're all engineers and we're lazy and we don't keep up with that. However > if you use version control, there you go, auto updated fields as you check > files in, and what's more, the comment field is now very useful since you > will have a log of what changes were made to your taf and tcf files without > having to go get a history of the file from CVS or any other repository you > use... Heck that alone should be a good reason to use CVS with WiTango. > > Hope this helps. > R > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body -- Mike Tyranski Lynch2 p: 847.608.6900 f: 847.608.9501 http://www.lynch2.com ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
