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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |