
Isn't CSS about giving a "style" to the "views" in the model-view-controller
paradigm? So basically it is a way to change the look of a user interface,
without having to change the user interface definition itself.
But isn't this just an environment monad that has functions to convert a
model into a view (= geometry = render function + picking function)? Plugin
a different environment and voila, the widgets are painted and maybe even
layed differently, but you don't have to change any code or data....
Of course what a "model" really is, is not fully clear:
http://blogs.msdn.com/johngossman/archive/2005/10/08/478683.aspx
On Tue, Feb 3, 2009 at 8:50 PM, Jeff Heard
Similarly, I've been wondering what's at the core of a GUI? It seems in recent years that more people have been moving towards web-based applications, and away from traditional GUIs, so the meaning of them may be changing. The old question seemed to be Page vs. Control-Board, but that seems like implementation, when the real essence of a GUI is taking in common kinds of user input and displaying output in a sensible way. Similarly, there are more ways to interact with a computer than ever before, from simple keyboard up through multitouch interfaces like the iPhone. It would be cool to me to see a semantic model that captures this.
2009/2/3 Conal Elliott
: [Spin-off from the haskell-cafe discussion on functional/denotational GUI toolkits]
I've been wondering for a while now what a well-designed alternative to CSS could be, where well-designed would mean consistent, composable, orthogonal, functional, based on an elegantly compelling semantic model (denotational).
- Conal
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe