> So, I want to suggest a new approach for doing GUII dialogs:
> The dialogs structure and logiv will be defined by in a simple text file,
> and the dialogs will be built in run-time from these files.
If this simple text file resembles Tcl syntax you'll even get a fourth Gui
(Tk) for free ;-)
Andre'
PS: I am even a bit serious here, Tk is a painless port to Windows and the
Mac. I currently use something like
------------ snip -----------
...
{c algo {"_Algorithm" "_Algorithmen"}}
{x rel {"_Reliability" "Zuverlässigkeit"}}
{a {k rel value} {"Reliability value" "Zuverlässigkeitswert"}}
{a {k rel value_comp} {"... edge composition" "... Kantenkomposition"}}
{a {k rel value_dec} {"... decomposition" "... Dekomposition"}}
{s}
{a {k rel pol} {"Reliability polynomial" "Polynom"}}
{a {k rel pol_comp} {"... edge composition" "... Kantenkomposition"}}
{a {k rel pol_dec} {"... decomposition" "... Dekomposition"}}
{s}
{a rel_example1 {"Example" "Beispiel"}}
{u}
{x}
...
{u}
{d}
{c help {"_Help" "_Hilfe"}}
...
{d}
...
------------ snip -----------
for describing the GUI of my project. The 'a', 'c' ... etc are Tcl commands
and the description is simply sourced by a Tcl interpreter. I think it
can't possibly get much easier to add a menu entry than to open a text
editor and insert a single line...
Now that I think of it... adding a Tcl interpreter to some C/C++ program is
a nobrainer, and we have been looking for some built-in scripting language,
haven't we?
--
Andre' Poenitz ........................................ [EMAIL PROTECTED]
