If my understanding of 508 is correct, you merely have to provide the
same service for everyone. That doesn't mean it has to look the same
for everyone. With my solution, all of the results are on the page. If
the user doesn't have javascript enabled, it is likely they either don't
have stylesheets enabled, or are smart enough to turn them off (you
would have to tell them this, of course), in which case, all the the
results show up. If you use the links right, you can have anchors in
the html for each "page" of results, so that <a href="#page3"
onclick="show('page3'); return false;" onkeypress="show('page3'); return
false;">3</a> could be worked to either show the page3 div if the user
has javascript, or jump to the page3 anchor (at the top of the page3
div) if the user does not. Another option would be to put
<noscript><input type="hidden" name="nojs" value="true" /></noscript> on
the search page so that if javascript isn't enabled, you can key off of
that value to display results in another way (if the number of results
is not astronomical, perhaps forego pagination?). A lot of this would
come down to who the project is for and how important branding is as
well.
Chris
> -----Original Message-----
> From: Dustin N. Jenkins [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 09, 2005 11:03 AM
> To: [email protected]
> Subject: Re: Pagination with dynamic XML (Was How-to CForms
> with Pagination)
>
> Thanks for the reply Chris, it's appreciated. I really like
> the idea too, but unfortunately we're trying to be 508
> compliant, which means we can't afford JavaScript. Again,
> thanks though.
>
> It'd be nice to be able to have a loop with a continuation
> kind of thing, but I don't see that working with the existing
> Pagination setup.
>
> Dustin
>
>
>
> Chris Marasti-Georg wrote:
>
> >I have a project where the searches can sometimes take a few
> seconds,
> >and are run as Xqueries in an eXist database. Since the
> search returns
> >all of the results, it doesn't make sense to hit the
> database with the
> >same search each time the user wants to view the next page
> of results.
> >If you have control over the users setup, and can afford a
> >css/javascript solution, I'd just make each "page" of results a div,
> >set them all to display:none, and use js to show/hide the page the
> >users wants.
> >
> >Chris
> >
> >
> >
> >>-----Original Message-----
> >>From: Dustin N. Jenkins [mailto:[EMAIL PROTECTED]
> >>Sent: Wednesday, June 08, 2005 4:47 PM
> >>To: Cocoon Users Group
> >>Subject: Pagination with dynamic XML (Was How-to CForms with
> >>Pagination)
> >>
> >>Sorry for reposting like this, but I wanted to simplify it
> a bit as my
> >>frustration is growing fast and I wanted to try and get feedback
> >>faster.
> >>
> >>In all the examples of Pagination I've seen, there's always been a
> >>static file to refer to as the source, but in my case my paginated
> >>list will vary. So I guess my question now is, has anybody
> gotten the
> >>Pagination to work as expected? I suppose writing my own
> wouldn't be
> >>all that hard, but I don't like rewriting something that exists
> >>already.
> >>
> >>Many thanks again,
> >>Dustin
> >>
> >>------------------------------------------------------------
> ---------
> >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
