[NUnitAsp-devl] NUnitAsp architecture thought

[David G. <Dav...@un...>]

(Apologies if this has already been discussed - I couldn't find anything
in the mail archive myself)
=20
My understanding of how NUnitAsp works is that it currently includes an
SGML parser that processes the incoming HTML. The upside of this
approach is I assume it is reasonably quick, and doesn't require any UI
stuff.
=20
The downside seems to be that there is obviously no client-side
JavaScript support, and there are also occasional issues with the SGML
parser (eg. some of the DOCTYPE bugs)
=20
What I'm wondering is whether it would be worthwhile embedding a browser
control (IE or Firefox should be able to do this - see
http://www.iol.ie/~locka/mozilla/control.htm) and letting that do the
parsing instead. Then you'd get the option of JavaScript and a more
flexible parser. I presume it would then just be a matter of querying
the DOM of the browser to extract the relevant information for NUnitAsp
to use.
=20
I'm not saying this would be an easy thing to do, but it's an idea at
least :-)
=20
-dave
=20
--=20
David Gardiner <>< Senior Programmer with UniSAnet Project.
Flexible Learning Centre, Underdale Campus, University of South
Australia
Email: dav...@un... Ph +61 8 8302 1278 Fax +61 8 8302
1288=20
Web: http://davidgardiner.blogspot.com/
=20