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

[Stuart Herring]

I guess the problem here is making the assumption that the XHTML tag
names are "perfectly good".
The alternative position is  that they're not.

Really, what is an "a"?  It's just a letter, and what does "href" even mean?
The XHTML spec doesn't introduce the <a> tag by saying "This is an
'A'", it says it's an Anchor, which is represented in an XHTML
document as an 'a'.
Seaside is not XHTML, it emits XHTML, so why should the human
interface (Seaside source code), use a Machine interface (XHTML) as
its language?  It makes far more sense to use the human terms rather
than the machine terms for something that is going to be used by
humans.

That's how I see it, anyway.  I understand that when you're used to
dealing directly with HTML that having to find out the seaside terms
adds a bit of a learning curve, but only because the tools you've used
in the past have forced you to deal directly with the machine
representation.  I guess the easiest way to adapt is to stop thinking
in terms of the characters used in HTML, but instead think in terms of
the actual words the characters represent.

Regards,
Stuart


On Thu, Feb 17, 2011 at 2:21 PM, Fritz Schenk
<intrader.intrader at gmail.com> wrote:
> I don't think that the decision of using new names (for example paragraph for
> <p>) is such a good idea.
>
> Why was it done?
>
> Thanks
>
> P.A. Wow the captcha for this post is 'crusade'
>
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>