email: mailto:tom.krehbiel@motorola.com

I am a software developer that was originally educated as an electrical engineer. I have held a varity of jobs other than software developer including semiconductor circuit designer, semiconductor device engineer, developer & manager of CIM systems manager and parametric testing manager. Before the UNIX revolution in the '80s I developed software on IBM mainframes, DEC mini's and Zerox time share systems. At that time I mostly programmed in Fortran but in the late '80s I switch to C as UNIX systems became more prevalent. Graphical user interfaces have always been a special interest of mine. This started when I wrote a menuing systems for a VT100 terminal and has progressed from using Dialog on Apollo systems, then to Xt,Motif, and to UIMX, and finally to Tcl/Tk.

----
''The following are notes on Tclkit/Starkit/Starpack and related subjects. I am gathering notes here and if a note survives and grows it will eventually be moved to its own page.''

----
'''Jean-Claude Wippler comments on how to do 3-file mode starkit'''
 > Could you elaberate a little on the "three-file mode". I'm only 
 > familiar with the 2-file mode. What is the correct method for loading 
 > extentions from a third starkit.

It's what Kitten does. One file is tclkit, one file is the app  starkit, and a third file contains a bunch of extensions, it could come  from another source, or contain things want to have around in multiple  projects anyway.

Here's a quick summary of steps to create/use a separate starkit for  extensions:

   * create myexts.vfs/main.tcl containing just these two lines (i.e. setup & return):

     package require starkit
     starkit::startup

   * place all your extensions inside myexts.vfs/lib/
   * wrap it up using "sdx wrap myexts.kit"
   * to use these extensions, all you need to do is "source myexts.kit"

A few possible refinements:

   * if you want it to work as above but also list all packages when launched, use:

     package require starkit
     if {[starkit::startup] eq "sourced"} return
     puts [lsort package names]
     # note that you'll also see other packages on auto_path

   * to source myexts.kit when it lives *next* to the launched app starkit:
     source [file join [file dirname $starkit::topdir] myexts.kit]

   * to avoid unwanted interaction between two starkits, perhaps make that:
     set savetop $starkit::topdir
     source [file join [file dirname $savetop] myexts.kit]
     set starkit::topdir $savetop

----
'''Using the local mode Wiki::init command'''

To use a Wikit as a help system for an application you need to do a Wiki::init command. The command has the following syntax

 Wiki::init <db-path> [<R/W-flag>] [<tk-path>] [<page>] 
 
Where:

 <db-path>   - path to .tkd database
 <R/W-flag>  - 1=readonly; 0=readwrite; default is readonly
 <tk-path>   - path to top leve tk window; default is ""
 <page>      - title of page to be displayed; default is ""

----
'''How to indent an image on a Wikit page'''

To indent an image on a Wikit page, preceed the image reference with some number of double qouted blanks.

 Example:

 ''     ''[http://myImage.gif]

----
'''How to access a Wikit page using its id number'''

If you need to view a wikit page and you only know its id number, then you can enter the page id surrounded by angle brackets (e.g. '[[45]]') into the search field. The search engine will report something like:

 Searched for "45" (in page titles):
    *    No matches found

But the "45" in the above message is a link so you can just click on it to go to the page with an id number of 45.

[Tom Krehbiel]
----

[[
[Category Home Page] |
[Category Person]
]]