On Sun, 13 Apr 2014 17:38:27 -0300, George Christman
wrote:
How do you think it will work with the back button? I'm assuming as soon
as you navigate away from the page and return with the back button your
going to lose your results?
As far as I know, back button usually doesn't work with
True. Ajax requests are not stored in the browser's history.
But this can be worked around by binding an action (ajax request) to an url
hash.
This can be done by using a javascript module such as jquery-ajax[1] (see
the demo[2]).
Never tested. Seems too intrusive and painfull for existing code bu
Yes, the back button will be broken. I think this is the case with all
Tapestry ajax interactions. There's a few javascript libraries that use
anchor URL's (#) and the javascript history api to support the back button.
I've never tried integrating any of these with tapestry. Perhaps this
deserves i
How do you think it will work with the back button? I'm assuming as soon as
you navigate away from the page and return with the back button your going
to lose your results?
On Fri, Apr 11, 2014 at 4:14 AM, Lance Java wrote:
> Perhaps Barry's solution could be applied to my pager component
> http
Perhaps Barry's solution could be applied to my pager component
http://tapestry-stitch.uklance.cloudbees.net/pagerdemo
The pager is driven by GridDataSource but allows you to render a page of
data however you like (ie in an list).
I wrote this one a few years ago. It's a mixin that you can attach to the
grid. It fetches more rows using the pagination links and adds them to the
page. This allows it to works the way Lance wants, it works with or without
javascript enabled. Most/all of the work is done by a jquery
lib
https:/
On Thu, Apr 10, 2014 at 5:04 AM, françois facon wrote:
The last time I tried Tap-Jquery it wasn't ready, I'll have to give it a
try again. I'm using beta-3, do you think it will still work with 3 too?
did you test the branch related to 5.4 ?
>
> According to
>
> https://github.com/got5/tapestry5
That's an interesting idea lance. It would be cool if we could detect js
before the page ever renders and serve up the appropriate UI. For the time
being I'd like to use this feature with mobile, but after reading some of
the side effects example the back button etc may prove very challenging.
On
did you test the branch related to 5.4 ?
According to
https://github.com/got5/tapestry5-jquery/blob/5.4/src/main/java/org/got5/tapestry5/jquery/components/PageScroll.java
and
https://github.com/got5/tapestry5-jquery/blob/5.4/src/main/resources/META-INF/modules/tjq/jscrollpane.js
this component s
Whatever the solution, I think it should gracefully degrade for crawlers /
bots etc. Ie initially render page links then replace page links with
infinite scroll if javascript is available.
On 9 Apr 2014 15:43, "George Christman" wrote:
> Hi Guys, has anybody happened to build an endless scroll c
Excellent, thanks Nourrdine, looks like we just need a 5.4 implementation
now :)
On Wed, Apr 9, 2014 at 10:57 AM, Nourredine K. wrote:
> Hi George,
>
> Taha's article should be a good start :
>
> http://tawus.wordpress.com/2012/11/25/scrolling-pages-tapestry5-onscrollbeyond/
>
> Also, check the
Hi George,
Taha's article should be a good start :
http://tawus.wordpress.com/2012/11/25/scrolling-pages-tapestry5-onscrollbeyond/
Also, check the PageScroll component's implementation in the
tapestry5-jquery module :
https://github.com/got5/tapestry5-jquery/blob/master/src/main/java/org/got5/tap
12 matches
Mail list logo
