Peter Newman 24 April 2004

'''INTRODUCTION'''

The ''Tcl Standard Library Specification'' is an idea that arose from the April 2004 discussion on [Tcl Common library].

The idea of a ''Tcl Standard Library'' was floated, and generated a lot of interest. But there were so many ideas, so many issues! Lots of people want a ''Tcl Standard Library''. But there were many different ideas as to what that actually was.

During that discussion, I realised that though Tcl is great, there are still lots of outstanding issues that haven't been resolved. For example:-

   * The lack of a '''standard distribution system''' - like Perl's CPAN and RPM.

   * The '''Tiny/Minimal Core''' versus '''Batteries Included Core''' issue. We seem to have a compromise solution at the moment, that neither side is entirely happy with.

   * The '''stagnation''' of certain aspects of Tcl - like skinning/theming of the core widgets, for example.

   * The '''poor documentation''' of many of the core commands, widgets and concepts.

   * Outstanding issues regarding TEA and CVS and how to create packages and enhancements to Tcl. In other words, the '''architecture''' and '''mechanics''' of how one goes about adding extensions to Tcl.

   * The continual talk/work on '''megawidgets''' and ''MegaWidget Librarys''.

   * And there may well be many more. If there is, just let me know.

These issues seem to have been discussed/debated for many years. But progress seems either painfully slow or non-existent.

But what struck me about the debate in [Tcl Common Library] was that though these issues are always thought of as separate and un-related - in fact the are all really just subsets of the ''Tcl Standard Library''. And to make progress on these issues, we need to create a '''Tcl Standard Library Specification''' that describes how all of these things fit together.

Or to put it another way - a properly designed ''Tcl Standard Library'' should (in my opinion,) provide answers and solutions to all the problems/issues listed above. 

But the first thing to do, is to create a ''Tcl Standard Library Specification'' - that describes exactly what the ''Tcl Standard Library'' is. And how it addresses and solves all these outstanding issues/problems.

So that's what this page and the''Tcl Standard Library'' are all about.

----

[daapp] 2004-04-24:I suggest to use following scheme:

   1. the tcl standard library [[TSL]] should include only one object-oriented extension. This extension can be compiled or pure Tcl, it doesn't really matter from a specification point of view.  From a performance and  foundation point of view, it probably should be compiled, either initially or at least eventually.  This extension should not be written in a way that other object-oriented extensions are made impossible to develop and use. 
   1. TSL should include a megawidget framework, based on the object-oriented extension
   1. TSL should include the tools and modules for documentation creation and convertion into other formats
   1. TSL should include the tools and modules to create skeletons for new modules and to work with a network archive of other code
   1. TSL should include the tools and modules for easy compilation (where appropriate) and installation of extentions 
   1. [[fill in other needs here]]

My candidates:

   1. [XOTcl] for the OO framework [[anyone want to explain _why_ the choices here were made?]]
   1. [Namespace MegaWidgets] or [Snit like Delegation in XOTcl] or create something new using [XOTcl]
   1. [doctools], but with [xhtml] output included :)
   1. modules framework, which needs to be created from stratch - perhaps based on starkits however as well as [TEA2] directory structure
   1. [CriTcl]

Well, it look like the Standard Tcl Library Specification :).

----

[davidw] I'd rather create a mailing list than use wiki's for discussion, but here are some of my thoughts on the matter:

'''[Worse is Better]!''' - let's get something working, and save the more contentious pieces until later.

Every module should have one or more people willing to take responsibility for it.

Every module should attempt to harmonize on a documentation standard.

Every module should have some tests demonstrating its functionality.

Every module (except where obviously not appropriate) should function on MacOS X, Linux/BSD/Unix and Windows.

Every module should have a BSD or compatible license.

Initial candidates: thread, TclX, XML stuff, tcl big number package, udp extension.