[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.platform] Re: Using databinding 3.3 api in 3.2 codebase application

Well, first because I was told not to :)

The basic reason being that if I move *now*, I'll have to port stuff that we've already have using 3.2 databinding *now* as well, which is currently although not a huge undertaking in itself, still a work that keeps me from doing some "constructive" work.

Considering that the application is not expected to grow too much in the foreseeable short-term future, and we have migration of the whole application to Eclipse 3.3 shortly after its release already planned, it is not worth the extra trouble quite right now...

Thanks for supporting me though :)

Tom Schindl kirjutas mulle midagi seesugust:
Hi,

I don't understand why you are stuck with 3.2 databinding the CVS-Tree
is *compatible with 3.2*. The only thing that is not possible is to use
the databinding libs that ship with 3.3 because of the fact I outlined
below.

Tom

Roland Tepp schrieb:
Thanks.

It still looks like I'm stuck with 3.2 databinding for the time being...



Tom Schindl kirjutas mulle midagi seesugust:
Hi,

As I understand it now the databinding plugins shipped with Eclipse are
not binary compatible with 3.2 API
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=177476) because the
java-compiler is adding references to classes only available since 3.3
although only 3.2 API is used. So you need to checkout the sources from
CVS in a 3.2 env and build them your own. When developing a RCP this
isn't really a problem because when exporting the product eclispe is
packaging everything for you.

Tom

Roland Tepp schrieb:
Hello,

For various reasons I am developing (not entirely an RCP) application
based on Eclipse 3.2 code base and I am considering using the Eclipse
Data Binding for, well, binding data to SWT widgets...

From another ng. I read that it is much recommended to use new 3.3 API
instead of 3.2 as these two are quite a bit different and porting from
one to another is a frustrating ant time consuming if not difficult
undertaking.

So the question to this ng.: Can I use eclipse databinding api/plug-ins
from 3.3 branch side by side with 3.2 based SWT and other plug-ins...

If yes - can I download the 3.3 data binding plug ins as a separate
download from somewhere or must I hand-pick any plug-ins that have
"databinding" in their names from the latest stable 3.3 eclipse build?




-- Roland Tepp