From: Peter G. <pe...@ar...> - 2003-06-04 19:45:31
|
This morning's development snapshot (j 0.19.0.3, lisp 0.0.0.36) is up: http://armedbear.org/j.zip (source and documentation) http://armedbear.org/j-jar.zip (just j.jar) This snapshot introduces the command xmlValidateBuffer, which does what its name suggests. At this point xmlValidateBuffer is not mapped by default, but it probably should be; suggestions of an appropriate free key combination are earnestly solicited. For a quick demo of xmlValidateBuffer, open any handy XML file (j's build.xml will do) and do Alt X, "xmlv" <Tab> <Enter>. When I do that with build.xml, I get about 350 lines of error messages (build.xml is well-formed, but it doesn't even try to be valid). Currently, all you can do is admire these error messages in the transient output buffer that is generated for that purpose, or maybe use Ctrl Shift G as a poor man's thisError, which isn't implemented yet for XML mode but will be in the next snapshot if all goes well. I liked the use of a transient output buffer with xmlValidateBuffer so much that I retrofitted xmlParseBuffer (mapped by default to Ctrl P in XML mode, which is something of a sore subject in itself) to work the same way. One thing this means is that in this snapshot, the old mechanism that took you directly to the source of the (one and only) error encountered by xmlParseBuffer no longer works. I think the transient output buffer approach, combined with a normal implementation of thisError, nextError and showMessage (just like in Java mode compilation buffers) will work better in the long run; this functionality should be in next snapshot. The real win is that xmlParseBuffer may generate a number of errors and/or warnings, not just one and only, and the transient output buffer lets you see much more clearly what's going on. (As an example, try the original 1998 XML version of the XML 1.0 specification, for which Crimson generates 9 warnings even with validation turned off.) (Note that the parsing done to generate the sidebar tree in XML mode is always done with validation off; the tree is just a navigational aid.) I'm not a big user of XML myself (and even when I do use it, my needs are very modest), so please let me know if this new stuff is on the right track (bearing in mind that at the moment it's still a bit rough). Thanks for your support. -Peter |