Skip to main content

New Pacakge gnocl::cairo

The process of tidying up the development code prior to a release increment has led me to weeding out some unused or difficult to maintain functions. One of these was the cairo.c module. This was experimental block of code which was an offshoot of developing the gnocl::splashscreen widget.  But, with the transition to Gtk3 on the horizon, all drawing operations will be performed by Cairo and so I thought that it was a good opportunity to make use of some of that old code. Hence, a new package. There's still way to go before it's finished and I'm still working on drawing to pixbufs but things are looking good. Here's the syntax for the command:

gnocl::cairo <drawable-id> -actions <script>

Where the script is simply a list of cairo operations.  Here's a snippet from my test script.

set actions "
# {sample set-line-join}
set_line_width 40.96
move_to {76.8 84.48}
rel_line_to {51.2 -51.2}
rel_line_to {51.2 51.2}
set_line_join miter
stroke

move_to {76.8 161.28}
rel_line_to {51.2 -51.2}
rel_line_to {51.2 51.2}
set_line_join bevel
stroke

move_to {76.8 238.08}
rel_line_to {51.2 -51.2}
rel_line_to {51.2 51.2}
set_line_join round
stroke
"
set pb(1) [gnocl::pixBuf new -width 512 -height 512]
gnocl::cairo $pb(1) -actions "$actions #"


This gives:



There will be some limitations. It's not possible to create several surfaces in advance and then to use them as required. There is only one surface and will be necessary to change its contents. I don't envisage implementing any introspection either, keeping track of what's taking place on the Cairo side of things will need to be handled Tcl-side. One change that I did make was to allow for angles to be specified in degrees rather than radians. I could make this optional with a -useDegree switch but that can be dealt with later.

Here's a list of the Cairo operations implemented so far. The names are derived from the Cairo api for which these are wraps.

        "image_surface_create_from_png",
        "paint",
        "line_to",
        "set_line_cap",
        "set_line_join",
        "rel_line_to",
        "rectangle",
        "arc",
        "arc_negative",
        "curve_to",
        "rel_curve_to",
        "stroke",
        "stroke_preserve",
        "set_source_rgb",
        "set_source_rgba",
        "fill",
        "fill_preserve",
        "set_dash",
        "set_line_width",
        "move_to",
        "pattern_create_linear",
        "pattern_add_color_stop_rgb",
        "pattern_add_color_stop_rgba",
        "set_source",
        "set_source_surface",
        "surface_destroy",
        "pattern_destroy",
        "select_font_face",
        "font_size",
        "show_text",
        "new_path",
        "close_path",
        "clip",
        "new_sub_path",
        "set_fill_rule",
        "scale",
        "rotate",
        "translate",
        "#"

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

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

Creating a button box with right aligned widgets

The dialog widget has its own internal functionaluty to create and position buttons at the bottom right corner of the window container. When creating these for ourselves it must be born in mind that default settings for fill and expand are both 0.5. Failing to set these will always place the child objects in the centre, regardless of alignment. For most cases these defaults are acceptable but, to create that dialog-button arrangement, use the following snippet as a model!   # to right align completely, set expand and fill to 0 set hbox [gnocl::hBox] set b1 [gnocl::button -text Select \                -data $lst                 -onClicked { puts DO-SOMETHING-WITH-%d} ] set b2 [gnocl::button -text Cancel -onClicked { puts DONE! } ] $vbox add $hbox -expand 0 -fill 0 -align right $hbox add $b1 $hbox add $b2