[Spindle-user] Latest update

[Geoff L. <glo...@in...>]

Integrated the custom parser into Spindle. Having problems though, as
xerces:

a) doesn't give very nice error message (validation) as compared to crimson.
They're rather cryptic
b) returns odd information for line number/column number when validation
fails.
   i.e. if a tag's contents contains illegal elements (per DTD), the error
points to the close tag rather than the open tag.
   as well, if there are validation problems with an element's attributes
the errors all point to the same line of the source,
   even if the tag is pread over multiple lines.

a) I can live with
b) screws up the error markers in Spindle. The markers don't necesarilly
appear on the line where the error occurs.

Also b is bad as I intend to use the same parser to parse the templates. As
that version of the parser will create
synthetic tags to make the file well formed, I'm concerned that there could
be real problems with this.

So I'm further customizing the parser's valdator so that the correct line
number/column number is used.

Which got me off on a tangent. Was having trouble ensuring that my errors
markers contained useful information.
The editor transforms the marker info into the icons that are shown in its
gutter and they were not showing up in the
right places.

The only way to see the contents of a marker was to debug through the code.
This is very time consuming.
So, I've built a new Eclipse view that I can use to inspect/change the
contents of any marker at runtime (no debugging).

To sum up, work on 2.4 support plods on.


Geoffrey Longman
Intelligent Works Inc.