MetaKit has its own Wiki [http://www.equi4.com/metakit/wiki.cgi/] and home page [http://www.equi4.com/metakit/].
MetaKit is the [persistence] engine for [WiKit], of course.












[Mark Roseman] has written a tutorial [http://www.markroseman.com/tcl/mktcl.pdf] on MetaKit
for Tcl developers.  Here's the same tutorial [http://www.equi4.com/metakit/mktcl.html] in HTML.
Here's the detailed documentation [http://www.equi4.com/metakit/tcl.html].

The [MetaKit File Format].

----
'''[DGP]'''
For what it's worth, here are the points I found most
useful in the Roseman intro:

   * Use properties that define as small a unit of information as possible. 
   * Creating more views is a good thing.  Do that, don't muck up a single view with special cases. 
   * Moving data to/from a Tcl array is easy and familiar to Tclers. 
   * Emphasis that restructuring of a view layout means you can continue revising your data model as you go.  Just start coding; you can change it later.
   * Some discussion when subviews are good vs. additional views.

----
"... many of the integrity
checks required in traditional database use are not required in Metakit,
because Metakit offers nested views -- a cleaner way to represent the
relationships often enforced by integrity constraints."







----
"cleaner" is a matter of opinion, ask a relational database theorist.  I don't want to start those arguments here, just point out that if you use Metakit for a complex system, you '''should''' design first, and be very careful. - EMJ
----
[Category Database]