Pierre-Mikael Legris <[EMAIL PROTECTED]> writes:

> > Can you explain, briefly, the system that this uses?  I'm not sure
> > I 'get it'.  If I end up using this, it will go in the main
> > mod_dtcl branch, not in the 'kitchen sink' distribution.

> The best is to have a look at the source of any file.
> the documentation can be retreived from .tcl .ttml and .ttd files (tle last one
> stands for tt documentation)

> The goal was to have a tool similar to javadoc.  Have a look to
> bin/ttdoc.tcl which is the application and to src/ttd/* which are
> the source documentation files.

> The system is a bit complex, but the gramar of the <TTD>...</TTD> blocs satisfy
> me. I think that ttdoc has to be completly rewriten to handle the documention
> generation whith a xml parser (and not a sgml parser like now).

How does one go about creating these?  Is there a specific tool?  They
look pretty ugly, IMO.  Maybe something like a seperate file would be
nice?  I don't know...

> > bin/               # maybe part of build/ ?
> > packages/
> >          index     # descriptions of the various packages, and what
> >                    # they do
> >          tt_pack/
> >          nstcl/
> >          etc/
> >          etcccc/
> > build/             # build scripts for everything

> Yep looks good for me.

I have created a 'tcl-kitchen-sink' directory in Apache's CVS.   Let's
see... for now, we can put in:

some database extensions
gdtclft
parts of pierre's work
hopefully, nstcl in the future...
other ideas?

-- 
David N. Welton
     Personal:           http://www.efn.org/~davidw/  
Free Software:           http://people.debian.org/~davidw/
   Apache Tcl:           http://tcl.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to