[Seaside] Re: Why - XHTML perfectly good names are now given en Seaside new names

[Stuart Herring]

I guess the simplest answer to your original question is:
The reason Seaside does not use XHTML tag names as-is is because
Seaside is not a wrapper, it is an abstraction.

(X)HTML was designed to be transmitted as-is over a slow network,
therefore when considering the trade-off between readability and
brevity, the designers of HTML chose brevity as the most important
concern.

Seaside is a framework designed to be used by humans, that will not be
sent as-is over a slow network (instead it uses HTML to do that),
Therefore the compromise goes the other direction - human readability
is in this case more important than brevity.

The other consideration is that thinking in terms of tag names instead
of the concepts they represent is a very 1998 way of thinking of HTML.
 Semantic markup makes what the tags _mean_ more important than the
name of the tag, so in that way, Seaside's choice can also help
improve design.

On Sat, Feb 19, 2011 at 8:11 AM, Fritz Schenk
<intrader.intrader at gmail.com> wrote:
> Stuart, you are not getting the point. The names in XHTML (and HTML) are
> arbitrary of course, they could have chosen some thing else back in 1990.
> However, why give them alternate names that new Seaside users need now learn to
> use?
> Thanks
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>