davoli@natinst.com (Russell Davoli) (03/15/90)
A while back, I asked for any information anyone might have for a source code control system other than Projector. Well, the only response I got was for MacSRMS, but it seems that Quilt has disappeared (they don't answer their phone at least) and APDA doesn't carry MacSRMS anymore. I can live with Projector, but now I'm wondering: 1. Is Symantec ever planning to fix THINK C's editor so that it doesn't get rid of the Projector resources when a file is saved? 2. If no plans for 1, is there anything else out there used for source code control with THINK C? I'd really like to avoid the trouble of using MPW scripts to save the Projector resources and provide a temporary copy of a file to edit with THINK C, then add the resources back when I'm checking the file back in. Any info will be greatly appreciated. ------------------------------------------------------------------------ Russell Davoli Software Engineer National Instruments davoli@natinst.com
siegel@endor.harvard.edu (Rich Siegel) (03/15/90)
In article <8461@natinst.natinst.com> davoli@natinst.com (Russell Davoli) writes: > >1. Is Symantec ever planning to fix THINK C's editor so that it doesn't > get rid of the Projector resources when a file is saved? THINK C 4.0 doesn't smash the resource fork of a file anymore, in response to this request. ~~~~~~~~~~~~~~~ Rich Siegel Staff Software Developer Symantec Corporation, Language Products Group Internet: siegel@endor.harvard.edu UUCP: ..harvard!endor!siegel "When someone who makes four hundred and fifty dollars an hour wants to tell you something for free, it's a good idea to listen." ~~~~~~~~~~~~~~~
michelr@xstor.UUCP (Michel Rynderman) (03/16/90)
In article <8461@natinst.natinst.com> davoli@natinst.com (Russell Davoli) writes: >A while back, I asked for any information anyone might have for a source >code control system other than Projector. Well, the only response I got There is PVCS from polytron I think. It works under MPW. It is an exact port of their stuff on the PC. I had for 30 days and then returned it. They charge approx. $300 and the manual has a couple of pages to do with the Mac. The rest was PC stuff. Other people in my office use it on the PC and don't think much of it. ------------------------------------------------------------------------------ Michel Rynderman | uunet!xstor!michelr Storage Dimensions, Inc. | 2145 Hamilton Ave. | San Jose Ca. 95125 | (408) 879-0300 | ------------------------------------------------------------------------------
ts@cup.portal.com (Tim W Smith) (03/18/90)
Here's what I would like to see Think C do: 1. When a file is opened ( either by the editor, or because the compiler needs to read it ), Think C would look for a resource of type 'SCCS'. 2. The 'SCCS' resource would contain a function that Think C would call, passing in the name of the file. The 'SCCS' resource would return a file name that Think C would open to get the contents of the file. 3. Think C would remember in the project file both the original file name and the name returned by the 'SCCS' code. It only does the name translation when a file is first opened. 4. There would be an item under the File menu that causes Think C to invoke the 'SCCS' code with an argument indicating that the file has been updated and the changes are to saved. 5. The 'SCCS' resource would normally be in the project file, although Think C would look first in the source file. I haven't worked out all the details of the above. The basic idea is for Think C to NOT know about the details of source code control. This is up the the author of the 'SCCS' resource. Third parties could write 'SCCS' resources that understand particular source code control systems. For example, if one of your source files was on your Unix machine, which is connected to your Mac by a serial port, you could have a dummy source file on the Mac that contains an 'SCCS' resource that knows how to login to the Unix machine, "get" the file, and download the "get"ed file to the Mac. This also would have a big advantage for Symantec. Source code control systems are like editors: the one I use is great; the one you use sucks! This way, if you don't like the source code control Think provides, use another one! Tim Smith