Re: all-XSLT implementation of Minesweeper
regarding speed, the performance seem to benefit when I changed 2 expressions from "//square" to "SweeperMap/square". But the performances varies a lot by how much free space there is on the map. The more empty space, the slower the algorythm. I submitted a bug to Mozilla with a sparse map file that shows a big difference between IE & FF:
and, regarding DOM mixing, well, yes, and it is worse than mere bad form... Microsoft has a knowledge-base article saying it might throw errors:
which I think I saw while coding and testing.
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format