Bug #38
closedmde inappropriately depends on specific IBM parser
0%
Description
need to eliminate dependency on IBM TX classes. Probably easiest way is to
break the view (JTree) from the storage of our DOM tree in a more typical MVC
architecture. If so, can probably use a DOM model in an interface class. Still
leaves the problem of interrogating the DTD, which will still be parser specific
at this point in time. Maybe build an application specific model of the DTD
from the SAX DeclHandler interface? Better, have an API for accessing the DTD
which can be mapped onto parser specific functionality, as was originally
envisioned for the ParserDriver interface. Overall this task is a major code
cleaner to factor out parser specific dependencies. Test by running under
xerces parser.
Updated by Matt Jones over 24 years ago
need to eliminate dependency on XML4J. Best if we use only SAX and DOM
interfaces for reading the document, and read the DTD separately. Possibly use
specific DTD parsing class.
Moved bug to dmanclient product.
Updated by Matt Jones over 23 years ago
Lowered priority because we might drop MDE and replace it with another editing
solution.
Updated by Matt Jones over 23 years ago
This bug is no longer valid because of architectural changes in Morpho.