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 Mon, 07 Mar 2005 07:48:18 GMT
I finally got around to testing this with a validating parser. In
MyEclipse the following validates fine...

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html >
<head>
</head>

<body 
   xmlns:t='http://jakarta.apache.org/tapestry/schema'
   t:jwcid="@Body">
<font face="Arial" t:jwcid="@Moo">This is my HTML page.<br>
</font>
</body>
</html>

and yes I would assume that the namespace declaration would need to be removed. 

Geoff


On Wed, 09 Feb 2005 16:37:11 +1100, Richard Lewis-Shell
<rlewisshell@mac.com> wrote:
> If it was a proper XML namespace, the prefix would be configurable per
> template.  eg. could be jwc:id, jwc:size.  Though is it valid XML to mix
> attributes and elements from different namespaces?  I suspect not :-(
> 
> jwc: as a prefix seems clearer (more obviously Tapestry) to me than
> either t: or tap: given that we are used to using jwcid now, and that
> components tend to use a .jwc file extension, but if XML namespaces
> allowed this, it would be up to the template developer to use whatever
> suited them.  Which is quite nice really.  If XML namespaces didn't
> allow this, I guess the prefix could be a .application|.library
> configuration property or something similar.
> 
> [If it is valid XML to mix elements and attributes from different
> namespaces] If we did use a Tapestry namespace, would we strip out that
> namespace declaration when rendering?  There would presumably be no
> Tapestry elements/attributes left in the rendered output.
> 
> Richard
> 
> Jamie Orchard-Hays wrote:
> > t:id? t:size?
> >
> > How about:
> > tap:id & tap:size
> >
> > Or are you guys just using shorthand?
> >
> > Jamie
> > On Feb 8, 2005, at 11:24 PM, Richard Lewis-Shell wrote:
> >
> >> In general, I think the informal/formal parameter attribute should
> >> take precedence.  But the t:id attribute should probably not take
> >> precedence over an id attribute - of course t:id (the component id) is
> >> not really a component parameter, so saying parameter attributes take
> >> precedence would technically be OK.
> >>
> >> Howard Lewis Ship wrote:
> >>
> >>> Interesting idea ... that we should define a namespace prefix.  Hm ...
> >>> what about conflicts?
> >>> <img t:id="@Image" size="20" t:size="100"/>
> >>> I guess the t: should take precedence.
> >>> On Wed, 09 Feb 2005 09:17:13 +1100, Richard Lewis-Shell
> >>> <rlewisshell@mac.com > wrote:
> >>>
> >>>>> 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.
> >>>>
> >>>>
> >>>> If prefixing the jwcid is OK, then why wouldn't the same prefix be
> >>>> added
> >>>>  to the other tapestry attributes?
> >>>> eg.
> >>>> <span tap:jwcid="@MyCustomComponent"
> >>>> tap:someXhtmlViolatingAttr="ognl:AParamterValue"/>
> >>>>
> >>>> Richard
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> 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 
> >>
> >
> >
> > ---------------------------------------------------------------------
> > 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 
> 
>

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