Quoting "David N. Welton" <[EMAIL PROTECTED]>:
> Pierre-Mikael Legris <[EMAIL PROTECTED]> writes:
>
> > #package with the TCL documentation HTMLized (cool but big)
> > http://fbwww.epfl.ch/~plegris/Tcl/code/tt0127.tgz 652k
>
> Personally, I'd rather not include these. I think most people have
> either man pages or access to the on-line versions of these...
Yeap, I agree, it's way to big..
> > DOCUMENTATION :
>
> 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).
> > tt_Base64: base64 Encoding / Decoding
>
> Hrmmm... can you tell me more? Apache has some functions to do this,
> IIRC - maybe it would be easiest to just provide an interface to that
> API.
Well this is absolutly useless, I wrote it one day while looking at php API for
ideas.. ;-)
> > tt_GetRemoteFiles: Provides tools to retrieve remote files
> > tt_HTML_Table: Advanced tools for html table generation
> > tt_Info: General info
> > tt_SendMail: Utilities to send mail
>
> How does this compare to other Tcl/Mail things? How do you feel about
> its security?
For now it just uses the application sendmail. A native implementation would be
nice.
>
> I want to establish a directory hierarchy for all this stuff before I
> start dumping my own files/contributions into it. At the moment I
> don't have any brilliant ideas, but some kind of order is necessary to
> avoid the confusion of having lots of packages. Any thoughts?
>
> Maybe:
>
> 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.
PM
-------------------------------------------------
This mail sent through IMP: imap.epfl.ch
Resent-Date: Tue, 06 Feb 2001 17:21:34 +0100 (MET)
Resent-From: [EMAIL PROTECTED]
Resent-To: [EMAIL PROTECTED]
Resent-Message-ID: <[EMAIL PROTECTED]>
X-Originating-IP: 128.178.164.51
Quoting "David N. Welton" <[EMAIL PROTECTED]>:
> Pierre-Mikael Legris <[EMAIL PROTECTED]> writes:
>
> > #package with the TCL documentation HTMLized (cool but big)
> > http://fbwww.epfl.ch/~plegris/Tcl/code/tt0127.tgz 652k
>
> Personally, I'd rather not include these. I think most people have
> either man pages or access to the on-line versions of these...
Yeap, I agree, it's way to big..
> > DOCUMENTATION :
>
> 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).
> > tt_Base64: base64 Encoding / Decoding
>
> Hrmmm... can you tell me more? Apache has some functions to do this,
> IIRC - maybe it would be easiest to just provide an interface to that
> API.
Well this is absolutly useless, I wrote it one day while looking at php API for
ideas.. ;-)
> > tt_GetRemoteFiles: Provides tools to retrieve remote files
> > tt_HTML_Table: Advanced tools for html table generation
> > tt_Info: General info
> > tt_SendMail: Utilities to send mail
>
> How does this compare to other Tcl/Mail things? How do you feel about
> its security?
For now it just uses the application sendmail. A native implementation would be
nice.
>
> I want to establish a directory hierarchy for all this stuff before I
> start dumping my own files/contributions into it. At the moment I
> don't have any brilliant ideas, but some kind of order is necessary to
> avoid the confusion of having lots of packages. Any thoughts?
>
> Maybe:
>
> 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.
PM
-------------------------------------------------
This mail sent through IMP: imap.epfl.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
