(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-5) was last changed on 28-Nov-2007 07:05 by RadomirDopieralski  

This page was created on 21-Nov-2007 00:05 by RadomirDopieralski

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 25 added 6 lines
As I see it, a reference implementation would only have to output a DOM tree in some form (XML?), so that it could be compared with the output of the application I'm developing and want to test. It doesn't need to be fast or efficient, but it would be nice if it had a lot of options in all those parts where the spec allows flexibility. I'm not sure whether I care about how clear the source code is or what language it is written in, as long as I can run it from my unit tests.
A perfect solution would be a "validator", that would take Creole and parsed HTML as input, and find parsing errors. I'm not sure whether it's even possible, but that would be the "reference implementation" of my dreams.
-- RadomirDopieralski, 2007-Nov-28
Version Date Modified Size Author Changes ... Change note
5 28-Nov-2007 07:05 1.71 kB RadomirDopieralski to previous what reference implementation I'd love to have
4 21-Nov-2007 20:22 0.965 kB YvesPiguet to previous | to last
3 21-Nov-2007 17:56 0.604 kB 150.254.78.35 to previous | to last everything?
2 21-Nov-2007 00:36 0.505 kB YvesPiguet to previous | to last yes
1 21-Nov-2007 00:05 0.461 kB RadomirDopieralski to last what's in a "documentation"
« This page (revision-5) was last changed on 28-Nov-2007 07:05 by RadomirDopieralski