tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Howard Lewis Ship <hls...@gmail.com>
Subject 3.1 Status / progress / thoughts
Date Tue, 05 Oct 2004 17:30:51 GMT
I'm just about ready to check in the first interesting changes for 3.1.

Just started introducing the 3.1 DTD.



<inherited-binding>, <static-binding>, <message-binding> have gone
away (still valid if you use the 3.0 DTD).

<binding> is now <binding name="..." value="..."> or <binding
name="..."> .... </binding>

You now use prefixes in the spec exactly the same as in the HTML
template. Consistency!

Example:

<component id="loop" type="Foreach">
  <binding name="source" value='ognl:items"/>
  <binding name="value" value="ognl:item"/>
  <binding name="element" value="tr"/>
</component>

<service> has gone away; you now need to do services from inside
HiveMind. 3.0 DTDs that use service will see a warning.

So, you can see, that I'm trying to simplify, streamline and improve
consistency in the specs.

One thing I would like dearly to do is make a few broader changes:

<property> (3.0) --> <meta> (3.1)  [[ for defining meta-data ]]
<property-specification> (3.0) --> <property> (3.1) [[ for adding
properties to a class ]]

I think it's much neater, and if this was 1.0, there would be no
question.  But it's 3.1 ... will this throw users too much?

Perhaps we support both <property> and <property-specification> in
3.1, as a transition towards <property>?

-- 
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message