Ross Gardler wrote: > > I think you are right, the Java API is probably best. > > So does all this mean that we have something like: > > package org.apache.forrest.view > > /** > * A tree navigator that displays the contents of a repository > */ > public class RepositoryNavigator > > --- > > package org.apache.forrest.repository > > > /** > * An interface describing the methods required to interface with > * and interact with an external repository. > */ > public class IRepositoryConnection > > /** > * A content provider that presents the content of a repository > * to a graphical widget for display. > */ > public class RepositoryContentProvider implements > IStructuredContentProvider > > > /** > * A label provider that provides labels for the content of a > * repository for display in a treeView. > */ > public class RepositoryLabelProvider extends LabelProvider implements > ITreeLabelProvider > > --- > > package org.daisy.forrest.repository; > > /** > * An implementation of a connection to a Daisy Repository > */ > public class RepositoryConnection implements > IRepositoryConnection > > --- > > The RepositoryConnection can do all the communicating with the > repository as you suggest. It would provide instances of the content > and label providers for the view. > > --- > > Does this fit with what you were planning? > That was the general idea I had. Thanks for refining it bit for me.
Anil.
