You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martijn Dashorst <ma...@gmail.com> on 2007/09/13 00:56:47 UTC
Backbutton support library that is BSD licensed
http://codinginparadise.org/projects/dhtml_history/README.html
Not sure if it is any good, but it might be something worthwile to
look at. The license is a-ok, which is a good starting point.
They are moving the project to googlecode though.
Martijn
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
Re: Backbutton support library that is BSD licensed
Posted by Gerolf Seitz <ge...@gmail.com>.
cool, i saw this one actually 2-3 weeks ago
and just for the record:
YUI also provides a "Browser History Manager":
http://developer.yahoo.com/yui/history/
but since it depends on yui's yahoo.js and event.js, i guess it's a no go.
gerolf
On 9/13/07, Martijn Dashorst <ma...@gmail.com> wrote:
>
> http://codinginparadise.org/projects/dhtml_history/README.html
>
> Not sure if it is any good, but it might be something worthwile to
> look at. The license is a-ok, which is a good starting point.
>
> They are moving the project to googlecode though.
>
> Martijn
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.0-beta3 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
>
Re: Backbutton support library that is BSD licensed
Posted by Johan Compagner <jc...@gmail.com>.
many ajax frameworks (look for example how gmail works)
have backbutton support even if they are full ajax. You can trick the
browser
by giving it a new hash in the history or something like that.
johan
On 9/13/07, Julian Klappenbach <jk...@gmail.com> wrote:
>
> Do we have a good writeup on the cases that we'd need to handle with back
> button handling? I can see a case for non-Ajax related navigation. But
> for
> Ajax? if you start a fresh browser instance with a link to a completely
> Ajaxified application, the back button will never come into play. That's
> because, by default, the back button is disabled on a new instance. The
> back button only becomes active when a normal URL request is issued. But
> the execution of an Ajax call does not change the back button state. In
> fact if every operation involved Ajax, the back button would never become
> active during the span of a session.
>
> Am I missing something here? I brought this up before (Ajax + back
> button),
> to find that the thread of conversation just died. Perhaps I had a point
> that people had overlooked.
>
> And in the case of a standard browser URL request, we have the page map,
> which is meant to solve the back button issue with non-Ajax request
> navigation histories. So, even if an Ajax application emits the
> occasional
> standard request, the application should handle this navigation through
> currently provided services.
>
> Again, am I missing something?
>
> -jjk
>
Re: Backbutton support library that is BSD licensed
Posted by Julian Klappenbach <jk...@gmail.com>.
Do we have a good writeup on the cases that we'd need to handle with back
button handling? I can see a case for non-Ajax related navigation. But for
Ajax? if you start a fresh browser instance with a link to a completely
Ajaxified application, the back button will never come into play. That's
because, by default, the back button is disabled on a new instance. The
back button only becomes active when a normal URL request is issued. But
the execution of an Ajax call does not change the back button state. In
fact if every operation involved Ajax, the back button would never become
active during the span of a session.
Am I missing something here? I brought this up before (Ajax + back button),
to find that the thread of conversation just died. Perhaps I had a point
that people had overlooked.
And in the case of a standard browser URL request, we have the page map,
which is meant to solve the back button issue with non-Ajax request
navigation histories. So, even if an Ajax application emits the occasional
standard request, the application should handle this navigation through
currently provided services.
Again, am I missing something?
-jjk
Re: Backbutton support library that is BSD licensed
Posted by Eelco Hillenius <ee...@gmail.com>.
On 9/12/07, Martijn Dashorst <ma...@gmail.com> wrote:
> Sure, but saving cycles on the client side so we can focus on the
> server side is a bad thing?
Not really, but having an extra dependency might. It's moot anyway as
long as we don't have a solution for syncing server-side.
Eelco
Re: Backbutton support library that is BSD licensed
Posted by Martijn Dashorst <ma...@gmail.com>.
Sure, but saving cycles on the client side so we can focus on the
server side is a bad thing?
Martijn
On 9/13/07, Eelco Hillenius <ee...@gmail.com> wrote:
> On 9/12/07, Martijn Dashorst <ma...@gmail.com> wrote:
> > http://codinginparadise.org/projects/dhtml_history/README.html
> >
> > Not sure if it is any good, but it might be something worthwile to
> > look at. The license is a-ok, which is a good starting point.
>
> But our problem is not that we don't know how to do this in the
> client. Our main hurdle is that we need to synchronize with the
> server-side in such a way that normal requests keep working as well.
>
> Eelco
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
Re: Backbutton support library that is BSD licensed
Posted by Eelco Hillenius <ee...@gmail.com>.
On 9/12/07, Martijn Dashorst <ma...@gmail.com> wrote:
> http://codinginparadise.org/projects/dhtml_history/README.html
>
> Not sure if it is any good, but it might be something worthwile to
> look at. The license is a-ok, which is a good starting point.
But our problem is not that we don't know how to do this in the
client. Our main hurdle is that we need to synchronize with the
server-side in such a way that normal requests keep working as well.
Eelco