You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship" <hl...@comcast.net> on 2004/01/19 18:38:38 UTC
RE: Losing posts to tapestry-user, tapestry-dev
Thanks! I'll do that in the future. I think I've only noticed this recently because I'm working at
home and have fewer distractions.
Tapestry users: frustrated that a posting never showed up on the list? Sorry -- repost and it should
shoot right through!
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry/
http://javatapestry.blogspot.com
> -----Original Message-----
> From: Erik Abele [mailto:erik@codefaktor.de]
> Sent: Monday, January 19, 2004 12:32 PM
> To: Howard M. Lewis Ship
> Cc: Apache Infrastructure List
> Subject: Re: Losing posts to tapestry-user, tapestry-dev
>
>
> On 19.01.2004, at 18:21, Howard M. Lewis Ship wrote:
>
> > I'm the moderator for the tapestry-user and tapestry-dev
> mailing lists.
> >
> > Although I filter out quite a bit of spam, I also approve a
> number of
> > submissions a week.
> >
> > Something I only noticed recently, is that messages I approve don't
> > always show up.
> >
> > If a message appears to be legitimate, my standard procedure is to
> > reply-to-all and remove all but
> > the "allow-tc" email address.
>
> Uhmm, you should also keep the "accept-" address. The "allow-tc" is
> only for future postings, afaik.
>
> Cheers,
> Erik
>
> > I'm not seeing these messages appear in the -user and -dev lists,
> > however.
> >
> > Is there any way I can see what is going on inside ezmlm?
> >
> > --
> > Howard M. Lewis Ship
> > Independent J2EE / Open-Source Java Consultant
> > Creator, Tapestry: Java Web Components
> > http://jakarta.apache.org/tapestry/
> > http://javatapestry.blogspot.com
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: replacing jwcid with XPath
Posted by Harish Krishnaswamy <hk...@comcast.net>.
Seems like an interesting idea.
-Harish
Jim Frederic wrote:
> I love the purity of the html in Tapestry templates.
> What about going a step further and removing (or making optional)
> the jwcid, replacing with XPath. For example:
>
> current .html:
> <a jwcid="loginLink" href="">Login</a>
>
> current .jwc (or .page):
> <component id="loginLink" type="PageLink">
> <static-binding name="loginLink" value="LoginPage"/>
> </component>
>
> proposed .html:
> <a id="loginLink" href="">Login</a>
>
> current .jwc (or .page):
> <component xpath="//a[@id='loginLink']" type="PageLink">
> <static-binding name="loginLink" value="LoginPage"/>
> </component>
>
>
> The main difference is the HTML is now completely pure. This could
> also remove the need for the copy-of attribute in the <component>
> element, since the XPath expression could resolve to multiple HTML
> elements.
>
> ---
> Jim Frederic
> Innodata Isogen
> 9390 Research Blvd
> Kaleido I, Suite 410
> Austin, TX 78759
> Tel: +(1) 512.372.8841
> Fax: +(1) 512.372.8133
> Web: http://www.innodata-isogen.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: replacing jwcid with XPath
Posted by Programozás <pr...@hotmail.com>.
I think that the current solution is more simple and readable for simple
cases (like your example), if there will be such a feature, it should be
only optional.
N.
----- Original Message -----
From: "Jim Frederic" <jf...@innodata-isogen.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Monday, January 19, 2004 6:52 PM
Subject: replacing jwcid with XPath
> I love the purity of the html in Tapestry templates.
> What about going a step further and removing (or making optional)
> the jwcid, replacing with XPath. For example:
>
> current .html:
> <a jwcid="loginLink" href="">Login</a>
>
> current .jwc (or .page):
> <component id="loginLink" type="PageLink">
> <static-binding name="loginLink" value="LoginPage"/>
> </component>
>
> proposed .html:
> <a id="loginLink" href="">Login</a>
>
> current .jwc (or .page):
> <component xpath="//a[@id='loginLink']" type="PageLink">
> <static-binding name="loginLink" value="LoginPage"/>
> </component>
>
>
> The main difference is the HTML is now completely pure. This could also
> remove the need for the copy-of attribute in the <component> element,
> since the XPath expression could resolve to multiple HTML elements.
>
> ---
> Jim Frederic
> Innodata Isogen
> 9390 Research Blvd
> Kaleido I, Suite 410
> Austin, TX 78759
> Tel: +(1) 512.372.8841
> Fax: +(1) 512.372.8133
> Web: http://www.innodata-isogen.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: replacing jwcid with XPath
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
It's an interesting idea. I do have a couple of problems.
You can't talke about the "loginLink" compoonent anymore, it's the long path to the component.
Sometimes you need to be able to access a component by its id in code [ getComponent("loginLink") ]
and that becomes problematic ... you end up with a component id (for use in code) and a component
xpath (to identify its portion of the template).
Also, Tapestry HTML templates are allowed to be really, really, pooly formed. Missing close tags,
unquoted attributes, all sorts of stuff. It reflects the kind of HTML we see in the wild (i.e.,
coming from our HTML developers). The internal representation of most of the template is array of
char ... not anything remotely DOM-like.
So, this goes against the grain of Tapestry. Tapestry HTML markup is quite invisible, so if that
lone attribute (jwcid) really bothers you, you have to ask whether it is worth trading away the rest
of the benefits of Tapestry for that one problem.
It also leaves the problem of what to do with the id attribute in the template; Tapestry doesn't
simply use id because HTML (especially DHTML, client-side DOM, client-side JavaScript and so forth)
may need it.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry/
http://javatapestry.blogspot.com
> -----Original Message-----
> From: Jim Frederic [mailto:jfrederic@innodata-isogen.com]
> Sent: Monday, January 19, 2004 12:53 PM
> To: Tapestry users
> Subject: replacing jwcid with XPath
>
>
> I love the purity of the html in Tapestry templates.
> What about going a step further and removing (or making optional)
> the jwcid, replacing with XPath. For example:
>
> current .html:
> <a jwcid="loginLink" href="">Login</a>
>
> current .jwc (or .page):
> <component id="loginLink" type="PageLink">
> <static-binding name="loginLink" value="LoginPage"/>
> </component>
>
> proposed .html:
> <a id="loginLink" href="">Login</a>
>
> current .jwc (or .page):
> <component xpath="//a[@id='loginLink']" type="PageLink">
> <static-binding name="loginLink" value="LoginPage"/>
> </component>
>
>
> The main difference is the HTML is now completely pure. This
> could also
> remove the need for the copy-of attribute in the <component> element,
> since the XPath expression could resolve to multiple HTML elements.
>
> ---
> Jim Frederic
> Innodata Isogen
> 9390 Research Blvd
> Kaleido I, Suite 410
> Austin, TX 78759
> Tel: +(1) 512.372.8841
> Fax: +(1) 512.372.8133
> Web: http://www.innodata-isogen.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
replacing jwcid with XPath
Posted by Jim Frederic <jf...@innodata-isogen.com>.
I love the purity of the html in Tapestry templates.
What about going a step further and removing (or making optional)
the jwcid, replacing with XPath. For example:
current .html:
<a jwcid="loginLink" href="">Login</a>
current .jwc (or .page):
<component id="loginLink" type="PageLink">
<static-binding name="loginLink" value="LoginPage"/>
</component>
proposed .html:
<a id="loginLink" href="">Login</a>
current .jwc (or .page):
<component xpath="//a[@id='loginLink']" type="PageLink">
<static-binding name="loginLink" value="LoginPage"/>
</component>
The main difference is the HTML is now completely pure. This could also
remove the need for the copy-of attribute in the <component> element,
since the XPath expression could resolve to multiple HTML elements.
---
Jim Frederic
Innodata Isogen
9390 Research Blvd
Kaleido I, Suite 410
Austin, TX 78759
Tel: +(1) 512.372.8841
Fax: +(1) 512.372.8133
Web: http://www.innodata-isogen.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org