easing WO pain
easing WO pain
- Subject: easing WO pain
- From: Jason Jobe <email@hidden>
- Date: Thu, 1 Nov 2007 09:46:18 -0400
As I am new to using Eclipse and WOLips I don't know yet if this is a
good or bad idea but I figured I'd toss it out there anyway.
I have done a bit of work in-house using an ObjC implementation of a
parser/handler for the Tagged Attribute Language (TAL) (first
introduced in Zope - http://wiki.zope.org/ZPT/TALSpecification14).
The bottom line is that I really prefer it to anything other template
syntax I have seen for dealing with (X)HTML.
One of its primary attributes is that the template can be displayed
in a browser *without* any preprocessing. Unknown attributes of a tag
are simply ignored AND can also have their own namespace(s). I
believe Dreamweaver and most other HTML editors will preserve said
attributes.
Essentially the difference is illustrated thusly:
(Don't ping for faulty syntax :-) I still learning the other options)
HTML
<a href="http://apple.com";>Apple<a>
WO
<wo:link href="http://apple.com";>Apple</wo:link>
or
<webobject name="Link1">Apple</webobject>
Link1 : WOLink {
href = theURL;
}
TAL
<a href="http://apple.com"; tal:attributes="href theURL">Apple</a>
The TAL representation will still render as a working link; the href
is given "default" value that will be replaced by the TAL processing
phase. This technique makes it much easier to mark up an HTML mockup
without destroying the original ability to edit or render.
PS - there are other implementations including one in Java
Additional Links
http://en.wikipedia.org/wiki/Template_Attribute_Language
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden