|
|
|
|
|
|
|
| Re: EMFObservables Provisional Status [message #528387 is a reply to message #528342] |
Tue, 20 April 2010 10:52   |
 Ed Merks
Messages: 33142
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------090001010602060007080901
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Tom,
One might argue that given it's provisional API we might consider
directly deprecating it now and that we'd be within the bounds of
expected behavior to remove it entirely, though doing that after M6
seems bad.
Tom Schindl wrote:
> Hi Enrico,
>
> I can think that we'd probably deprecate and remove in a timeframe of
> some releases (as specified by the Eclipse API Deprecation guidelines)
> but we naturally know that many people are using the Observables-API and
> so we'll support it with bugfixes *but won't* add new features (e.g.
> support for ObservableSets was only added to the Properties-API).
>
> So though there's no immediate reason to switch over to Properties
> (beside that doing this with 3.5.2 reveals a performance problem fixed
> in 3.6.0) I'd think about switching over to Properties with the Helios
> release of Eclipse- and EMF-Databinding.
>
> Tom
>
> Am 20.04.10 09:56, schrieb Enrico Schnepel:
>
>> Whats the difference between the Properties and Observables APIs? Up to now
>> I have used the Observables API. Shall I switch for current/future projects?
>> Will the Observables support be removed in future version or marked as
>> deprecated?
>>
>> Enrico
>>
>> "Tom Schindl" <tom.schindl@bestsolution.at> schrieb im Newsbeitrag
>> news:hqie49$5t0$1@build.eclipse.org...
>>
>>> Hi,
>>>
>>> EMFProperties and EMFEditProperties is the thing you want and it's part
>>> of EMF-Databinding since the last release.
>>>
>>> We'll add features to the Properties API in future and not to
>>> EMFObservables because we get direct support for this from upstream
>>> (Eclipse-Databinding).
>>>
>>> Tom
>>>
>>> Am 19.04.10 22:20, schrieb Nick:
>>>
>>>> Thank you Ed and Tom for the fast responses. The Patterns API sounds
>>>> interesting Tom, could you give me a link for it?
>>>>
>>
>
>
--------------090001010602060007080901
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Tom,<br>
<br>
One might argue that given it's provisional API we might consider
directly deprecating it now and that we'd be within the bounds of
expected behavior to remove it entirely, though doing that after M6
seems bad.<br>
<br>
<br>
Tom Schindl wrote:
<blockquote cite="mid:hqjnt0$2sh$1@build.eclipse.org" type="cite">
<pre wrap="">Hi Enrico,
I can think that we'd probably deprecate and remove in a timeframe of
some releases (as specified by the Eclipse API Deprecation guidelines)
but we naturally know that many people are using the Observables-API and
so we'll support it with bugfixes *but won't* add new features (e.g.
support for ObservableSets was only added to the Properties-API).
So though there's no immediate reason to switch over to Properties
(beside that doing this with 3.5.2 reveals a performance problem fixed
in 3.6.0) I'd think about switching over to Properties with the Helios
release of Eclipse- and EMF-Databinding.
Tom
Am 20.04.10 09:56, schrieb Enrico Schnepel:
</pre>
<blockquote type="cite">
<pre wrap="">Whats the difference between the Properties and Observables APIs? Up to now
I have used the Observables API. Shall I switch for current/future projects?
Will the Observables support be removed in future version or marked as
deprecated?
Enrico
"Tom Schindl" <a class="moz-txt-link-rfc2396E" href="mailto:tom.schindl@bestsolution.at"><tom.schindl@bestsolution.at></a> schrieb im Newsbeitrag
<a class="moz-txt-link-freetext" href="news:hqie49$5t0$1@build.eclipse.org">news:hqie49$5t0$1@build.eclipse.org</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
EMFProperties and EMFEditProperties is the thing you want and it's part
of EMF-Databinding since the last release.
We'll add features to the Properties API in future and not to
EMFObservables because we get direct support for this from upstream
(Eclipse-Databinding).
Tom
Am 19.04.10 22:20, schrieb Nick:
</pre>
<blockquote type="cite">
<pre wrap="">Thank you Ed and Tom for the fast responses. The Patterns API sounds
interesting Tom, could you give me a link for it?
</pre>
</blockquote>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>
--------------090001010602060007080901--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: EMFObservables Provisional Status [message #528389 is a reply to message #528387] |
Tue, 20 April 2010 11:06 |
Thomas Schindl
Messages: 6651
Registered: July 2009 |
Senior Member |
|
|
Hi Ed,
So you'd suggest:
* Deprecate Observables in Helios and remove Provisional from Properties
* Remove deprecated in Next Release Train
I would have done this before if I would have the time to implement the
missing feature in the Properties-API before last weekend :-(.
Tom
Am 20.04.10 12:52, schrieb Ed Merks:
> Tom,
>
> One might argue that given it's provisional API we might consider
> directly deprecating it now and that we'd be within the bounds of
> expected behavior to remove it entirely, though doing that after M6
> seems bad.
>
>
> Tom Schindl wrote:
>> Hi Enrico,
>>
>> I can think that we'd probably deprecate and remove in a timeframe of
>> some releases (as specified by the Eclipse API Deprecation guidelines)
>> but we naturally know that many people are using the Observables-API and
>> so we'll support it with bugfixes *but won't* add new features (e.g.
>> support for ObservableSets was only added to the Properties-API).
>>
>> So though there's no immediate reason to switch over to Properties
>> (beside that doing this with 3.5.2 reveals a performance problem fixed
>> in 3.6.0) I'd think about switching over to Properties with the Helios
>> release of Eclipse- and EMF-Databinding.
>>
>> Tom
>>
>> Am 20.04.10 09:56, schrieb Enrico Schnepel:
>>
>>> Whats the difference between the Properties and Observables APIs? Up to now
>>> I have used the Observables API. Shall I switch for current/future projects?
>>> Will the Observables support be removed in future version or marked as
>>> deprecated?
>>>
>>> Enrico
>>>
>>> "Tom Schindl" <tom.schindl@bestsolution.at> schrieb im Newsbeitrag
>>> news:hqie49$5t0$1@build.eclipse.org...
>>>
>>>> Hi,
>>>>
>>>> EMFProperties and EMFEditProperties is the thing you want and it's part
>>>> of EMF-Databinding since the last release.
>>>>
>>>> We'll add features to the Properties API in future and not to
>>>> EMFObservables because we get direct support for this from upstream
>>>> (Eclipse-Databinding).
>>>>
>>>> Tom
>>>>
>>>> Am 19.04.10 22:20, schrieb Nick:
>>>>
>>>>> Thank you Ed and Tom for the fast responses. The Patterns API sounds
>>>>> interesting Tom, could you give me a link for it?
>>>>>
>>>
>>
>>
|
|
|
| Re: EMFObservables Provisional Status [message #528414 is a reply to message #528389] |
Tue, 20 April 2010 12:42 |
Ed Merks
Messages: 33142
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------060408080602040304070809
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Tom,
Yes, I think that would be best.
Tom Schindl wrote:
> Hi Ed,
>
> So you'd suggest:
> * Deprecate Observables in Helios and remove Provisional from Properties
> * Remove deprecated in Next Release Train
>
> I would have done this before if I would have the time to implement the
> missing feature in the Properties-API before last weekend :-(.
>
> Tom
>
> Am 20.04.10 12:52, schrieb Ed Merks:
>
>> Tom,
>>
>> One might argue that given it's provisional API we might consider
>> directly deprecating it now and that we'd be within the bounds of
>> expected behavior to remove it entirely, though doing that after M6
>> seems bad.
>>
>>
>> Tom Schindl wrote:
>>
>>> Hi Enrico,
>>>
>>> I can think that we'd probably deprecate and remove in a timeframe of
>>> some releases (as specified by the Eclipse API Deprecation guidelines)
>>> but we naturally know that many people are using the Observables-API and
>>> so we'll support it with bugfixes *but won't* add new features (e.g.
>>> support for ObservableSets was only added to the Properties-API).
>>>
>>> So though there's no immediate reason to switch over to Properties
>>> (beside that doing this with 3.5.2 reveals a performance problem fixed
>>> in 3.6.0) I'd think about switching over to Properties with the Helios
>>> release of Eclipse- and EMF-Databinding.
>>>
>>> Tom
>>>
>>> Am 20.04.10 09:56, schrieb Enrico Schnepel:
>>>
>>>
>>>> Whats the difference between the Properties and Observables APIs? Up to now
>>>> I have used the Observables API. Shall I switch for current/future projects?
>>>> Will the Observables support be removed in future version or marked as
>>>> deprecated?
>>>>
>>>> Enrico
>>>>
>>>> "Tom Schindl" <tom.schindl@bestsolution.at> schrieb im Newsbeitrag
>>>> news:hqie49$5t0$1@build.eclipse.org...
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> EMFProperties and EMFEditProperties is the thing you want and it's part
>>>>> of EMF-Databinding since the last release.
>>>>>
>>>>> We'll add features to the Properties API in future and not to
>>>>> EMFObservables because we get direct support for this from upstream
>>>>> (Eclipse-Databinding).
>>>>>
>>>>> Tom
>>>>>
>>>>> Am 19.04.10 22:20, schrieb Nick:
>>>>>
>>>>>
>>>>>> Thank you Ed and Tom for the fast responses. The Patterns API sounds
>>>>>> interesting Tom, could you give me a link for it?
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>>
>
>
--------------060408080602040304070809
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Tom,<br>
<br>
Yes, I think that would be best.<br>
<br>
<br>
Tom Schindl wrote:
<blockquote cite="mid:hqk1s2$h30$1@build.eclipse.org" type="cite">
<pre wrap="">Hi Ed,
So you'd suggest:
* Deprecate Observables in Helios and remove Provisional from Properties
* Remove deprecated in Next Release Train
I would have done this before if I would have the time to implement the
missing feature in the Properties-API before last weekend :-(.
Tom
Am 20.04.10 12:52, schrieb Ed Merks:
</pre>
<blockquote type="cite">
<pre wrap="">Tom,
One might argue that given it's provisional API we might consider
directly deprecating it now and that we'd be within the bounds of
expected behavior to remove it entirely, though doing that after M6
seems bad.
Tom Schindl wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Enrico,
I can think that we'd probably deprecate and remove in a timeframe of
some releases (as specified by the Eclipse API Deprecation guidelines)
but we naturally know that many people are using the Observables-API and
so we'll support it with bugfixes *but won't* add new features (e.g.
support for ObservableSets was only added to the Properties-API).
So though there's no immediate reason to switch over to Properties
(beside that doing this with 3.5.2 reveals a performance problem fixed
in 3.6.0) I'd think about switching over to Properties with the Helios
release of Eclipse- and EMF-Databinding.
Tom
Am 20.04.10 09:56, schrieb Enrico Schnepel:
</pre>
<blockquote type="cite">
<pre wrap="">Whats the difference between the Properties and Observables APIs? Up to now
I have used the Observables API. Shall I switch for current/future projects?
Will the Observables support be removed in future version or marked as
deprecated?
Enrico
"Tom Schindl" <a class="moz-txt-link-rfc2396E" href="mailto:tom.schindl@bestsolution.at"><tom.schindl@bestsolution.at></a> schrieb im Newsbeitrag
<a class="moz-txt-link-freetext" href="news:hqie49$5t0$1@build.eclipse.org">news:hqie49$5t0$1@build.eclipse.org</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
EMFProperties and EMFEditProperties is the thing you want and it's part
of EMF-Databinding since the last release.
We'll add features to the Properties API in future and not to
EMFObservables because we get direct support for this from upstream
(Eclipse-Databinding).
Tom
Am 19.04.10 22:20, schrieb Nick:
</pre>
<blockquote type="cite">
<pre wrap="">Thank you Ed and Tom for the fast responses. The Patterns API sounds
interesting Tom, could you give me a link for it?
</pre>
</blockquote>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>
--------------060408080602040304070809--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.04170 seconds
] 
Search
Help
Register
Login
Home
