Can I load a Glade GUI file just like other Gtk language bindings? |
No, not at the moment though some support for Glade is a possibility. Glade produces an XML
file create a user interface module to which programmers
can attach callback routines in the language of their choice. The a description file is created which is parsed by the
libglade module loaded into the user application. The rationale behind
Gnocl was to create a module which worked in a way similar to Tk in
which much of the work of connecting widget events to callback
functions can be streamlined leaving the programmer to focus on the
task of applications programming. Should it be the case that a
programmer needs additional funcitonality for a particular widget which
is available as a Gtk library function, it would be more pragmatic to
implement this feature as either a gnocl widget option or command
enabling the code to become re-usuable, rather than causing it to
become fixed in application bound libraries.
|
Are my Tk scripts compatible with Gnocl? |
No. Gnocl is intended to
provide the programmer with the means of producing Gtk applications.
Whilst the command syntax is modelled after Tcl , the commands
themselves are incompatible. In some ways, Gnocl GUIs are simpler to
create than Tk.
|
What are the differences between TileGtk and Gnocl? |
TileGtk is an extension to the Tile themeing package used in
versions 8.x of Tk and later. Tile has been included in the Tk core as
a means of providing theme to the Tk widget set to make it more
visually appealing. In the case of TileGtk and TileQt, the widget
rendering engines of these environments are used to render Tk widgets.
The overall effect is to beatify Tk. Gnocl on the other hand, is a
straightforward binding to the Gtk/Gnome widget set complete with the
features and bindings expected from Gnome compliant applications.
|
What are the major differences between the Tk and Gtk/Gnome widget sets? |
|
When should I choose to use Gnocl as against Tk?
|
In brief, if a programmer want to
develop genuinely Gtk./Gnome compliant applications the use Gnocl.
However, if an existing Tk application needs to look at home on a Gnome
desktop use Tk and modify it to use the Tilegtk theme.
|
Does Gnocl work in conjunction with Tk? |
Yes. Gnocl supports the creation of plugs and sockets which enables widgets to be embedded in Gnocl windows.
|
Are there Windows and MacIntosh versions of Gnocl? |
If
there's a Gtk port for a particular platform then its possible to
create a version of Gnocl for that platform. At present a version
exists for Microsoft windows (courtesy of XXXX) and for Maemo, running
on Nokia XXX, internet tablets (courtesy of XXXX). At present there is
no MacIntosh version of Gnocl.
|
How easy is it to extend the Gnocl widget set? |
Implmenting
new widgets in Gnocl is not difficult, but is time consuming in order
to create the support code for the various properties, set up of
signals management and the creation of commands. The best way to tackle
solution of
|
How does Gnocl differ from other Gtk language bindings such as PyGtk and RubyGtk? |
Most bindings act a wrapper around the Gtk library using a process
similar to SWIG. The programmer can then, using their chosen scripting
language create widgets, connect signals to callback functions and
access the Gtk environment. Gnocl, on the other hand, isolates the
programmer from the innards of the Gtk/Gnome libraried by providing a
higher level of abstraction. Rather than leaving programmers to
re-create much of the signal managments functions for their new
applications, Gnocl takes the command language approach, where signals
and callbacks can be created or configured in compound calls. The
option and commands terms for the Gnocl widgets themselves, generally
reflect the nomenclature of the Gtk libraries so that those programmers
more familiar with the Gtk library will be able to get an idea of which
option of call relates to its Gtk equivalent.
|
How can I contribute to the development of Gnocl? |
|