Please leave your sense of logic at the door, thanks!

HTML5 Conformance Checker Code Now More Easily Available

by Henri Sivonen in Conformance Checking

My (so far incomplete) HTML5 conformance checker has been Open Source / Free Software all along. However, due to the lack of a publicly-accessible version control system and due to numerous dependencies, the codebase hasn’t really been approachable.

This has now changed. The code is in an anonymously accessible CVS repository. There is also a single script that you can check out and run. The script will take care of downloading dependencies, building the software and running it. The instructions are on the about page.

6 Responses to “HTML5 Conformance Checker Code Now More Easily Available”

  1. Why CVS? Why not just Google Code, or SVN coupled with Trac? Need help with hosting?

  2. Because the schema project was already in CVS. I am now trying out SVN again after a two-year break. If Subclipse is finally ready for daily use, I will suggest to fantasai that we migrate the whole thing to SVN. However, a working Eclipse plug-in is a must have, so I won’t jump right in given my bad exprience with Eclipse and SVN in 2005.

  3. Ah, okay. I agree that SVN tooling has been a bit sub optimal. I don’t quite see the need for an IDE plugin, though; especially if it sucks. I used AnkhSVN for Visual Studio for some time, but found that plain Tortoise (shell extension) was way less buggy and easier to operate, so I threw out Ankh. I can understand the neatness of having SVN tightly integrated with the IDE, but is it really a requirement?

  4. Yes, a working Eclipse plug-in is a requirement. Writing Java code requires an IDE. In my case it is Eclipse. CVS is integrated with Eclipse. Any version control system that isn’t integrated with Eclipse is worse than CVS as far as I’m concerned when developing Java code. It does not matter how great the version control systems is on its own compared to CVS. I’ve worked with a version control system that required me to use the version control separately from Eclipse (SVN in 2005). It was seriously not cool compared to Eclipse CVS integration.

    On a more positive note: Subclipse as of 2007 seems to work so far.

  5. I agree Java needs an IDE (so does C#), but I think we just disagree with regard to the need for integrated source control in the IDE. Visual Studio comes with integrated support for SourceSafe, but I still think Subversion is superior. But then again, the leap between SourceSafe and Subversion is a bit greater than the one between CVS and Subversion.

    Nice to hear that Subclipse is working for you, let’s hope it continues to do so too! 🙂

  6. Yeah, we disagree about the need of IDE integration. Fortunately, Subclipse seems to be working now, so I have requested our version control provider to proceed with the upgrade to SVN.