[Seaside] Re: Why - XHTML perfectly good names are now given
en Seaside new names
sebastian at flowingconcept.com
Thu Feb 17 23:36:51 UTC 2011
I prefer 100 gazillion times to fail at that (or implement an autocompleter that includes an html2tag glossary) than to break the intuitive consistency of the trade off I've mentioned.
That trade off may work for you or not.
By the way what's the alternative?
To prioritize and overrate irrelevant details?
I'm not inspired to do software by <a>'s I'm inspired to put anchors (the concept) where matters. The details comes after that. Whatever comes after that. I can be talking of something that is two centuries after deprecating html and be perfectly useful and intuitive except for the details.
Seaside gives you the luxury of rendering (like painting) your application's concepts using html as the accidental brush you have at hand right now. You can decide to take that at your advantage looking at it that way (or inefficiently try to use it as hammer and feel frustrated).
On Feb 17, 2011, at 7:36 PM, Fritz Schenk wrote:
> Sebastian, you say a 'decent autocompleter';
> To say <a> and its attributes you have to say anchor. The autocompleter does not
> say anything else about callback, url, attributes, etc.
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside