Tcl Library Source Code

View Ticket
Login
Ticket UUID: 8c587f8f3380a3cf0ae7ad5578fc5c9ef88ff10a
Title: Combine information from /support into /modules
Type: RFE Version: 0.1
Submitter: hypnotoad Created on: 2015-01-06 11:05:44
Subsystem: Development Tools Assigned To:
Priority: 5 Medium Severity: Cosmetic
Status: Open Last Modified: 2015-01-06 19:04:48
Resolution: None Closed By: nobody
    Closed on:
Description:
Tcllib currently maintains two separate file structures: /modules (where the implementations for modules live) and /support (where sak maintains it's indices.)

I am trying to adapt a similar structure for taolib (a collection of TclOO classes) and taotk (a megawidget framework built around tao.) I also have been working on adapting some of my tools in odie to be distributed in tcllib.

Trying to find out all of the proper places to index a new package is somewhat frustrating. I also find that tcllib's SAK make quantum assumptions about the structure of a package. What I would like to see instead is more of a plugin architecture, where each module provides a ".sak" script which collects all of the index information in one shot. This would also be an excellent place to tweaks to documentation, generate C implementations for distribution in the teapot, etc.
User Comments: aku added on 2015-01-06 19:04:30:
Yes, the _tcl, etc. information in the modules.tcl are procedures in actions.tcl. _tcl is the standard module with plain packages. Some modules already have special actions, like _tcx,, or similar for their special requirements.

Agreed on using a feature branch "kettle" for initial porting and eval.

hypnotoad added on 2015-01-06 18:45:47:
Agreed, running things through the main installer seems to do the right thing(tm) if the module is properly indexed in support/installation/modules.tcl.

As far as quantum assumptions go... for taolib I had to rewrite chunks of the SAK installer. Tao has several rather large feature sets that are broken up into multiple files and directories. The SAK installer has no concept that a module could have subdirectories. Also, packages like taotk need to bundle an assortment of image resources for icons, and there isn't a neat way to do that. (Though I was unaware of the ../actions.tcl mechanism, I'll see if I can get around those issues using that.)

I'm open to evaluating Kettle. My thought is to start off with a feature branch (say... "kettle") and begin the process of porting the installer.

aku added on 2015-01-06 16:38:29:
Adding a new module should only require extending support/installation/modules.tcl, and possibly .../actions.tcl in case it requires some special stuff.

Adding a package to an existing module should not require anything.

Please correct the above should I be wrong.

Quantum assumptions: Can you list which assumptions you have found ?

Plugin ... I wonder if a switch to use Kettle would be do-able ? With that we can have a "build.tcl" in each module, and a main "build.tcl" specifying recursion in the main/top directory. ... Of course, Kettle makes assumptions about structure too.