Skip to main content

Recent activity -Scripting...

The past couple of days has seen me gnocl scripting rather than working on core code. One pet project of mine is the automated creation of edocs and ebooks. Although I have an old version of AbbySoft Professional which runs on my laptop and an equally ancient version of Acrobat 6, I want to add docs as I work on my desktop machine. To do this I created a front Tcl/Gnocl front end to control the scanning, clean-up and cropping of scans, the conversion to DJVU with OCR and packing of graphics to a multipage TIF for later processing in FineReader. Everything works fine but my control script had been hacked to gether over the past year or more and so some rationalisation is in order. But, but, but... Who likes writing code from scratch all the time? Creating new basic GUIs is always a chore so I thought that I'd create something to the growing gnocl megawidgets package. Todays addition will build a container and add the main control elements for menus, toolbars, the main content area and status block. Names and aliases for these items is returned as a list for future modification. Its still all basic at the moment, but it make life easier. Perhaps I should include this with the next release? Well, here's the proc itself:

#---------------
# Create a boilerplate application window
#---------------
proc gnocl::default {args} {
# set some defaults here
set opts(menubar) ""
set opts(toolbar) ""
set opts(box) ""
set opts(status) ""
foreach {arg val} $args {
    switch -- $arg {
        -opt1 -
        -opt2 { append opts(menubar) "$arg $val " }
        -opt3 -
        -opt4 { append opts(toolbar) "$arg $val " }
        -opt5 -
        -opt6 { append opts(box) "$arg $val " }
        -opt7 -
        -opt8 { append opts(status) "$arg $val " }
        default { puts "WARNING: Invalid option $arg."    }
        }
}
set app(menuBar) [gnocl::menuBar]
set app(toolBar) [gnocl::toolBar]
set app(box) [gnocl::box]
set app(status) [gnocl::statusBar]
set app(container) [gnocl::box -orientation vertical]
$app(container) add $app(menuBar)
$app(container) add $app(toolBar)
$app(container) add $app(box) -fill {1 1} -expand 1
$app(container) add $app(status)
# create menus
# file i/0
# create menus
set app(menu,file) [gnocl::menu]
set app(menu,help) [gnocl::menu]
#attach items
$app(menuBar) add [gnocl::menuItem -text "%__File" -submenu $app(menu,file)]
$app(menuBar) add [gnocl::menuItem -text "%__Help" -submenu $app(menu,help)]
#add menu sub-items
$app(menu,file) add [gnocl::menuItem -text "%#Quit" -onClicked exit]
$app(menu,help) add [gnocl::menuItem -text "%__About" -onClicked {puts "About Gnocl"}]
# create toolbars
$app(toolBar) add item -text "Button1" -onClicked {puts Button1}
$app(toolBar) add space
$app(toolBar) add checkItem -text "Button2" -onToggled {puts Buton2}
#eval "set app(top) [gnocl::window -visible 1 -child $app(container) ]"
#$app(top) center
#eval "$app(top) configure $winArgs"
$app(status) push "Ready"
# return a list consiting of widget aliases and names
return [array get app]

}

Comments

Popular posts from this blog

gnocl::calendar

Given this module some attention today. Added some of the more package wide options to the module and created customised handler for setting the month. (For some odd reason months are are counted 0-11 whereas days are 1-31.) There's still a little more to do to this one including the addition of code to store diary details. Here's the working test script to show the range of options at work. The percentage substitution string item %e explores something that I've been toying with, the name of the signal/event that initiated the call. Ok, a script can keep its own internal trace but who knows, it might prove useful. #--------------- # calendarTest.tcl #--------------- # Author:   William J Giddings # Date:     07/05/09 #--------------- #!/bin/sh # the next line restarts using tclsh \ exec tclsh "$0" "$@" #--------------- package require Gnocl set cal [gnocl::calendar] $cal configure -day 8 -month 7 -year 1956 $cal configure -rowHeight 1 -colWidth 1 $ca

Gnocl Dashboard

Over the past few programming sessions I've been working on producing a central point, a dashboard, around which it's possible to see the various Gnocl widgets and commands in operation. In many ways like the demo script which shipped with the earlier releases of Gnocl but offers much more. The introspection functionality provides details of the various options and sub-commands of each Gnocl procedure which are displayed under the associated tab. Sample scripts are included for each item which offers newcomers a clearer insight into how make the most of what's on offer.

Simple Runtime Debugging Message Dialog

At times it's useful to see what values variables hold, or offer some pause point before the code goes elsewhere before causing havoc. Its possible to write output to the terminal but this can get lost in copious forms of other outputs, besides, there's no pausing the script execution either. The following proc creates a custom dialog which displays ad message along with the point in the calling script from which it was invoked. ## simple runtime debugging feedback dialog, alternative to console based gnocl::msg # @param msg message to display # @returns none # proc xxx::msg {txt} { set frame [info frame -1] append msg "Message:\n\n" append msg " $txt \n\n\n" append msg "Called from:\n\n" append msg "Proc:\t[lindex [info level -1] 0]\n" append msg "File:\t[file tail [dict get $frame file]]\n" append msg "Line:\t[dict get $frame line]\n" gnocl::dialog \ -type info \ -text $msg