an idea how to keep things clean and consistent here: use simple "namespaces"
at dialog names, and also use same "namespace" at all widgets + other data that
relates to the same dialog.

for example: we have a dialog with a name "f1_dialog_openfile". now we should
name it's components for example "f1_label_text" and "f1_entry_filename". GLADE
will generate default names for widgets like "button1" or "label5" but using
those seems to lead into a complete mess sooner or later...

so, we could use for example the following "namespaces":
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

"f" -> file operations related
"e" -> engine-class setup related
"a" -> algorithms-related stuff
"t" -> trajectories etc...

and perhaps

"p" -> preferences-related???

how to rebuild GLADE code and keep old modifications:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

the code under target3/ contains the modified versions, and code under
target3/glade/src contains the original versions. THE VERSIONS SHOULD BE KEPT
IN SYNC FOR FUTURE UPDATES!!! a rough rebuild-procedure is following:

1) cd target3/glade/src
2) make diffs <will store current modifications to diff files.>
3) <start GLADE and rebuild the source; the modifications are now lost.>
4) cp main.c main.cpp; make <this will test the GLADE code; RECOMMENDED!>
5) mkdir zzz; cp * zzz <make backups of everything, just in case...>
6) make update <copies new source to target3/ and applies the patches.>
7) <if (or when) something at step 6) fails, update the changes manually.>
