Alexander ten Bruggencate wrote: > > first, your mailing list sent your reply to my email address and then > later to the xmleditor-support list. It doesn't have to send me the > reply since i'm on the list... One copy of your reply is enough ;-)
Sorry for that but we haven't taken the time to fine tune this, so you'll have to support this annoyance once again. > Perhaps the makefile could me a little more intelligent? as in not > compiling something that hasn't been changed and not looping through > directories. I note that I havn't reviewed your code and perhaps it must > be done the way you do it now. It just seems a waste of time... I just have 2 minutes to spend writing a makefile that's why my makefiles are far being from perfect. (And I don't use ant -- even if ant files can be created using XXE with the DTD generated by ant itself -- partly because ant is too complicated and partly because I'm satisfied with make.) > > > I'm especially happy with the print function and it's ability to handle > > > different paper sizes. > > > > Oh, this is just a quick and dirty way of printing an XML document. > > The second I pressed send I thought "I really should have checked > that...". I was thrown off by the standard java printing dialog... > At least the print page x from to y function works (checked it ^_^) You can also print the explicitly selected element (the element with a red line around it) rather than the whole document. > Are you guys planning to write your own xml-schema engine? if so why? > for example i use xerces from the apache project... We have already written our own XML-Schema validation engine after evaluating Xerces. Not an easy job! You can download it from http://www.xmlmind.com/xsdvalid.html . Why? because it is a critical component of the future product, because Xerces quality is just ``fair'' and because we need at least ``good''. (For us, the quality of a component comes from its reliability, speed, size, conformance, design.) An other example is the XML parser: we have not written an XML parser though it is a critical component. We use James Clark's XP which quality is simply _excellent_ (see http://www.xmlmind.com/xpforjaxp.html ). Note that we have tried Xerces 1.x, Crimson, ?lfred. In our opinion, after XP, the best is Crimson.
