Re: scheduling, and gui clients (Win, Mac)

>You'll hear "Mac Mac Mac" if people say it. :-) It isn't that anybody is

OK, that's easy then: Mac Mac Mac 8-)

>Now... without seeing MacCVSClient, I'll just say that if it bears any
>resemblance to WinCVS, then I'd be disappointed to see it carry over into
>SVN land. See my earlier comments about the user model / UI of WinCVS and
>how it is sadly mistaken for a Good UI(tm) for a versioning system.

MacCVSClient is *SUBSTANTIALLY* different. What can I say,
I love it! 8-) I am sure there are things here that could do
with clean up (your example of the status command output
is a good one; that goes onto the "console" window in
MacCVSClient as well; shame on me; the reason for this,
though, is that I NEVER EVER use it; and nobody has complained
about it yet. ;-) Anyway, I don't want to bore you with
non-SVN blurb.

>I haven't seen it, so I can't really be a good judge.
>
>I'd think that you might be able to share some "pure" GUI points. But the

Yeah, thought about it again, and you're probably right
in that sharing source code will probably be limited to
GUI related code.

>"real" code, the code that does the work, couldn't really be shared. I have

Probably needn't either: the protocol is implemented and
it should "just" be a matter of porting it and getting it
to run. Then the SVN part that reads a working copy and
holds all its information should be usable as well. These
two modules have direct counterparts that I did myself for
MacCVSClient => replace. Now there is the code left that
parses CVS output (e.g. log and diff), which needs to be
rewritten.

What's left is the GUI. *IF* the user models match closely
enogh. In that case, it would be a starting point after all.

In a way it's like you guys having the SVN command line
accept the same kind of commands and arguments as CVS.
Easy transistion for CVS victims.

Cheers,
Joerg

-- 
They can take away my Mac when they pry
my cold, dead fingers from my mouse.