Fwd: [PATCH 14 of 20] hgweb: add ajaxScrollInit skeleton

[Dave S]

(You'd think I'd learn to send these properly)

---------- Forwarded message ----------
From: Dave S <snidely.too at gmail.com>
Date: Fri, Aug 23, 2013 at 10:56 AM
Subject: Re: [PATCH 14 of 20] hgweb: add ajaxScrollInit skeleton
To: Alexander Plavin <alexander at plav.in>



On Tue, Aug 13, 2013 at 10:56 AM, Dave S <snidely.too at gmail.com> wrote:

> On Tue, Aug 13, 2013 at 1:34 AM, Alexander Plavin <alexander at plav.in>wrote:
>
>>
>>
>> 13.08.2013, 03:32, "Dave S" <snidely.too at gmail.com>:
>> > (resend, to list this time)
>>
>
>
>> > I haven't figured out who much the page is growing; Opera's "page info"
>> tool doesn't seem clear about this, and I haven't looked enough to have a
>> better tool.
>>
>>
>
>> Don't get what you want to say here by 'who (how?) much the page is
>> growing'. It grows 60 entries each time you scroll to the bottom.
>>
>
> Yes, "how much"; I apologize for the proof-reading goof.  I couldn't tell
> if it was growing by 6 or 60 entries, and having a visual clue would have
> been nice.  I was also looking for Opera page-info to tell me, and it
> didn't ... at least not in a way I could recognize; I think the numbers it
> displayed reflected the initial load, and didn't change when I scolled down
> and triggered some more.
>
> Also, I am not certain I prefer "grows by 60" to "moves the visible buffer
> by 60" (Android, and I guess MySQL, call this a "cursor"); in the latter
> case, the top of the window would be showing a different line after each
> dynamic load (and maybe with a cursor, you want to move 60/2, and also have
> to add dynamic up-scrolling).
>
>
As an example of asynchronous completion, here's a little background on
"cursors" (which you may understand better than I; I was obviously being
loose in my usage).

<http://en.wikipedia.org/wiki/Cursor_%28databases%29>

What I was trying to use "cursor" to say, was having the display be a fixed
number of rows, but sliding down (or up) the full set of rows (I guess
another description of this would be something like a browser's viewport).

And this article has an interesting usage:

<
http://tech.sarathdr.com/android-app/convert-database-cursor-result-to-json-array-android-app-development/
>

"This might be use ful when you do some database applications with
phonegap. Phonegap storage class could be some times slow and difficult
handle. Then you can write a separate plugin to do the querying. If you use
database raw queries you will get the results as cursor data structure. The
below code converts that to json array."


But I can see that removing the top entries that were previously displayed,
and then restoring them when scrolling up, would add to the complications
of writing the code.

/dps






-- 
test signature -- please apply at front gate on Tuesdays only.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20130823/a23e1036/attachment.html>