tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Longman <glong...@gmail.com>
Subject Re: [jira] Assigned: (TAPESTRY-165) Adding a namespace for the Tapestry tags
Date Tue, 08 Feb 2005 20:26:02 GMT
I had Jira to resend me my password.. but it has not shown up yet and
I wanted to chime in on this...

While on the surface TAPESTRY-165 appears to be innocuous, I think
this should not be done.

The first goal of having validatable documents at edit time is an
admirable goal but probably not obtainable anyways in the case where
implicit components are used.

ie. 

<span jwcid="@MyCustomComponent" someXhtmlViolatingAttr="ognl:AParamterValue"/>

where 'someXhtmlViolatingAttr' is of course a parameter defined in
MyCustomComponent.jwc

The above example will not validate for two reasons: 'jwcid' is not a
valid attribute for span, and because 'someXHtmlViolatingAttr'  also
is not.

Taking the step requested in TAPESTRY-165....

<span tap:jwcid="@MyCustomComponent"
someXhtmlViolatingAttr="ognl:AParamterValue"/>

 solves the first problem but not the second one. The second problem
can't be solved in this way.

So why bother at all. We will end up with templates that will not
validate as XHTML regardless.

Geoff


On Tue, 8 Feb 2005 21:00:24 +0100 (CET), Howard M. Lewis Ship (JIRA)
<tapestry-dev@jakarta.apache.org> wrote:
>      [ http://issues.apache.org/jira/browse/TAPESTRY-165?page=history ]
> 
> Howard M. Lewis Ship reassigned TAPESTRY-165:
> ---------------------------------------------
> 
>     Assign To: Howard M. Lewis Ship
> 
> > Adding a namespace for the Tapestry tags
> > ----------------------------------------
> >
> >          Key: TAPESTRY-165
> >          URL: http://issues.apache.org/jira/browse/TAPESTRY-165 
> >      Project: Tapestry
> >         Type: Improvement
> >   Components: Framework
> >     Versions: unspecified
> >  Environment: Operating System: All
> > Platform: All
> >     Reporter: Robert Hicks
> >     Assignee: Howard M. Lewis Ship
> >      Fix For: 3.1
> 
> >
> > From a discussion in the newsgroup I would like to request a feature. That
> > feature would be to change the way Tapestry embeds its tags from:
> > <span jwcid="insertStuff">this gets replaced</span>
> > To (something like this):
> > <span tap:jwcid="insertStuff">this gets replaced</span>
> > This allows for several things to happen. The first is that Tapestry now
> > create XHMTL compliant templates at EDIT time so that developers and HTML
> > coders can validate the XHTML. The second is more nebulous. But I believe the
> > change to using a namespace would allow Tapestry more flexibility as future
> > HTML changes come down the pipe to ensure Tapestry meets those specifications.
> 
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
> - 
> If you want more information on JIRA, or have a bug to report see:
>    http://www.atlassian.com/software/jira 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org 
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org 
> 
>

---------------------------------------------------------------------
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