Thanks, Bob. <br><br><div class="gmail_quote">On Mon, Feb 2, 2009 at 11:42 PM, Thomas Davie <span dir="ltr"><<a href="mailto:tom.davie@gmail.com">tom.davie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
On 3 Feb 2009, at 08:12, Achim Schneider wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
"John A. De Goes" <<a href="mailto:john@n-brain.net" target="_blank">john@n-brain.net</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Perhaps I should have been more precise:<br>
<br>
How do you define "layout" and "interaction semantics" in such a way<br>
that the former has a *necessarily* direct, enormous impact on the<br>
latter?<br>
<br>
HTML/CSS is a perfect example of how one can decouple a model of<br>
content from the presentation of that content. The developer writes<br>
the content model and the controller, while UX guys or designers get<br>
to decide how it looks.<br>
<br>
</blockquote>
HTML, or rather XML, would be layout to me. GUI's usually don't serve<br>
static content, and allowing a CSS layer to position eg. a filter GUI<br>
that supports chaining up any amount of filters by slicing them apart<br>
and positioning them on top of each other (maybe because someone didn't<br>
notice that you can use more than one filter) wrecks havoc on both<br>
usability and the semantics.<br>
<br>
"Wrecks havoc on the semantics" in the sense of that if a thing is<br>
editable, the semantics should guarantee that it is, indeed, editable.<br>
Likewise, if something is marked as visible (and such things are<br>
explicit in the model, not defined by an outer layer), the semantics<br>
should guarantee that it is visible.<br>
</blockquote>
<br>
<br></div>
I mostly don't get how a topic discussing how to do GUIs in a beautiful, consistent, composable, orthogonal, functional way got onto the topic of "oh hay, you could do it with html and css". Sure, those two may be declarative languages, but that doesn't make either of them fill the list of features required above!<br>
<br>
<br>
Bob<div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org" target="_blank">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br>