Hello Bob!
I think you are approaching this from the wrong direction. The focus
should be what functions we want to provide to our users.
If borrowing the Java6 implementation and adapting it is the best
solution to solve a problem or add a function, then let's go ahead. The
normal set of restrictions to using someone else's code applies with
licenses and whatever... I don't know if that is a problem in this case.
If there isn't a problem to be solved, or a function to be added, let's
not do it. Because of this I don't see the reason for a discussion on
principle here.
/Linus
> -----Original Message-----
> From: Bob Tarling [mailto:[EMAIL PROTECTED]
> Sent: den 12 januari 2007 21:03
> To: [email protected]
> Subject: [argouml-dev] The change to Java5
>
> I'm wondering whether on the move to Java 5 whether we could
> optionally include some Java 6 classes?
>
> I've been doing similar in GEF for some time. Even though GEF
> currently supports Java1.3 as minimum it does contain some Java1.4
> classes that it only calls conditionally at runtime. An example is
> mouse wheel support for scrolling the diagram pane.
>
> Issue 4208 is one place where I see this _might_ be useful. To either
> call our existing code or to use the Java 6 class if available.
>
> I don't know if this does actually solve that issue but it gives us an
> avenue to explore and the principle may be useful elsewhere.
>
> Or does this give us too much room for error?
>
> Bob.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
