Skip to main content
This revision made October 09, 2011 12:25, by magnum

In general, MDIFramework versions are fully backward compatible with previous ones. This page presents the cases where versions introduced backward incompatibilities with previous versions.

Version 0.5

Version 0.5 introduced two versions of the framework , one working on Java Swing and containing swing components, one without any Swing components, working on Android. Because of this, the was a clear separation between classes which did not need Swing, and classes which were dependent on the Swing framework.

Version 0.6

The only breaking change in Version 6 is adding a File parameter in the putConfiguration and getConfiguration methods of the Configuration interface. There is no need to use this parameter, but it will now allow Configurations which use File properties in their Preferences to take advantage of this File parameter, which represent the base directory for the Preferences XML File, thus allowing the File properties to be relative to this directory, and so making it portable across installations.

Difference compared to previous revision
<span>In general, MDIFramework versions are fully backward compatible with previous ones. This page presents the cases where versions introduced backward incompatibilit<span style="text-decoration:underline;color:green">i</span>es with previous versions. =Version 0.5= Version 0.5 introduced two versions of the framework , one working on Java Swing and containing swing components, one without any Swing components, working on Android. Because of this, the was a clear separation between classes which did not need Swing, and classes which were dependent on the Swing framework<span style="text-decoration:underline;color:green">. =Version 0.6= The only breaking change in Version 6 is adding a File parameter in the ''putConfiguration'' and ''getConfiguration'' methods of the ''Configuration'' interface. There is no need to use this parameter, but it will now allow Configurations which use File properties in their Preferences to take advantage of this File parameter, which represent the base directory for the Preferences XML File, thus allowing the File properties to be relative to this directory, and so making it portable across installations</span>.<span>
 
 
Close
loading
Please Confirm
Close