🚀 go-pugleaf

In article <6us8bl$dt$14@blue.hex.net>
           cbbrowne@hex.net "Christopher Browne" writes:
> There are two main approaches to user-interface builders that are
> relevant here:
> 
> a) Template generator.
> 
> You drag'n'drop things into place to "prototype" a widget (or menu or
> screen or whatever). 
> 
> Click "compile," and code is generated for you to then use. 
> 
> If, horror of horrors, you have to customize the results, you can't push
> it back into the template generator; it's a one-way pipeline. 
> 
> b) GUI maintainer. 
> 
> This is the rather more complex approach.  This sort of system can
> handle "both directions." You slap components together to build GUI
> elements.  And the system generates code.   You then tune the code,
> running, testing, adding event handlers.

Also (c):

have a program that takes an ascii file as input, and produces as
output another ascii file, which contains the source code in a HLL
of the UI you have built. The input file will be a very-high-level
script defining the UI, eg something like:

Menubar [ 
   Menu "File" 
      ["New" "Open..." "Save" "Save as..."]
...etc...  


-- 
@@--Phil Hunt-----------------------------Don't fear the penguins(*)--@@ 
@@  [*] Disclaimer: this is FREE ADVICE, and is distributed in the    @@
@@  hope that it will be useful, but WITHOUT ANY WARRANTY; note also  @@
@@  that this advice may not apply if your name is Gates or Ballmer.  @@