Skip to main content

gnocl::draw

Resurrected the cairo module today. I almost deleted it a while ago but decided to return to it after I needed some its functionality in my ScanDocs application. Ok, some of these drawing functions can be achieved using a canvas, but I wanted optimal speed. When I returned to the code I found that I broke away after coming to a standstill on implementing the line and fill attributes. I'd got 90% of the way there.... Today got through that one in about 15mins. I've got the most of the Cairo primitives sorted now but have come to a similar 'sticky wicket' with regard to setting patterns. Its a little late now and so this is something for later on this week.

Here's the test script:

#---------------
# test-cairo.tcl
#---------------
#
#---------------
#! ./bin/sh
#\
exec tclsh "$0" "$@"
#---------------

package require Gnocl

# how to pass these values to a cairo context?
# keep them in a global context, when drawing occurs, these are read!



#gnocl::mainLoop

set pb1 [gnocl::pixBuf load -file ./im-0007.pnm]
set pb2 [$pb1 resize -width 210 -height 297]

gnocl::draw set \
    -lineColor {1.0 0.0 0.0 0.5} \
    -fillColor {0.0 0.0 1.0 0.5} \
    -lineWidth 10 \
    -dash DUNNO

# top
gnocl::draw line $pb2 -from {0 0} -to  {0 296}
# bottom
gnocl::draw set \
    -lineColor {0.0 0.0 1.0 0.5} \
    -fillColor {1.0 0.0 0.0 0.5} \
    -lineWidth 10 \
    -dash DUNNO

gnocl::draw line $pb2 -from {200 0} -to  {200 296}

gnocl::draw circle $pb2 -center {200 200} -radius 50

set xc 100
set yc 100
set r 100
set a 90

gnocl::draw arc $pb2 \
    -center {100 100} \
    -radius 50 \
    -startAngle 0 \
    -endAngle 90 \
    -fill 1 \
    -negative 1

gnocl::draw curve $pb2 \
    -points {
        0 150
        50 50
        150 150
        200 50} \
    -fill 1

gnocl::draw pattern $pb2 \
    -type radial \
    -center1 {115.2, 102.4,} \
    -radius1 {25.6} \
    -center2 {102.4, 102.4,} \
    -radius2 {128.0} \
    -startColor {1 1 1 1} \
    -endColor {0 0 0 1}

# sides
#gnocl::draw line $pb2 -from {200 0} -to  {200 296}
#gnocl::draw line $pb2 -from {200 0} -to  {200 296}

#centre
#gnocl::draw line $pb2 -from {105 0} -to  {105 296}

set img1 [gnocl::image -image %?$pb2 ]
gnocl::window -child $img1



And a screenshot...



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