The list below provides an overview of the current gnocl::abiwidget commands and any relevant subcommands. Looking at the abiwidget source code shows that there are no 'properties' as typically associated with Gtk+ widgets. This is understandable really as what appears to be here is access to the functionality branched into from the Abiword control loop. This is great as it results in speedy completion of this package. What is strikingly apparent is that there are (at least so far anyway) no options. Nor are there any styles. In practical terms this is a megawidget. Certain functionality is not directly obvious, print for example, but the default Abiword key bindings are still in place (Ctrl-P for instance will bring up the print dialog). Unless something else turns up when I read through the code, then such functionality might be evoked using a signal emit. Interestingly, I found no 'clear' function. Ctrl-N will result in a fully rendered Abiword window!
The next step for me is to implement signal handlers. These were probably set up for the management of toggle buttons etc. As there are are only three signal callback prototypes, again I think that this will be simple to complete.
As detailed documentation for the Abiwidget is practically none-existent, the behaviour of some of these commands needs a little more observation before deciding what's actually happening. Most of them, however, are self-explanatory.
o load
o save
o clear (stub-only)
o class
o delete
o undo
o redo
o cut
o copy
o paste
o subcommand
special
o align
o subcommand
center
justify
right
left
o select
o subcommands
all
block
line
word
bob
bod
bol
bow
eob
eod
eol
eow
left
right
nextLine
pageDown
prevLine
screenDown
screenUp
to
o erase
o subcommands
bob
bod
bol
bow
eob
eod
eol
eow
left
right
o insert
o subcommands
data
space
table
image
o edit
o subcommands
header
footer
o file
o subcommands
open
save
o remove
o subcommands
header
footer
o toggle
o subcommands
bold
underLine
bottomLine
insertMode
italic
overLine
plain
strike
sub
super
topLine
unindent
bullets
numbering
o view
o subcommands
marks
print
normal
onLine
o moveto
o subcommands
bob
bod
bol
bop
bow
eob
eod
eol
eow
left
right
nextLine
nextPage
nextScreen
prevLine
prevPage
prevScreen
o zoom
o subcommands
whole
width
o set
o subcommands
showMargin
wordSelections
fontName
fontSize
style
textColor
zoom
page
authors
o get
o subcommands
showMargin
wordSelections
fontNames
zoom
page
pageCount
pointer
authors
o find
o subcommands
string
prev
next
The next step for me is to implement signal handlers. These were probably set up for the management of toggle buttons etc. As there are are only three signal callback prototypes, again I think that this will be simple to complete.
As detailed documentation for the Abiwidget is practically none-existent, the behaviour of some of these commands needs a little more observation before deciding what's actually happening. Most of them, however, are self-explanatory.
o load
o save
o clear (stub-only)
o class
o delete
o undo
o redo
o cut
o copy
o paste
o subcommand
special
o align
o subcommand
center
justify
right
left
o select
o subcommands
all
block
line
word
bob
bod
bol
bow
eob
eod
eol
eow
left
right
nextLine
pageDown
prevLine
screenDown
screenUp
to
o erase
o subcommands
bob
bod
bol
bow
eob
eod
eol
eow
left
right
o insert
o subcommands
data
space
table
image
o edit
o subcommands
header
footer
o file
o subcommands
open
save
o remove
o subcommands
header
footer
o toggle
o subcommands
bold
underLine
bottomLine
insertMode
italic
overLine
plain
strike
sub
super
topLine
unindent
bullets
numbering
o view
o subcommands
marks
normal
onLine
o moveto
o subcommands
bob
bod
bol
bop
bow
eob
eod
eol
eow
left
right
nextLine
nextPage
nextScreen
prevLine
prevPage
prevScreen
o zoom
o subcommands
whole
width
o set
o subcommands
showMargin
wordSelections
fontName
fontSize
style
textColor
zoom
page
authors
o get
o subcommands
showMargin
wordSelections
fontNames
zoom
page
pageCount
pointer
authors
o find
o subcommands
string
prev
next
Comments