Hi Boris

You raise valid concerns about the JDK level. Right now, apart from the 
@Override stuff, SwingWorker is the only class in Trident that actually 
requires Java 6.

I cannot promise that all future versions of Trident core are going to be Java 
5 compatible. Up until now i didn't need any of the new collection APIs added 
in Java 6, but i don't know what type of bugs / enhancements will require using 
those APIs, or any other new core functionality added in Java 6.

I can remove the @Override annotations and change the build script to produce 
the core / Swing / SWT / Android bits as four separate libraries, and have 
people playing with Trident - to test it as one possible animation library for 
use in e4. 

Thanks
Kirill




________________________________
From: Boris Bokowski <[email protected]>
To: E4 Project developer mailing list <[email protected]>
Sent: Fri, December 4, 2009 2:56:47 PM
Subject: Re: [e4-dev] Re: Trident (was: animations)


Hi Kirill,

> Thanks for the comments. It looks like we are talking about minor 
> issues - how Trident is implemented. That's a lot of valid points 
> that we can discuss in this list or in the project mailing lists.

You are right - we may want to take this off list or discuss it in the issue 
tracker over at http://kenai.com/projects/trident.

There is one more thing at this level though - your code currently requires 
Java 6, and we would like e4 to be usable on 1.5 VMs as well. I went through 
the code (the core and SWT parts), and the only 1.6 feature you are using is 
the ability to annotate methods with @Override when they are just implementing 
a method from an interface. Would you be able to produce a version of Trident 
(just the core and SWT parts) without these annotations? More importantly, 
would you be able to promise, going forward, that you won't introduce 
dependencies on anything that is only available in the 1.6 class libraries, 
from the core and SWT parts? Obviously, at some point in the future, requiring 
1.6 instead of 1.5 may make sense for e4, but we're not there yet.

Boris



      
_______________________________________________
e4-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/e4-dev

Reply via email to