Do Transitions really need to be final?

[Tom Eugelink]

Ok. Eh. Ok? Any description on how that would be a problem?

Tom


On 17-12-2011 9:15, Tom Schindl wrote:
> Hi,
>
> I can only guess but making something final makes evolving the API less
> problematic.
>
> See
> http://wiki.eclipse.org/Evolving_Java-based_APIs_2#Evolving_API_Classes
> that e.g. adding a public field to a class which is allowed to be
> subclassed might break binary compat.
>
> Am 17.12.11 08:32, schrieb Tom Eugelink:
>>
>> On 2011-12-17 08:25, Daniel Zwolenski wrote:
>>> Hey Guys,
>>>
>>> Just wondering if there is a reason for the various transition classes
>>> (FadeTransition, PathTransition, etc) being final?
>>>
>> I would even like to put that one step higher; why is any class final? I
>> know that the fact that they are not in Swing have allowed for many
>> improvements, unforeseen at the time Swing was created.
>>
>> Tom
>>
>