On Thu, Nov 23, 2000 at 02:01:27PM +0800, Joerg Bullmann wrote:
> Hi all,
>
> I just hear Windows Windows Windows. What about the
> Mac? 8-) Is there anybody here interested? I had been
You'll hear "Mac Mac Mac" if people say it. :-) It isn't that anybody is
/not/ interested, it is simply that people scratch their own itches.
Eventually, somebody such as yourself, or Fred or somebody, will come along
and say "damn it. I want a Mac client!" and go code one :-)
> lurking and looking what's going in terms of clients,
> but am far from sure I understand the client lib and
> all its architecture (e.g. baton etc.). [ an aside:
> How is the architectural description (the subversion
> TeX doc) going? Any updates there? ]
Nope. Probably not until we're done. The current stuff in there is just a
bit too out of whack. If we were to go and update it again, then we'd just
suffer the chance that we'd need to rewrite it a third time. Heck, I JimB
just checked in two major rewrites of libsvn_fs/structure today.
> In the beginning of SVN I had wondered how much work
> it would be to use MacCVSClient as a base for a
> MacSVNClient.
Maybe some of the GUI features, but certainly none of the actual code to
interact with the working copy or the repository.
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.
>...
> Many of MacCVSClient's features (context diff, hierarchical
> log lists, and stuff like that) are currently based
> on the CVS server output (parse diff or log output)
> and would probably need major rework.
Definitely.
> I still wonder,
> though, whether it would be possible (and feasible)
> to unify both (CVS and SVN) and have the two clients
> share lots of existing code.
Urk. I'll give my own opinion (dunno whether this is shared or not), but I
would be rather vehemently against CVS interop / shared code within the
subversion code base. I'm just not up for the pollution and maintenance
headaches that would entail. My answer to people that want to try that: SVN
is so much better, that you'll spend less time upgrading your CVS repository
and using SVN, than you would in trying to get the two to work together.
> Now, before I get too wound up here (also have got
> a good list of MacCVSClient on the plate), could
> others please tell whether they would support
> that.
"that" meaning sharing code? If it was in a client, then it is no skin off
my bakc. Do whatever. But see above if the code will sit in SVN itself :-)
> Do you think MacCVSClient is a good base
> or would you rather start afresh? I'm just tossing
> the idea in here and haven't thought through many
> details myself.
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
"real" code, the code that does the work, couldn't really be shared. I have
to imagine that would save you time, but it isn't going to provide a ton of
leverage. And if you need to revamp the GUI to a cleaner model? May as well
not try to share any of it. (judicious stealing of code is always fine, but
to expend effort to attempt to share code when it isn't justified is another
matter...)
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:15 2006