>7. Documentation. So the other day, I was trying to figure out how to use >the #javascript directive. I went to scripting.com and looked around. >Couldn't find anything, even though I knew there was something there. >What I did find, after using the search engine, was a mention of the >directive, a statement that it wouldn't be explained there, and something >to the effect that when we needed to know it we'd be able to figure it >out. Or something like that. It was accurate. I needed to know it and, >through trial and error, I figured it out. Frontier is so complicated, so >big, so grand, that it's hard to explain how to use it.

This is why I'm not terribly big on the kernilization of html.buildpagetable. If I can't make it work, I go back and look at the source. I could figure out where #javascript is used, and what I needed to make it work. I'll admit to not having looked at the docs since Matt wrote his set a year ago, but I do know they don't answer my questions then. The source answered many more questions than the documentation ever could.

Maybe there needs to be a complete no nonsense HTML suite reference guide. Not a how to manual, or a getting started page. This guide doesn't tell you how to do anything. Just what takes what, where things need to be goe, and how it's used. If kernalization is the future, this will be absolutely necessary to build html systems that work.

John!

BEWARE OF IMITATION! NOT GENUINE WITHOUT HIS SIGNATURE

John Simms jsimms@pair.com ----------------------------------- http://www.john.pair.com

Enclosures

None.  

Replies

None.