[aerogear-dev] AeroGear 1.0 and Paging

Summers Pittman supittma at redhat.com
Fri Mar 22 10:26:28 EDT 2013


On 03/22/2013 10:18 AM, Matthias Wessendorf wrote:
>
>
> On Fri, Mar 22, 2013 at 3:07 PM, Summers Pittman <supittma at redhat.com 
> <mailto:supittma at redhat.com>> wrote:
>
>     From the spec:
>     A|parameter provider|API will be provided to that the application
>     developer can submit any (paging) parameter that the used server
>     requires. An example would be that the used paging service
>     supports sorting as well.
>
>     That is what this class did and is getting renamed to be correct.
>
>     You are referring to Paging parameters.
>
>
> https://github.com/aerogear/aerogear.org/blob/master/docs/specs/aerogear-client-paging/index.markdown#default-parameter-providers
>
>
Hrm.  I guess I always read that as default paging parameters since that 
is the topic of the entire previous paragraph.
>
>
>
>     On 03/22/2013 10:05 AM, Matthias Wessendorf wrote:
>>     parameter provider, is used to specify the "query" (e.g.
>>     limit/offset , page. per-page) etc
>>
>>     Is that waht it does ?
>>
>>     On Fri, Mar 22, 2013 at 2:55 PM, Summers Pittman
>>     <supittma at redhat.com <mailto:supittma at redhat.com>> wrote:
>>
>>         Y'all,
>>
>>         I noticed that some of the method and class names in AeroGear
>>         Android around Paging are sub obtimal.
>>
>>         I would like to, before 1.0 is cut, make the following changes
>>
>>         Methods:
>>         PageConfig.setPageHeaderParser -> PageConfig.setParameterProvider
>>
>>
>>         Classed:
>>
>>         PageResultExtractor -> ParameterProvider
>>         ParameterProvider -> gets merged into Parameter Provider
>>
>>         All implementations are updated
>>
>>         wdyt?
>>
>>
>>         _______________________________________________
>>         aerogear-dev mailing list
>>         aerogear-dev at lists.jboss.org
>>         <mailto:aerogear-dev at lists.jboss.org>
>>         https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>>
>>     -- 
>>     Matthias Wessendorf
>>
>>     blog: http://matthiaswessendorf.wordpress.com/
>>     sessions: http://www.slideshare.net/mwessendorf
>>     twitter: http://twitter.com/mwessendorf
>>
>>
>>     _______________________________________________
>>     aerogear-dev mailing list
>>     aerogear-dev at lists.jboss.org  <mailto:aerogear-dev at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>     _______________________________________________
>     aerogear-dev mailing list
>     aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> -- 
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130322/9cf23bbd/attachment.html 


More information about the aerogear-dev mailing list