[Jakarta Tapestry Wiki] Updated: SimplifiedSpecificationsProposal

[ta...@jakarta.apache.org]

   Date: 2004-10-05T12:34:25
   Editor: HowardLewisShip <hl...@apache.org>
   Wiki: Jakarta Tapestry Wiki
   Page: SimplifiedSpecificationsProposal
   URL: http://wiki.apache.org/jakarta-tapestry/SimplifiedSpecificationsProposal

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -64,7 +64,7 @@
 
 The example also shows a long format binding, ({{{class}}}), is represented.
 
-== <inherited-binding> ===
+== <inherited-binding> ==
 
 In Tapestry 3.1, all component parameters will have a connected parameter property (see the ComponentParametersProposal). 
 This will eliminate the need for the {{{<inherited-binding>}}} element.
@@ -162,3 +162,11 @@
 
 That is, inside a {{{<component>}}} element, each element identifies a parameter of the component to bind.  Saves a small amount of typing.  Abandoning the DTD will allow other changes, such
 as changing {{{<page-specification>}}} to {{{<page>}}} and {{{<component-specification>}}} to {{{<component>}}}. That is, we have much more freedom to interpret elements based on context ({{{<component>}}} as a root element is different than {{{<component>}}} as a child element).
+
+== Status ==
+
+The work on <binding> has taken place (including removal of <static-binding>, <message-binding> and <inherited-binding>).
+
+<service> has been removed.  A warning has been added for use of <service> in a 3.0 DTD specification.
+
+Geoff threatened to kill me if I eliminated the DTD entirely. This was not unexpected.

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