Skip to main content

gnocl::richTextToolBar -working version ready...

Not working on any academic research over the past few days has given me time to focus on completing the implementation of a simple pango/html rich text edit widget. GtkHtml was one route to take but this is being phased out in favour of WebkitGtk (besides, GtkHtml documentation of any work simply doesn't exist). After hacking together an editor using the webKitGtk, which itself is something of a work around, I modified the existing gnocl webkit package to offer all the basic functionality of a simple html doc editor. But, this required implementing Javascript calls in C procs which were then called through a Tcl front end! Apart from the package taking a second or two to load, I found that webkitGtk will tend to crash after a while. Not much use to me! My aim is to create markup strings which can also be used for display within Gtk+ widgets during run-time, i.e. marked up labels or list entries. As a glance through previous blog postings will show, I had already put together some basics, exploring the task from both the Tcl and C side of things. At the end of the day, I coded the whole lot in C and it now works fine although some care needs to be taken when applying background colours. Needless to say, if there is an error in the pango markup then this won't cause a crash as the returned text will be stripped of any markup. Along with the editor, there's also a html-source viewer.

As the widget item name suggests, this is basically a toolbar, if the -text option is set, then any pre-existing text widget can be used.

Here's a snapshot and the script that created it.
#--------------------------
# test_gtk_richTextToolBar.tcl
#--------------------------
#!/bin/sh
#\
exec tclsh "$0" "$@"

 package require Gnocl

 set txt [gnocl::text -wrapMode word -markupTags 1 -baseFont {Sans 14}]
set app(rtbar) [gnocl::richTextToolBar -text $txt -textAccelerators 1 ]

 $txt configure -onChanged {
           $app(rtf,lab1) configure -text [$txt getMarkup start end]
           }
   
set vbox [gnocl::vBox]

 set app(rtf,lab1) [gnocl::label -useMarkup 1 -justify left -align topLeft  -wrap 1 ]
set eb1 [gnocl::eventBox -child $app(rtf,lab1) -background white ]

 $vbox add $eb1 -fill {1 1} -expand 1
$vbox add $app(rtbar)
$vbox add $txt -fill {1 1} -expand 1

 gnocl::window -child $vbox -setSize 0.4


Comments

Post a Comment

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
7 comments
Read more

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.
6 comments
Read more

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
Post a Comment
Read more