Greg Stein <gstein@lyra.org> writes:
> > 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.
The .texi design doc was updated about a month ago; it no longer
contains *wrong* information. It's simply been cut down to vague
generalities (which are still accurate) along with pointers that say
"read the header files". The biggest strike against the doc is that
it doesn't contain any details anymore. But it least it's not
misleading. :)
But a new developer should be able to figure out what's going on by
reading the spec, then reading headers in subversion/include/.
(Someday libsvn_fs/structure, svn_delta_edits_fns_t and other beasts
will be worked back into the design doc.) :)
> > 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.
>
Side note for GUI developers: one other major difference between SVN
and CVS is that SVN attaches "properties" to files and directories.
(Or Joerg, in your case, you can call it a "resource fork".) A good
GUI design will need to think about how a user might want to see or
edit these things.
Received on Sat Oct 21 14:36:15 2006