Re: jCVS Swing Port (was: jCVS version using Swing UI available)

[time@ice.com]

> I imagine that when you say that the Swing version of jCVS would be a separate app.  You
> mean that the two versions would only differ in the UI files?

What I mean is that there would be 'com.ice.cvsc', 'cvs.ice.jcvs', and a new
package, say 'com.ice.swingcvs'. Thus, the swing ui developement and awt ui
development could exist in parallel, each producing a separate application,
while the client protocol layer (which is 'com.ice.cvsc') remains as the kernel
of both applications.

I already have plans for a simple scripting language (based loosely on the
command specs now used to configure jCVS) that will allow me to do some
simple scripting of cvs commands. This would be yet another package.

> Out of curiosity how many people are expressing an interest in modifying jCVS?
> I wondering
 so estimate how often the source will be changing.

Well, I have some modifications sent to me a long time ago that I have never
manged to integrate. I simply have not had the time and the modifications were
to a very old release. I have three or four others who have expressed an
interest in making some changes or enhancements. And now, Erwin has indicated
that he has ported jCVS to Swing. One other individual wanted to propose the
Swing port  for some sort of grant, but decided to wait on my 5.0 release.

tim.
Tim Endres, ICE Engineering, Inc.
   mailto: time@ice.com    http://www.ice.com
   "Usenet - A slow moving self parody." -- Peter Honeyman