On 28 Jun 2007, at 22:31, Miguel Arroz wrote:
The pager kicks ass, as it handles huge amount of data, using the
objectInRange stuff in Wonder to limit the resources usage.
Everything works like a charm. Except... when the user clicks the
evil back button.
There, two things happen:
Check out the backtracking code at http://www.bernard-web.com/pierre
Does exactly that.
On Jun 28, 2007, at 11:31 PM, Miguel Arroz wrote:
Hi!
Ok, this is a weird question. My problem is this: I implemented a
pager and a pager controller. (I know all this stuff is in Wonder,
but I'm a
Hi!
No. The problem is not the browser making the request or fetching
from its cache. The problem is that the pager component (and
controller) internal structures are always in the last state. ie,
imagine the controller has an array of the elements that are visible
on the current page.
That's all a matter of perspective. It may be easier to change your
perspective slightly than to rewrite your application :-). I'd say
that the vast majority of web applications, not just WO ones, work by
refreshing backtracked pages.
Paul
On 29 Jun 2007, at 15:19, Miguel Arroz wrote:
Another solution is to use Ajax. Then the back button goes back to
the previous page and not the previous batch.
Chuck
On Jun 29, 2007, at 7:19 AM, Miguel Arroz wrote:
Hi!
No. The problem is not the browser making the request or fetching
from its cache. The problem is that the pager
Hi!
Ok, this is a weird question. My problem is this: I implemented a
pager and a pager controller. (I know all this stuff is in Wonder,
but I'm a guy who needs to code to understand - see http://
rentzsch.com/notes/programmersDontLikeToCode).
The pager kicks ass, as it handles huge
