Alexander Mueller <alex@littleblue.de> writes:
> > I think this is the point of the SWIG bindings that are being
> > currently developed in the Subversion source tree already.
>
> Hmmm. Do you know a shortcut for me to find them to check out?
Heh...I wish I did. If you look in subversion/subversion/bindings,
that's the workspace for those bindings. I just took a glance, and
realized just how little is actually present there. If you're
interested in pushing through on the lowest-level stuff, I'd recommend
butting heads with Greg Stein (gstein@lyra.org) to determine what
needs to be done there.
> > Heh. Saying things like "Functions maybe like WinCVS" might get you
> > beheaded by some of our list followers. :-) I like the idea of using
> > Swing -- in fact, I (at least initially) like any idea that will earn
> > us a GUI that not just behaves the same on all supported platforms,
> > but *looks* the same as well.
>
> In fact, I dont want it to behave exactly like WinCVS. Most of
> all of the other CVS GUI frontends (jCVS, SmartCVS, LinCvs, WinCvs)
> try an approach thats is too technical for the end user. I really
> love the command line, but well you see too much of the dirty details...
I agree fully. An example of an interface that provides a fairly
decent balance of functionality vs. user-friendliness (IMO) is that of
Visual SourceSafe. I'm not familiar with many other VC frontends, but
that one was my first VC GUI, and was pretty easy to get a grasp on,
as well as to use once I fully understood what was going on under the
hood.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:33 2006