| Creating Team Repository Provider that delegates to other Providers [message #463856] |
Fri, 16 February 2007 18:26 |
Eclipse User |
|
|
|
Hello everyone,
We've got an RCP application with our own custom Project View and we're
trying to add source control to it. We'd like to support a few of the
common source control systems such as CVS, SVN and Perforce so customers
aren't tied to a particular system. However, rather than exposing the
UI of these plugins, we also would like to maintain as much control over
the UI as possible. We want to keep it as simple as possible for our
non-technical users. Ideally we'd provide all of the commmon source
control UI and delegate the functionality to the other source control
plugins.
After reading through the Team documentation, we're considering creating
our own Repository Provider that would delegate to other Repository
Providers as needed. We would like our application to handle most of
the work of marking files for source control add, edit and delete
through user initiated app-specific actions.
It seems like it would be possible but does anyone have experience
regarding this approach or suggestions for an alternate approach?
Thanks in advance,
Dave
|
|
|
Powered by
FUDForum. Page generated in 0.02921 seconds
Home