Re: Imperative vs. Declarative programming

Hello,

> I've posted a short blurb about the benefits of separating 
> declarative code from imperative code:

   I just stumbled over a comment by Manish Jethani that touches on
the same theme. Manish writes:

   The "in" thing now is to put the UI description, including the
association of event handlers with their controls, into an XML file.
XUL, XAML, SwixML, .... The UI is separate from the logic.

 Mozilla, in particular, actually does all of its UI work in the XUL
layer. The event handlers are actually just JavaScript functions! The
execution doesn't go into Mozilla "core" (I mean the C++ code, the
components that make up the real Mozilla) until there's some real work
to be done. It's really fantastic.

  Now, haven't we come full circle? The UI in VB was a FMB (binary)
file. In VC++ it was a RES (binary again) file. They've just become
XML files now. :) Writing programming language code manually to set up
the UI never appealed to me.

   - Gerald

-------------------
Gerald Bauer

XUL Alliance | http://xul.sourceforge.net  
United XAML  | http://xaml.sourceforge.net