Re: [nebula-dev] Re: one plugin per control

[Christopher J Gross <chris.gross@xxxxxxxxxx>]

Comments inline...

nebula-dev-bounces@xxxxxxxxxxx wrote on 12/21/2006
02:27:11 PM:

> Are we talking about packaging widgets, or the structure of CVS?  Should
> these be the same?
> 
I think we are kinda talking about both
the structure of the projects and the packaging.  I think its all
related.

> 
> I guess I am not officially a committer yet, but I really like 1 zip
per 
> control.  I think we could then take a poll of who wants to be
in a 
> release (we have sort of already done this), and these could all be
> packaged up as a Nebula release (we can export a bunch of plugins
as a 
> Zip).  Then if someone wants to try out all the widgets they
can do this.

One zip that includes all the plugins
is a good idea.  I like that idea better than one plugin with all
the code.

> I'm not sure if we have decided on how to go with JFace style widgets,
> that is if a widget is available in two different forms.  Is
this two 
> different plugins (one that depends on another) or just 1 and you
can 
> access it in either way? If we go with the second approach then we
have:
> 
> org.eclipse.nebula.grid
> org.eclipse.nebula.ctabletree
> org.eclipse.nebula.compositetable
> org.eclipse.nebula.pgroup
> org.eclipse.nebula.pshelf
> org.eclipse.nebula.graph (zest graph)
> 
> However this doesn't help if and when we move to SWT, since the JFace
> and SWT parts must be separated then.  Although I guess if we
forced 
> package conventions within the plugins (SWT and JFace must be in 
> separate packages and the SWT package must not have eclipse.ui 
> dependencies this would work).
> 
> Cheers,
> Ian

Two different plugins that depend on each other.  So
for example, for Grid we would have
org.eclipse.swt.nebula.grid (only depends on SWT)
org.eclipse.swt.nebula.nebface.grid (depends on SWT,
the grid plugin and JFace)

The idea is to make the widgets available the same
way normal SWT widgets are available.  As either the base widget with
a simpler API, or wrapped by a viewer.  


-Chris