> > Alexander Mueller <alex@littleblue.de> writes:
> >
> > > Thought a lot about implementing the java interface using JNI oder
> > > the command line interface.
> >
> > I, too, have been considering Java/JNI as the interface of choice.
> >
> > > * low level: wrapper interface using JNI. just to get the
> > > interconnection between java and the c api. no extra
> > > functionality. would be great if generated automatically out the
> > > svn_client.h or whatever meta description
> >
> > 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?
>
> > > * medium level: some fine java classes that implement higher
> > > levels of abstraction like having it dont with a
> > > model-view-controller like this
> >
> > Okey dokey.
> >
> > > * highest level: the gui. Using Swing components for
> > > display. Functions maybe like WinCVS
> >
> > 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 don't know if you have access to an OPENSTEP or Mac OS X box, but
CVL is, in my opinion, the most usable of the myriad of GUIs out there
for CVS.
http://www.sente.ch/software/cvl/
-Fitz
---------------------------------------------------------------------
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