I list below all topic groups, which I have done according to subjects, which they handle. You can return to this topic group by using this menu and the link Table of topic groups on the top of the each page.
This folder has primary zip files to plug-ins menus to HTML-Kit. Also some other zip-files may be available.
Here is the list of finished plug-in menus for HTML-Kit with short explanations. Compiled executable DLL-files link directly to the site of HTML-Kit. You can find them from the HTML-Kit plugins page, along with other plug-ins, including most of listed plug-ins below:
LINKelement. I added XML-related basic declaration (
<?xml-stylesheet type="text/css" href="" ?>) to the first button. I put also the element
LINKto fulfil XHTML requirements. The meaning of these exchanges is, that this menu is intended also to XML-documents and the user of this menu can't miss any required attribute.
FRAMESETbecause at least MS IE 5.x supports it. In principle modern web browser, which support of framesets is turned off can render
NOFRAMESwith CSS. At the same main principle a modern web browser, which support of scripting languages is turned off can render
NOSCRIPTinformation with CSS. I got an e-mail, where the writer said, that some user agents (e.g., Amaya) can use
LINKrelationships (e.g., next/prev) to construct a book form of a document. Then this element can have some kind of presentation with CSS in some user agent. Supporting of these elements is however quite theoretical. The TM CSS menu tells however, which elements can in theory get CSS.
EMBED, because Opera 4.0 supports it. I classify it now as a proprietary selector. I added
IFRAMEbecause Opera and MS IE support it.
counter(), counters(), no-close-quote, no-open-quote).
<xsl:text>). I checked all according to the DTD.
Menus, which are under construction:
rev, which is an implied attribute of the element
blinkwas marked as proprietary elements of MS IE. This is incorrect. It is proprietary element of Netscape. MS IE has instead of it the
Please report any possible errors which I should fix. If you have suggestions for editing the source code, send an e-mail to me.
Executable *.hks and *.dll files must be in the 'Plugins' folder of HTML-Kit (don't try to open them by double clicking files). After you have put new HKS- or DLL-files to the 'Plugins' folder of HTML-Kit (for example 'c:/Program Files/Chami/Htmk-Kit/Plugins'). Install plugins properly or clear the plugins cache using the main menu (Tools > Install > Install Plugins | Clear Plugins Cache) and restart HTML-Kit.
You can edit source codes (*.hpd) and compile them into *.hks files with HTML-Kit Plugins Generator (don't try to double click files; open first the applications). If you want to compile source codes into DLL-files you need an additional application. You can create new menus or add buttons to existing menus by using as the name of the Section the same as in some existing menu. For example, you can extend TM WMLScript and TM WAPPush menus like any other menu you wish. I have made to my personal use links to local help files to all plugins, which I have done + some default menus of HTML-Kit (Local_Help.hks).