Re: [nebula-dev] Support for Eclipse Data Binding

[Roland Tepp <roland@xxxxxxxxxxxx>]

I'm not a committer either, but here are my 2 cents:
First - the separation of plug-in per widget is good for Nebula because 
I find that I often want to include just one or the other widget and 
don't want to clutter my classpath with others unless I so choose to.

Maybe You could have a build scipt that would generate 2 variants of 
plug-in(s) - one "jumbo" plug-in that contains the whole soup and one 
that builds separate plug-ins per widget.

So that those who just want the "nebula widgets", would pick the whole 
thing, but those who want to pick and select, can do that as well...

Tom Schindl kirjutas mulle  midagi seesugust:
> Hi,
>
> I'm not a commiter but my feelings are:
>
> - nebbinding +1
> - one plugin / widget -/+0 although I'm more against
>
> What would be when you group widgets:
> - org.eclipse.nebula.table
> - org.eclipse.nebula.text
> - ...
>
> You need some top-level plugins which hold things shared by different
> plugins. Create a seperate plugin / control would be the same as if SWT
> would provide a seperate plugin for each of it's widgets.
>
> Tom
>   

--
 Roland Tepp

begin:vcard
fn:Roland Tepp
n:Tepp;Roland
org:Videobet
adr:;;;Tallinn;;;Estonia
email;internet:roland@xxxxxxxxxxxx
title:Software Developer
x-mozilla-html:FALSE
url:http://www.videobet.com/
version:2.1
end:vcard