The making of WebCoder 2009 – part 7

November 10, 2008

With each new application I develop, there seems to be one recurring item on my TODO list: Better IntelliSense support! I personally love IntelliSense, and I think that most of you do too - the rest will always be able to turn it off :). In WebCoder 2009, I have introduced IntelliSense in two more areas by now. First of all, I have added HTML entity IntelliSense, so that you can type them faster than before, without having to know their exact name:


The list is pretty comprehensive - it actually consists of each and every HTML entity as defined by W3. Of course, this will only work if you can remember at least the first part of the entity name, as shown on the picture. If you're looking for the entity name of a specific character, you can use the special character CodeLib, which I have updated for WebCoder 2009, so it also comes with every possible entity/character :). That's all good, but have a look at the next screenshot, which shows something that I think is even cooler:


Inline syntax coloring and IntelliSense support for CSS code in the style attribute! It wasn't an easy task to implement, but after some adjustments, it's working out pretty nicely, and I personally love to have CSS IntelliSense outside the regular CSS documents too :)

Besides that, I have added loads of information to the IntelliSense lists. For instance, each HTML tag and attribute will have a small description and a small notification if they are deprecated, CSS properties will show a list of possible values, with the default value marked in bold, and so on. There are lots of small details like that all over the place :)

Kasper (TSW) @ 9:31 am in WebCoder

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

  1. Kevin Johnson says:

    This is awesome, what a huge timesaver! I get really sick of having to search for these every time.

  2. Jacob says:

    When can we expect a bete version?

  3. Kasper (TSW) says:

    Thank you Kevin, I’m glad you like it :)

    Jacob, when it’s ready :P. Hopefully soon :)

  4. Philip says:

    I usually breadboard the CSS inline in the HTML document and then transfer it out to the sheet when I am happy that it just needs tuning. What would be so very cool would be an export function that could take the inline CSS out of the HTML and import it reformatted into the style sheet.

  5. Kasper (TSW) says:

    Hi Philip,

    That’s actually a really good suggestion! I have implemented it today, and you can see it in the first beta version, soon to be released. I hope you’ll like it :)

Leave a Reply