On Feb 12, 2007, at 4:51 PM, [EMAIL PROTECTED] wrote:
On Feb 12, 2007, at 23:04 UTC, Tim Jones wrote:
I haven't tried it yet with the new version control format, but I
have
successfully used the XML format with svn for a long time.
TheXML version is tough to parse with large projects because the
ENTIRE project is one large file.
What? Not in my projects, it isn't. I make every project item
into an
external XML file. Version control would be pretty useless with it
otherwise.
And therein lies the secret - make each element external and then
export them as XML. I'll agree that this will work, but it's a lot
of work compared to what VCP is "supposed" to provide. I'll look at
making each element external, but even mys smallest project is 12
windows and 8 modules.
So here's what I suspect I'll need to do:
Create a new Project Folder
Step through each Menu, Window, Class and Module and export them
INTO that folder as CML
Create a new project and Option-Drag each of the exported elements
back into the project
Save the project as XML in that same folder
Does that cover it or have I missed something?
Oh well, I relly didn;t want to watch Discovery channel tonight,
anyway :). Thanks for that explanation.
I've already done that and I do get the proper line breaks displayed,
but the issue is on the server side when the a diff mode call is
made. The result is that the entire file has changed.
Right, this still doesn't make sense to me unless you're either
sharing
development with users on other platforms, or your server is
misconfigured. You should ask about this on a subversion forum or
mailing list; I bet they have an easy answer. Basically, I think you
want to set your svn repository to leave the line endings intact, and
you currently have it set to convert them.
Accordingly, based upon feedback from an svn forum, I set up a local
repository that doesn't involve the server and I get the same
results. Without the svn:eol-style=native for each of the VCP file
types, an svn diff results in the files being displayed with the ^M
characters and as one long line. With the conf changes, the lines
are split, but one entry change still results as the entire file
being displayed as the diff.
That's exactly the problem - it's not. The VCP files are all written
out with the Mac CR EOL. That's what the feature request was for:
http://www.realsoftware.com/feedback/viewreport.php?
reportid=ppxkfpqm
Yes, I agree that would be better, but you should be able to work
around its lack (except in a mixed-platform environment) with svn.
Still searching for how.
Tim
--
Tim Jones
[EMAIL PROTECTED]
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
