The making of WebCoder 2009 – part 3

October 15, 2008

So, in the last episode, we talked a bit about the new realtime validation functionality in WebCoder 2009, but you only saw a small part of it. The realtime validation checks for a wide range of problems, currently 15 different issues, and reports them back to you, by underlining the problem areas directly in the editor, as shown in the previous episode, but also by keeping a newly added list of issues in the main WebCoder window. This allows you to sort out most of the problems that can prevent your document from passing the W3 validation test, without having to manually validate the document over and over again. Here is an example of the error view, to show what I'm talking about:


As you can see, there is a piece of text for each error, telling the user what's wrong, but in fact, WebCoder 2009 will do more than just that. It will also help you fix the problem:



As you can see, a solution is proposed here, but if WebCoder knows how to fix a problem, then why do it manually? Press the quick fix shortcut, or activate it from the error view, and WebCoder can fix most of the errors for you. Some solutions are obviously more elegant than others, for instance, there's pretty much only one way to fix an "unknown attribute" error: Remove the attribute. Deprecated tags and attributes are fixed more elegantly though: WebCoder 2009 comes with a conversion map, which can be user modified, that tells the application how to convert deprecated tags and attributes into something that will validate and still work as intended. For instance, <font> tags are converted to <span> tags, and the deprecated attributes of it, like "face", "size" and "color", are converted to the CSS alternatives and placed in the style attribute. This allows WebCoder to convert most legacy HTML code into modern HTML and CSS code, with minimal user interaction. Letting WebCoder fix the most obvious validation errors is a real time saver, when compared to manually validating and manually fixing each and every error. Just wait and see :)

Kasper (TSW) @ 3:24 pm in WebCoder

9 Responses to “The making of WebCoder 2009 – part 3”

  1. BlackYeLL says:

    Great job, as always :)

  2. Jacob says:


    When can webcoder read my mind and make a website of that? (maybe an USB solution will be in place, haha) :P

    That is nice!

  3. Kevin Johnson says:

    Fancy :) I’m really excited to keep my eyes on this as it moves forward. Thanks for your hard work!

  4. Kasper (TSW) says:

    Thank you, guys :)

    Jacob: I’m saving that feature for WebCoder 2015, I think ;)

  5. Morten says:

    Nice feature :D can’t wait to use it in my development of websites ;)

    Do you have an expected release date for the first beta version of WebCoder 2009?

  6. Kenneth says:


    In the new webcoder 2009. Is it possible to get the CSS IntelliSense and HTML IntelliSense working inside the ASP tags . This would make my year ;)

    By the way thanks for a great coder tool :)

  7. Kasper (TSW) says:

    Morten: “When it’s ready for it”, but my hope is somewhere around New Year, probably after :)

    Kenneth, I’m afraid that the ASP support will not be extended, as described in a previous blog comment. Sorry :)

  8. daniele says:

    Web Coder 2009 will be multilanguage?
    If possible… i can will make Italian translation!!!

  9. Kasper (TSW) says:

    I’m still considering my possibilities in regards to localization, Daniele. An italian translation would be very cool though :)

Leave a Reply