RSSThe TSW Blog

The making of WebCoder 2009 – part 2

October 8, 2008

In the last episode, I talked about the new HTML parser in WebCoder 2009. The next couple of episodes, including this one, will be dedicated to highlighting some of the cool, extra functionality made possible by the HTML parser. For instance, since WebCoder knows the structure of your document, it can match start tags with end tags and let you know if you have forgotten either one of them. It will use the active HTML definition to decide whether or not a tag needs an ending tag. The realtime validator, which I will write much more about in the next episode, helps highlight this problem:

missing_end_tag

Errors are highlighted just like a spelling error in your favorite word processor, and you can get more information about the problem, as shown on the image, by hovering the mouse over the highlighted word.

 

needs_selfclosing

The active HTML definition is used and you will be reminded to close your tags in the correct way. Here it is the img tag, which needs the self-closing forward slash instead of a regular end tag.

 

endtag_proposal

WebCoder can help you close the tags you have open, and in the correct order of course, as required by XHTML. This also lets you turn off the HTML AutoComplete feature, where WebCoder automatically inserts the ending tag as soon as you write the starting tag, and then write the ending tag when you actually need it, while still getting help. When you need to end a tag, simply type the < character and press Enter, since WebCoder automatically highlights the appropriate end tag.

 

tagmatch

Since WebCoder keeps track of begin and end tags, highlighting matching tags is just a benefit! Place the cursor in either the start tag or the end tag, and WebCoder will highlight the matching opposite!

 

That's all for now, but I have a lot more to tell you about these features. In the next episode, we will take a deeper look at the realtime validation and how it can help you much more than what we've seen today. As always, stay tuned for more :)

Kasper (TSW) @ 8:44 am in WebCoder

7 Responses to “The making of WebCoder 2009 – part 2”

  1. BlackYeLL says:

    It promises to be great :) Nice work.

  2. Jacob says:

    That is really nice!

    But one thing i always wondering very much about, and that is how you can get all these nice features into that bit of space. I mean Webcoder 2007 does only require about 17 MB, while other programs maybe fill up 500 MB!

    I like to read your blog!

  3. Nicholas Swiatecki says:

    Good joob, can’t wait :)

  4. Kevin Johnson says:

    SWANKY!!~

  5. one, one,
    two. three.
    beaten’ like a brat
    from this mutha freakin beat!

    be

    cause…

    Ahww

    well…

    yessssindeed, Mista Kasper!
    Mista Kasper, indeed– ahww, yes!

    Crammin’ dat skank in’na small damn spaces
    Educatin’ mutha’s lef’ n right–
    all places!

    ‘bodys gettin’ down cause’a Genius in da house!
    layin lean code, he be krispy krazy clean
    floatin like some crisp cool snow, y’all
    ain’t nobody stoppin
    the krispy krazy ghost!

    now…

    we…

    all

    be itchin’,

    bitchin to get down
    on a what’s he comin’ round
    he all blast past
    last year
    we all better be watch out, cause he whack out
    dont be slow, y’all
    or be all without

    pay attention junior
    cause kasper krisp n krazy layn kode!
    naw, cant hack!
    no body can’t hack
    jack
    jill
    hurry up
    sit still
    better pull the shades n hide
    this krazy kasper style goin’ wild…
    — beeiotch!

    [translation:
    sounds interesting. indeed, i am eager to preview more of this new software. judging from the commentary so far, Tanggaard is poised for another great success. how very fortunate for ‘Coder fans: to anticipate yet another outstanding revision of our familiar favourite, while we catch breath– yet so quick that we might be more skillful with what we’re used to now.]

    -j

  6. Kasper (TSW) says:

    Thanks, guys :). I have already written part 3 and 4, and I can’t wait to share it with you, so keep up the nice comment flow!

    Jacob: With a .NET application, the .NET framework handles all memory management, if that’s what you’re thinking about. If you’re thinking about harddisk space, then taking up lots of space is usually caused by lots of graphics and perhaps even audio and video. WebCoder doesn’t need all that, just simple icons, which usually only requires less than 1 kb per icon :)

    Kevin: Swanky?! I think I need a translation here ;)

    Jeff: You’re crazy ;). Nice rap, but perhaps try to limit the amount of space used per comment the next time? :D

  7. Jacob says:

    Haha.

    And i am an opensource programmer :)

    Maybe thats the answer…

    …Actually i have gotten my fingers in the .NET platform.
    I have acquired me a professional version of visual studio 2008 and also windows server 2008!

    Wish me luck and good programmering about the .NET and Microsoft!

Leave a Reply