Home » Eclipse Projects » Eclipse Platform » [DataBinding] 3.3M6 - Where is BindSpec ?
| [DataBinding] 3.3M6 - Where is BindSpec ? [message #313754] |
Mon, 26 March 2007 09:19  |
Eclipse User |
|
|
|
Originally posted by: sf.tragwerk-dresden.de
I20070323-1616
After upgrading to 3.3M6 I got some complile errors at the missing classes
org.eclipse.core.databinding.BindSpec
org.eclipse.core.databinding.BindingEvent
org.eclipse.core.databinding.DefaultBindSpec
org.eclipse.core.databinding.IBindingListener
The JavaDoc is incosistent; while some of those classes are still
described in the package documentation of org.eclipse.core.databinding,
the classes above (and maybe others) are not listed.
Wasn't there an API-freeze for 3.3M5 ?
How can I convert my code ?
Are there more API-changes planned ?
Thank you.
Sebastian
|
|
| | | |
| Re: [DataBinding] 3.3M6 - Where is BindSpec ? [message #313800 is a reply to message #313771] |
Mon, 26 March 2007 11:03  |
| Eclipse User |
|
|
|
Hi Sebastian,
I know it's frustrating that we've had more than the usual number of API
changes over the last 3 weeks or so due to having a hard deadline of M6
for getting those changes in. Most of the changes were removing API we
weren't certain about and didn't want to commit to supporting forever.
But you can be assured that the API as it works now won't change. Where
there are JavaDoc discrepancies, these should be logged as bugs. Our
focus naturally has been on getting the API working and finalized. Now
our focus will be more on documentation.
Best regards,
Dave Orme
Sebastian Fuchs wrote:
> Thank you Tom,
>
> Most of all I'm confused, that there are so many propagated API-versions
> including examples, webinars and so on, which are all invalid 4 weeks
> later; while http://fire-change-event.blogspot.com, databinding-wiki nor
> this newsgroup do not tell about changes.
>
> Sebastian
>
>
>
> Tom Schindl schrieb:
>> Hi,
>>
>> The platform API freeze as describe by the Europa-Release-Plan was M6. I
>> think databinding wanted to target an earlier Milestone but had to
>> change some of the API because once it would have been published in M6
>> it would have to stay for ever and would make provoke problems when
>> evoling in the next releases.
>>
>> I cann't give you definite answer but as I know that M6 was the last
>> chance to modify public API you should be safe now although things can
>> always change until the final release of 3.3 is out of the doors.
>>
>> The change you are seeing is described in:
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=172193
>>
>> All API changes happened between M5 and M6 had to +1ed by the PMC so you
>> should find requests like this on the PMC mailing list.
>>
>> I found the following:
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=175418
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=172193
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=175840
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=162630
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=171906
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=177256
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=177684
>>
>> But I might have missed one and to get PMC approval there must have been
>> an entry in bugzilla so querying with M6 you should get the definitive
>> list of bugs.
>>
>> Tom
>>
>> Sebastian Fuchs schrieb:
>>> I20070323-1616
>>>
>>> After upgrading to 3.3M6 I got some complile errors at the missing
>>> classes
>>>
>>> org.eclipse.core.databinding.BindSpec
>>> org.eclipse.core.databinding.BindingEvent
>>> org.eclipse.core.databinding.DefaultBindSpec
>>> org.eclipse.core.databinding.IBindingListener
>>>
>>> The JavaDoc is incosistent; while some of those classes are still
>>> described in the package documentation of org.eclipse.core.databinding,
>>> the classes above (and maybe others) are not listed.
>>>
>>> Wasn't there an API-freeze for 3.3M5 ?
>>> How can I convert my code ?
>>> Are there more API-changes planned ?
>>>
>>> Thank you.
>>> Sebastian
>>
>>
--
Senior Consultant, Trainer
Coconut Palm Software, Inc.
http://www.coconut-palm-software.com
|
|
|
| Re: [DataBinding] 3.3M6 - Where is BindSpec ? [message #313802 is a reply to message #313771] |
Mon, 26 March 2007 11:05 |
| Eclipse User |
|
|
|
Sebastian Fuchs wrote:
> Thank you Tom,
>
> Most of all I'm confused, that there are so many propagated API-versions
> including examples, webinars and so on, which are all invalid 4 weeks
> later; while http://fire-change-event.blogspot.com, databinding-wiki nor
> this newsgroup do not tell about changes.
One last thing: the Eclipsecon examples should still be valid. At
least, I know they were done after the BindSpec removal Search the Wiki
or Eclipsezilla to find them.
If you have other specific questions, feel free to ask here.
Best regards,
Dave Orme
--
Senior Consultant, Trainer
Coconut Palm Software, Inc.
http://www.coconut-palm-software.com
|
|
| |
| Re: [DataBinding] 3.3M6 - Where is BindSpec ? [message #313838 is a reply to message #313804] |
Tue, 27 March 2007 03:31 |
| Eclipse User |
|
|
|
Originally posted by: sf.tragwerk-dresden.de
Thank all of you for your answers.
Databinding seems to be a very important tool not only for Form-Developers.
Maybe that's why some people, including me, work on the edge.
I agree that a stable and future oriented API is most important.
My only wish is a good documentation which describes the functionality
under the hood (IObservable, Pipeline, ...) and points out what
Convinience-classes exist (SWTObservable, BeansObservable, ...). So
every user should be able to answer even more complicated questions
himself, such as how to cascade comboboxes, validate over seperate
controls, reuse validators and so on.
Keep on the good work,
Sebastian
Brad Reynolds schrieb:
> All M6 API changes can be found with the following query. This is on
> the TODO[1] page on the wiki (although I probably wouldn't look there
> either).
>
> https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advan ced&short_desc_type=allwordssubstr&short_desc=%5BDat aBinding%5D&classification=Eclipse&product=Platform& amp;component=UI&target_milestone=3.3+M6&long_desc_t ype=allwordssubstr&long_desc=&bug_file_loc_type=allw ordssubstr&bug_file_loc=&status_whiteboard_type=allw ordssubstr&status_whiteboard=&keywords_type=allwords &keywords=api&bug_status=NEW&bug_status=ASSIGNED &bug_status=REOPENED&bug_status=RESOLVED&bug_sta tus=VERIFIED&bug_status=CLOSED&emailtype1=substring& amp;email1=&emailtype2=substring&email2=&bugidty pe=include&bug_id=&votes=&chfieldfrom=&chfie ldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+ same+sort+as+last+time&field0-0-0=noop&type0-0-0=noo p&value0-0-0=
>
>
> I apologize for not getting the information out sooner but we've been
> very busy.
>
> -brad
>
> [1] http://wiki.eclipse.org/index.php/JFace_Data_Binding_TODO
>
|
|
| | |
| Re: [DataBinding] 3.3M6 - Where is BindSpec ? [message #314447 is a reply to message #314438] |
Thu, 12 April 2007 17:25 |
| Eclipse User |
|
|
|
Brad Reynolds wrote:
> Partial validation was removed from the toolkit because we had quite a
> few doubts about it. It was only used for masking Text and having an
> abstraction for that one use case didn't make sense.
Yes, I agree with all of this. In fact, I was quite surprised to find it
in the API in the first place. But, unfortunately, now that our user has
already seen it in action... :)
> More information
> can be found in bug 169965[1]. The recommendation is that you create an
> observable that handles the masking and then bind it to your model.
Thank you, this is exactly the information I was looking for. I'll get
down to it...
> Overriding UpdateValueStrategy.doSet() won't do anything in regards to
> partial validation as this is invoked on every update. Also if the
> value was not able to be parsed or was invalid it would be caught by the
> "after get" validator and doSet() would not be invoked.
Immediately after I made the post, I realized that myself :) I was
really only hoping that the meaning of this method was "do the setting
of the value on the target (before starting the conversion and copying
to the model)".
Marko Topolnik, Ph.D.
CROZ d.o.o.
mtopolnik@croz.net
>
> Marko Topolnik wrote:
>> I was previously using DataBinding.setPartialTargetValidator, then
>> addTargetValidator(BindingEvent.PIPELINE_VALUE_CHANGING), but now with
>> the UpdateValueStrategy the whole partial validation thing is gone.
>>
>> Does that mean that now I need to override UpdateValueStrategy.doSet
>> in order to reintroduce the partial target validation semantics, or is
>> this supported in the new API after all? If it is, could someone
>> please point me in the right direction?
>>
>>
>> Marko Topolnik, Ph.D.
>> CROZ d.o.o.
>> mtopolnik@croz.net
>>
|
|
|
Goto Forum:
Current Time: Tue Oct 28 12:47:59 EDT 2025
Powered by FUDForum. Page generated in 0.17681 seconds |
Home