| approach to team implementation [message #186689] |
Thu, 29 January 2004 12:02 |
Eclipse User |
|
|
|
Our application is used in a team environment where designers use our
framework built on top of Eclipse. Sharing files is an integral part of
our framework. However, they aren't sharing source code like a developer,
but sharing design files (XML, custom files, proprietery files, etc)
geared to our application.
The Eclipse support of CVS (CVS client) is a great feature and a bunch of
the built in features like branching, versioning, compare, the synch view
are all beneficial to our requirements. However, what we would like to do
is create a hybrid solution and simplify the UI. Our typical user is not
from a development background and would be more comfortable with a watered
down UI from what the CVS client provides.
So, I'm looking for a good way to go about this. We don't necessarily
want to create our own repo provider as the CVS client implementation
already provides much of the functionality, what we really want to achieve
is creation of our own UI elements that minimizes what the user can do (we
don't need all the CVS client features) and gears these UI elements
towards our lingo but still can leverage the built in CVS framework
already provided.
I have looked at the file system repo provider example. While that is a
good start to creating your own, we would wind up having to build so much
into it that the CVS client already has, it wouldn't be worth the effort.
thanks
|
|
|
Powered by
FUDForum. Page generated in 0.03454 seconds
Home