[Prototype-core] Re: Prototype Pagination

2007-10-18 Thread Matt Foster

Hey Mislav,

Given that this is a forum dedicated to core improvements to
prototype you're correct in that this isn't perfectly suited to the
topic.  On the other hand this forum is probably the biggest hub for
prototype developers, and if not in mass than certainly in talent.
Given that, this is exactly the audience I am attempting to attract.
If the audience finds my monthly posts to be offensive I will cease
such activity because that is not going to draw positive attention.

The disclaimer aside, thanks for the response it is good to hear some
feedback.  Pagination in nature is typically server side which makes a
lot of sense.  For quite a few reasons though i have found client side
pagination to be really useful.  Creating a Google Gadget that
displayed an RSS feed in pagination form was pretty fun and given the
result set wasn't inordinately large it was a great implementation.
It wouldn't be too hard to refactor code in the gadget to display
anyone's RSS feed, if anyone is interested.  I found the pagination
control in that implementation to be a little smoother than scrolling,
when you've got a small asset that scrolls inside a larger document
that scrolls the UI can get tricky as the focus of the mouse
determines which object will scroll with the mouse wheel.

Cheers,
 Matt


On Oct 17, 8:47 am, Mislav Marohnić [EMAIL PROTECTED]
wrote:
 On 10/15/07, Matt Foster [EMAIL PROTECTED] wrote:



  I have developed a pretty smooth UI Control for handling
  client side pagination.  It is composed of 3 classes that allow for
  maximum decoupling.  In this manner the view is decoupled from the
  iteration control, such that the same iteration control can be used on
  any data set while the view can be specialized for any format of JSON
  or XML.

 I'm not sure if such announcements are suitable for this group. (Someone
 correct me if I'm wrong when stating it isn't.)

 That said: Interesting work. I handle pagination server-side myself (using
 the will_paginate plugin for Rails), but I definitely see use cases when you
 have to move this logic client-side.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---



[Prototype-core] Re: Prototype Pagination

2007-10-17 Thread Mislav Marohnić
On 10/15/07, Matt Foster [EMAIL PROTECTED] wrote:


 I have developed a pretty smooth UI Control for handling
 client side pagination.  It is composed of 3 classes that allow for
 maximum decoupling.  In this manner the view is decoupled from the
 iteration control, such that the same iteration control can be used on
 any data set while the view can be specialized for any format of JSON
 or XML.


I'm not sure if such announcements are suitable for this group. (Someone
correct me if I'm wrong when stating it isn't.)

That said: Interesting work. I handle pagination server-side myself (using
the will_paginate plugin for Rails), but I definitely see use cases when you
have to move this logic client-side.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---