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

Boris Popov, DeepCove Labs boris at deepcovelabs.com
Thu Feb 17 23:35:44 UTC 2011


If you feel so strongly about it, this is what open source is all about:
make a package called Seaside-OldSchool and add things like
WARenderCanvas>>a and WARenderCanvas>>ul. I've done a ton of HTML before
Seaside as well and didn't really have any issues transitioning, because
expanded names actually make more sense in many cases (#a vs #anchor)
and are a lot more consistent (#url vs #href:/#src:).



-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Fritz
Sent: Thursday, February 17, 2011 6:29 PM
To: seaside at lists.squeakfoundation.org
Subject: [Seaside] Re: Why - XHTML perfectly good names are nowgiven en
Seaside new names

Stephan, I don't get your comment. 
What I meant, was that I have programmed web pages since 1992; pretty
close to its invention in 1990. It is most natural for me to jot a site
in vim and be done with it and make it Web2.0 with jQuery is most
Seaside offers a new language to generate html; and I was inquiring as
to whether 'old' users would just be more confused with the two ways to
generate html. 
Now, in Seaside we can 'say jQuery in Seaside' - but not quite, as when
importing html in a jQuery AJAX load action.


seaside mailing list
seaside at lists.squeakfoundation.org

More information about the seaside mailing list