Hi, you can find my personal pages at http://www.equi4.com/jcw/, which is part of my company's website at http://www.equi4.com - I can be reached at mailto:jcw@equi4.com

There's no need to explain [Wiki] and [WiKit] here, since they both have a page.
Nor MetaKit, which has a homepage [http://www.equi4.com/metakit/].
Good, that's out of the way.

There are several places for discussion about both the content ([Comments on the Tcl'ers Wiki]), and the implementation of this site ([Suggestions for WiKit]).  The whole idea of [Wiki] is fascinating, but can also be confusing (see [Wiki Gripes]).

Finding things in such a place as this can be, eh, challenging.  I find the [Search] facility, the [Recent] changes list, and pages such as [Tcl'ers] and [Acronym collection] to be quite workable.  Many new starting points will turn up in the [New pages] section, no doubt.
----
Some random thoughts on what ''could'' also be done on this site:
   * A list of download sites ''(really? another one?)''
   * A list of extensions and their home page ''(really? another one?)''
   * Links to other scripting languages (many of which interface to Tk, btw)
   * A list of projects in the Tcl community, or better still: a status overview
   * Mailing lists overview: audience, topic, how to sign up, archive location
   * Who's who, perhaps a page for everyone mentioned in the [Tcl'ers] list
   * A list of abandoned packages, or frequently lost download spots (FLDS?)
   * A list of books/articles/magazines ''(really? another one?)''
   * Track news on NeoSoft and build a list with links to major announcements
   * Condensed summaries of frequently discussed / controversial issues in Tcl
----
''From another page written early March 1999:''

Planned formatting changes:
   * Auto-recognize normal URLs and jump to them when clicked.  In the local version this means having a little web browser inside, which is simple with the "html_library" package.
   * Brackets around full URLs which end in .gif, .jpeg, or .jpg should show an inline image (which will be cached inside the WiKit document, btw)

Planned enhancements:
   * Import the entire WiKit document (export is done)
   * Allow remote update of the driving sript in WiKit from my site
   * History of changed pages (per page), allow rollback.  Diff's?
   * Titles which end in .html are pages consisting of html text
   * Allow ":command args..." to execute custom script pages (safe interp?)
   * Create a mechanism to localize this thing (should be quite simple)
   * Customize fonts with X options or some other way

Really major enhancements:
   * Let a web-based version act as server for changes to local clients
   * Dataset-server functionality: efficient outbound XML updates
   * Bi-directional synchronization (or perhaps collect by email)

There's a nice page with ideas about ThoughtsWeaver at http://c2.com/cgi/wiki?ThoughtsWeaverAdditions : ''ThoughtsWeaver (q.v.) is an extension of the WikiWikiWeb, which is used inside AT&T. This page describes some of the
differences between ThoughtsWeaver and the WikiWikiWeb. ''