Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » Using remote source within workspace projects
Using remote source within workspace projects [message #267170] Mon, 16 August 2004 16:35
Eclipse UserFriend
Originally posted by: kevin.brock.fullscope.com

I am working on a project where we must store our source on a central
server and have an eclipse plug-in that contacts this server to read/write
files as well as execute remote utility programs. I've written the server
portion and inter-process communication protocols but am fairly new to
writing eclipse plugins. I've done a lot of research through the help,
on-line faqs, this forum, and read through a lot of source (though with
the size of eclipse, there is a lot to read and understand).

I was taking the approach to build my own views ... and even have a crude
prototype working (a basic tree and viewing files in an appropriate editor
using IStorageInput; but that doesn't allow saving; I understand though
that I could build IDocumentProvider framework to handle that issue
though). This will probably work but during my research I realized that
the eclipse standard workspace really provides a lot of functionality with
it's internal tree structure, delta changes, and the standard extension
points. I would prefer not to reimplement all that code base but also
want to adhere to the API rules for well-behaved plugins...so will not be
extending or implementing any "internal" items or those docuemented to not
be implements (e.g. IFile).

Today I encountered more information on IAdaptable and IAdaptableFactor
and am now wondering again if it's possible to actually use the workspace
tree since I think I can use these interfaces and the adapter factory
registry to link my custom resource classes to the workspace tree elements
(seen something like this in the eclipse JDT).

The real trick here is that there will be few if any local physical
resources -- folders and files. These actually reside on the server.
Does anyone know if this may be a good approach or should I just stick
with implementing my own tree view (as I have started) and live with the
lost functionality? Or perhaps there might be a better way to implement?

--Kevin Brock
Previous Topic:EclipseClassLoader info
Next Topic:Problem with sharing an external JAR among plugins...
Goto Forum:
  


Current Time: Mon Sep 15 22:20:20 EDT 2025

Powered by FUDForum. Page generated in 0.05299 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top