DOM backward compatibility: Difference between revisions
some edits & i/o plug-in link, add catg |
|||
| Line 11: | Line 11: | ||
==IO plug-in changes== | ==IO plug-in changes== | ||
This section tracks changes made to the [[I/O plug-in]] system. | This section tracks changes made to the [[I/O plug-in]] system. | ||
===Revision 8805=== | |||
In revision 8805 (7 May 2007) changes were made to the atomic type and meta attribute systems that require changes in I/O plugins. Responsibility for handling whitespace when reading a document has been moved from the I/O plugin to the atomic types. This should simplify I/O plugins. See the changes made to daeLIBXMLPlugin.cpp in revision 8805 for more details. | |||
[[Category:COLLADA DOM]] | [[Category:COLLADA DOM]] | ||
Revision as of 05:12, 30 May 2007
This page lists changes to the DOM API.
Purpose
Sometimes the DOM API changes in a way that prevents client applications from working properly when they upgrade to the latest DOM version. Although the DOM maintainers minimize API breakage as much as possible, sometimes it's necessary. In most API breakage situations, the client application no longer compiles.
This page is used to record any changes that require clients to modify their code to work with a newer version of the DOM.
Core API changes
This section tracks changes made to the core API.
IO plug-in changes
This section tracks changes made to the I/O plug-in system.
Revision 8805
In revision 8805 (7 May 2007) changes were made to the atomic type and meta attribute systems that require changes in I/O plugins. Responsibility for handling whitespace when reading a document has been moved from the I/O plugin to the atomic types. This should simplify I/O plugins. See the changes made to daeLIBXMLPlugin.cpp in revision 8805 for more details.