
Basic Installation instructions:

as GUBI currently doesn't support configure and/or autoconf/automake,
a simple Makefile is supplied that can easily be configured to most
peoples needs.
the machine type for wich you are about to compile GUBI can be entered
in Makefile.cnf where as normal code optimization and or DMALLOG defines
go into the normal Makefile.
you should be able to get GUBI up and running just by typing `make'
and starting it after successful compilation.


Usage:

GUBI supports several command line flags that will load/merge/save
*.gbc files and build source code for you. check out
gubi --help
since the GUI is currently under development, its documentation is
as well. ;)


Builing source files:

the source files that get build by GUBI are classified into
dynamic and static files. dynamic files change when the widget tree
or some else project specific data changes.
static source files will ever stay the same, no matter what project
will be output by GUBI (though they will certainly change if you alter
their template counter parts or if you use another release of GUBI).
therefore some (static) files are only written by GUBI if neccessary,
and some are overwritten each time GUBI puts out new source.
wether a specific source file will be outputted, skipped or
overwritten is determined by a rule in write_cond.txt.


NOT to do:
-	do not connect a gtk_widget_destroy() function to a "delete_event"
	if you want the widget to be destroyed on this window manager signal,
	connect it to gb_return_true().


Contacts:

if you have problems regarding compilation, fatal abnormal behaviour
or just simple questions on the usage, contact one of the authors (file
AUTHORS supplied with GUBI).
new releases of GUBI will be announced on the Gtk+ mailing list at
redhat.com, to subscribe:
mail -s subscribe gtk-list-request@redhat.com < /dev/null

and you can always check out whats new about GUBI on its homepage:
http://www.softhome.net/pub/users/timj/gubi/.
