Forum OpenACS Q&A: ns_ and tcl api pages

Collapse
Posted by Tom Jackson on

I'm lazy. I'm also annoyed easily. So after years of browsing to tcl and ns_* api pages, I decided to make it easy on myself and provide an easier, for me anyway, url to get to commands by name.

Tcl api: commands are at http://zmbh.com/tcl/, just append the name of the command, for example string.

AOLserver ns_* commands: commands are at http://zmbh.com/nsapi/, just append the name of the command, for example ns_set. The wget script to download the files, plus for ns_* commands, the parse script are included in the directories, so you can do the same thing on your local server if you want. Hey, if anyone has recently tried to navigate the AOLserver api pages, you are probably annoyed that you have to guess what 'type' of command it is. Now you just need to know the name of the command. I'll work on the mostly horrible (not mine) formatting at a later date.

Collapse
2: Re: ns_ and tcl api pages (response to 1)
Posted by Jade Rubick on
Tom, this is a nice idea. Perhaps we should set these up as packages, and include them in the default install?
Collapse
3: Re: ns_ and tcl api pages (response to 1)
Posted by Tom Jackson on

Another idea I was working on was to turn all the files in an install into a set of html'ized pages. How? Well I'm working on a sed script right now that is pretty modular. You add a set of substitution tokens and a start/end file. Probably we could turn all the openacs api calls into links to the definition, or the api-doc page. The package maintainer would probably only need to provide a list of tokens and a script could generate the substitution text.

Collapse
4: Re: ns_ and tcl api pages (response to 1)
Posted by Alfred Werner on
One of my favorite short stories is 'The Tale of the Man Who Was Too Lazy to Fail' - classic Heinlein ;)