Is it possible to backport Radiance to run on earlier releases of Java? Again, the best way to get well functioning Radiance APIs is to tell me what is missing, and what does not work well. If I make a mistake and release APIs that are not good, I'm not going to support them forever. That's a long time to carry the burden of APIs that were not designed well. I plan for Radiance to be here in the next 10-15 years. There's plenty of time in the release cycle (roughly twice a year now) to take the latest development bits for a spin and see how well - or not - Radiance APIs address the needs of your application. The best way to stop me from breaking Radiance APIs is to test them early and give me feedback on what doesn't work. If your application requires absolute visual backwards compatibility, it would be best to create a custom skin that does not extend any of the existing core Radiance skins. Visuals of different components and skins undergo periodic reexamination to address visual flaws, add polish and remove visual noise. There are no guarantees about visual compatibility between major or minor releases. Classes in the org.pushingpixels.***.internal packages are not for application use and can change at any point in time. I will do my best not to break the APIs exposed in the org.pushingpixels.***.api packages. What is the policy for backwards binary and visual compatibility? You are free to fork and modify any part of the code as long as you mention the original license in the source code / the runnable distribution.
Radiance libraries are released under BSD license. Can I use some / all the code in Radiance?
0 kommentar(er)
