Blogs

Demerits of Presentational Markup in handling data markup

Imagine if you could take pieces of existing HTML content and programmatically slice, dice and transform it into a new document that fits new criteria! You cannot reliably do that with conventional HTML because it is not always well-formed and hierarchical enough to enable DOM navigation to find and extract required information. This is especially difficult and even impossible when the markup is not semantic (using tables and other presentational markup). Do not loose hope though.

HTML-Kit Tools for window (Currently in Alpha version) has introduced a feature that is usually reserved for more expensive code editing suites and environments.

This second application (and improved sequel of the popular and free Web development application, HTML-Kit) has so far proven that a good and cost-effective application can be improved upon to make the current price of the released version ($45) a nominal cost for the many features and web development comforts that the two continue to offer.

.NET or ASP.NET is touted to be more powerful, versatile and future-compatible that the now archaic ASP server-side programming language. To mention a few, the .NET architecture is built to support XML natively, and it supports more powerful and robust server-side programming languages such as C# and Visual basic in contrast with ASP which mainly supports VBScript which as the name suggests is a non-compiled scripting language.

In the migration from HTML web design to XML based design, why wouldn't one choose to skip XHTML and go straight to the source, cut the middle-man and code content in XML?

Many clean-code Web Developers like myself swear by the unintrusive, clean development suite that HTML-Kit is famed to be. This tool (Version 292) is not perfect as it is, and that has warranted the development of HTML-Kit Tools for Windows/Linux (Currently in the final stages of Alpha Development).

One of the indispensable functions of a Web Development and code authoring tool is the ability to undo code modifications during a session, or even over the entire editing lifespan of a document within the tool. Previously, within HTML-Kit 292 one had to be content with unlimited undo-redo steps within a given editing session. This led to many developers keeping documents open for a long time because once a document was closed, then the facility to revert to a previous version was lost.

Similar to the above online tool provided by Chami.com especially for users familiar with the UI (User Interface) and functionality of HTML-Kit, Chami.com's new application (currently in Alpha version) HTML-Kit Tools for Windows/Linux has a similar feature for general web documents.

This document is the first in a series that will collectively focus on the many features, benefits, and limitations of Chami.com HTML-Kit and HTML Kit for Windows (and Linux). This is not an exhaustive analysis, comparison or critique of all the Web Development editors in the market, but an honest opinion of a seasoned user. I have been using Chami HTML-Kit for the last five (5) years, and more recently, I have started Alpha testing the new application (HTML-Kit Tools for Windows).

The @import function will not work if it comes after regular CSS definitions and commands in your CSS file. Make sure that @import commands come before anything else in your CSS file

The @import feature for importing external CSS files from one file into another is instrumental in creating a well organised and library of manageable CSS files. One can add these commands; example:

Without a proper understanding of CSS selector specificity, the basic approach to managing the override of one CSS is to have a single selector/declaration pair for every element, and then employ the !important switch/declaration to override pre-existing declarations.