Paul McNett wrote:
> Carl Karsten wrote:
>
>> Thanks for the auto adding suggestions. It seems that even with some
>> code, auto ADDing isn't exactly auto.
>
>
> I think that auto-adding isn't a good idea. You want to explicitly add
> things to your repository. Just IMO. With a proper setup of the file
> skeletons to ignore, combined with a judicious use of 'svn status', you
> should get into the swing of seeing and dealing with the remaining ?'s.
>
> How many new files get added to a repository once it is set up anyway?
> And why wouldn't you know about those new files and remember to add them?
Not very many, and that is the problem. If I only add files once a
month, then I won't get into the swing of things any time soon.
>
>
>> So Plan B: use the VFP project to define what gets added. Vfp meny,
>> Tools, Options, Projects, Source control options, Active Source
>> Control Provider. Any idea how to get subversion to be a choice?
>
>
> Has VFP's integrated source control gotten way better over the past
> couple years? It totally blew chunks in VFP7 at least, slowing me down,
> corrupting my VCX's, not keeping me in the loop as to what is actually
> happening, etc. Then again, that may have been more of a SourceSafe
> issue, and SourceSafe is a product that, well, sucks and blows at the
> same time! :) (no offense to Ted who wrote an excellent book about VSS
> and set me on the path that eventually led me to Subversion!)
Does the book document what is needed to be used by VFP?
>
>
>> Plan C: Project hooks. Anyone know where a project hook class is
>> that does any sort of source control? even it it isn't subversion,
>> seems like it would be a good place to start.
>
>
> Do you know about scX? It doesn't provide the source control, but does
> provide a project hook that converts VFP binary formats back and forth
> to text renditions that you save to source control. So, instead of
> saving mylibrary.vcx and mylibrary.VCT to Subversion, you'd instead save
> mylibrary.vcx.sc, which is a plain-text format that can be diff'd and
> merged.
>
> http://paulmcnett.com/scX.php
Um, project hook?
I looked it over briefly, and have a 'simple' request: a line or 2 of
comments that explains what it does. Maybe another line describing the
parameters. ;)
README says that I need to open the project with "DO scProject WITH
(your project name)" - given that I am a VFEite, which somehow opens the
pjx for me, I have a problem. Ideas?
>
>
>> I made a nifty util that will be cool if I can tie in:
>> http://fox.wikis.com/wc.dll?Wiki~VcxDiff
>
>
> This does seem cool!
Any idea how I can deal with method code better? for openers, a better
way of displaying the whole method code, and ultimately a line by line diff.
Carl K
©2004 Carl Karsten |
