Peter Donald wrote: > > This can be generalized in an XML workflow language. Theres a few attempts in > opensource and commercial alike that attempt this. Many are even independent > of the rendering technology (ie XML vs Swing vs whatever).
Yes, and my personal pet idea is that the workflow modelling and the user interface modelling should be in the same XML language. I believe in data-driven applications, even though this idea is not very popular with users of procedural programming languages. Users of declarative programming languages have never written anything else than data-driven applications, so some mainstream people tend to ignore this concept. If we're talking about data-driven user interfaces (instead of layout-driven), then XML and XML Schema are of course a natural fit for the data that is supposed to drive things. Usually applications are divided into the three main concerns of logic, data and presentation. The problem is that in a "classic" app the GUI is really a bunch of custom and active logic that pulls data to fill in the blanks. In a data-driven application the GUI is a bunch of passive and generic logic and the data is pushed into it. Ulrich -- Ulrich Mayring DENIC eG, Systementwicklung -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
