You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Paul Ferraro <pm...@columbia.edu> on 2004/04/09 02:49:05 UTC
[OFF-TOPIC] And the client gets thicker...
I came across this link today and thought that it might prove useful for
some Tapestry users and perhaps be leveraged by the contrib:Table component.
http://www.kryogenix.org/code/browser/sorttable/
In short, this simple, but clever technique leverages CSS and a couple
of static javascript functions to provide client-side sorting
functionality to any HTML table. Upon reading the documentation, I
imagined extending its functionality to support client-side pagination
through the use of invisible table rows. There are some obvious
limitations to this kind of client-side functionality, but I think its
benefits are equally obvious.
Thoughts?
Paul Ferraro
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
how a jsp file get parameters in Tapestry application
Posted by "julian.hu" <de...@hotmail.com>.
Dear All,
In my application, i want to use a little bit jsp program.
But there is a problem i can not resovle. How to transfer any
parameters from page to jsp? I tried using visit class,but it is
not work.
Julian
Re: [OFF-TOPIC] And the client gets thicker...
Posted by Matt Raible <li...@raibledesigns.com>.
No, not yet. I've thought about adding it - just haven't had the
motivation to do so.
Matt
On Apr 8, 2004, at 9:42 PM, Erik Hatcher wrote:
> On Apr 8, 2004, at 10:48 PM, Matt Raible wrote:
>> How about this one - it works in Safari. ;-)
>>
>> http://homepage.mac.com/mraible/demos/sortTable.html
>
> Nice! Do you use that in conjunction with displayTag?
>
>
>
> ---------------------------------------------------------------------
> 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: [OFF-TOPIC] And the client gets thicker...
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On Apr 8, 2004, at 10:48 PM, Matt Raible wrote:
> How about this one - it works in Safari. ;-)
>
> http://homepage.mac.com/mraible/demos/sortTable.html
Nice! Do you use that in conjunction with displayTag?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [OFF-TOPIC] And the client gets thicker...
Posted by Matt Raible <li...@raibledesigns.com>.
How about this one - it works in Safari. ;-)
http://homepage.mac.com/mraible/demos/sortTable.html
Matt
On Apr 8, 2004, at 8:25 PM, Erik Hatcher wrote:
> I've seen this trick before... XDoclet's documentation used to do this
> (I just checked, and the online stuff doesn't currently). I agree it
> would be a cool (optional) addition to the table component.
>
> The site you provided doesn't function as it should in Safari on the
> Mac. And IE on the Mac gives a JavaScript error when it attempts to
> remove a handler.
>
> What a sad world we live in where there is so much incompatibilities
> with browsers. Rich clients are the future! :)
>
> Erik
>
>
> On Apr 8, 2004, at 8:49 PM, Paul Ferraro wrote:
>
>> I came across this link today and thought that it might prove useful
>> for some Tapestry users and perhaps be leveraged by the contrib:Table
>> component.
>>
>> http://www.kryogenix.org/code/browser/sorttable/
>>
>> In short, this simple, but clever technique leverages CSS and a
>> couple of static javascript functions to provide client-side sorting
>> functionality to any HTML table. Upon reading the documentation, I
>> imagined extending its functionality to support client-side
>> pagination through the use of invisible table rows. There are some
>> obvious limitations to this kind of client-side functionality, but I
>> think its benefits are equally obvious.
>>
>> Thoughts?
>>
>> Paul Ferraro
>>
>>
>> ---------------------------------------------------------------------
>> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [OFF-TOPIC] And the client gets thicker...
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
I've seen this trick before... XDoclet's documentation used to do this
(I just checked, and the online stuff doesn't currently). I agree it
would be a cool (optional) addition to the table component.
The site you provided doesn't function as it should in Safari on the
Mac. And IE on the Mac gives a JavaScript error when it attempts to
remove a handler.
What a sad world we live in where there is so much incompatibilities
with browsers. Rich clients are the future! :)
Erik
On Apr 8, 2004, at 8:49 PM, Paul Ferraro wrote:
> I came across this link today and thought that it might prove useful
> for some Tapestry users and perhaps be leveraged by the contrib:Table
> component.
>
> http://www.kryogenix.org/code/browser/sorttable/
>
> In short, this simple, but clever technique leverages CSS and a couple
> of static javascript functions to provide client-side sorting
> functionality to any HTML table. Upon reading the documentation, I
> imagined extending its functionality to support client-side pagination
> through the use of invisible table rows. There are some obvious
> limitations to this kind of client-side functionality, but I think its
> benefits are equally obvious.
>
> Thoughts?
>
> Paul Ferraro
>
>
> ---------------------------------------------------------------------
> 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