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

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

Re: shared things, thats actually something
we are trying to avoid.  If any of the widgets want to be included
in SWT, they should try to have as little dependencies as possible.  So
we are trying to avoid sharing classes across widgets.  So this will
actually be a boon to that effort.

Tom Schindl <listom@xxxxxxxxxxxxxxx>
Sent by: nebula-dev-bounces@xxxxxxxxxxx

12/20/2006 02:03 PM

Please respond to
Nebula Dev <nebula-dev@xxxxxxxxxxx>

To	Nebula Dev <nebula-dev@xxxxxxxxxxx>
cc
Subject	Re: [nebula-dev] Support for Eclipse Data Binding

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

Chris Gross schrieb:
> Sorry Dave, forgot to respond to this.
> 
> Yes I think we should have a separate nebbinding (or maybe just
> nebula.binding?).  This also brings up another thought I've had.
 We
> should really separate our widgets into separate plugin projects.
 Right
> now, we are just creating separate jars but using the same project.
 I
> did this originally so we could ensure that everyone was using the
same
> set of dependencies.  But this makes it difficult for developers
to use
> our widget in Eclipse applications.  It would make much more
sense have
> each widget constitute its own plugin.  This would also mean
that any
> additional facilities for each widget (viewers, databinding support,etc)
> would also have to be separate plugins.  I think this makes sense.
> 
> What does everyone else think?
> 
> -Chris
> 
> David J. Orme wrote:
>> All,
>>
>> With Eclipse 3.3 comes official API support for Eclipse Data Binding.
>> I'd like CompositeTable to support this API along with the JFace
>> Viewer API.  We have the NebFace project for JFace viewers,
should we
>> create a NebBinding project for Data Binding support?
>>
>>
>> Regards,
>>
>> Dave Orme
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> nebula-dev mailing list
>> nebula-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>>   
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev

_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev