RE: Proposal (AW: [ jEdit-users ] Version Management Plugin)

[Travis B. <tr...@in...>]

There is java code for managing CVS.  I wonder how hard it would be to port
it over to a plugin.

Travis Bauer
Graduate Student, Indiana University
http://www.cs.indiana.edu/~trbauer

-----Original Message-----
From: jed...@li...
[mailto:jed...@li...]On Behalf Of Maik Schreiber
Sent: Friday, October 19, 2001 11:27 AM
To: jed...@li...
Subject: Proposal (AW: [ jEdit-users ] Version Management Plugin)


>I kinda vote for some a bit more generic.  Such that CVS or
>SourceIntegrity or whatever could be plugged in.

I think we should really concentrate on developing a kind of SAL
(software abstraction layer) where any kind of version management
control (VMC) implementation can be plugged in to.


So far I see about three types of different VMC implementations (types
are quite analogous to JDBC driver types):

Type 1 - SCC bridge. This implementation employs the SCC DLL interface
from Microsoft. This needs a single direct VMC implementation that uses
the DLL and delegates all actions to it and the drivers available to it
(all transparently handled by the DLL). Because of the very nature of
this implementation, this would only run on Windows at this time.

Type 2 - Native API; partly Java. This implementation uses JNI directly
to talk to various shared libraries or other tools to accomplish the
task. This does not necessarily mean that it doesn't run on all
platforms, but it could.

Type 3 - Direct; pure Java. The last implementation type uses only Java
to do things. It would speak to servers directly over sockets or other
things (depending on implementation).


I think all these different types can be handled transparently by a
single VMC plugin that has various action methods which are then
delegated to a particular VMC implementation module.

Since I don't know each and every VMC system (only CVS, RCS and
SourceSafe), I'll try to propose a first generic API for the VMC plugin
here that should be most suitable for almost all VMC systems.

The first type of actions should be server-dependant:

- login
- logout
- get status (?)
- select repository/module/... (?)

The second group will operate on single files as well as directories:

- check in, retaining lock yes/no
- check out, acquire lock yes/no
- log
- diff
- get status


Note that not all VMC systems provide all of these actions, so that is
why the VMC plugin has to determine which actions are available. As a
result, certain menu items or context menu items must be grayed-out or
simply not be displayed at all, so the user cannot accidentally invoke
non-implemented features.


I'd like to encourage all users of VMC systems to add comments and
thoughts about this (quite simple actually) proposal.

--
Maik Schreiber
IQ Computing - http://www.iq-computing.de
mailto: in...@iq...


--
-----------------------------------------------
jEdit Users' List
jEd...@li...
https://lists.sourceforge.net/lists/listinfo/jedit-users