Hi,
I thought that the new bead would be "magically" full automatic.
Can you give an example (a very basic one) of the getMoreData method
implementation ?
Harbs <harbs.li...@gmail.com> escreveu no dia segunda, 1/05/2023 à(s) 17:14:
> I added InfiniteScroller.
>
> You can use it like this:
>
> <js:List id=“myList”>
> <js:beads>
> <js:InfiniteScroller scrollEnd=“getMoreData()”/>
> </js:beads>
> </js:List>
>
> If the scroll container is not the actual list, you should use it like
> this:
> <js:Group id=“scrollContainer”>
> <js:List id=“myList”>
> <js:beads>
> <js:InfiniteScroller scrollEnd=“getMoreData()”
> scrollContainer=“{scrollContainer}”/>
> </js:beads>
> </js:List>
> </js:Group>
>
> I’ll try to add the other bead tomorrow…
>
> Harbs
>
> > On Apr 26, 2023, at 12:46 PM, Hugo Ferreira <hferreira...@gmail.com>
> wrote:
> >
> > I'm sold :)
> >
> > When you push that to github, please make a comment here.
> > I will test it right a way ;)
> >
> > Harbs <harbs.li...@gmail.com> escreveu no dia quarta, 26/04/2023 à(s)
> 10:43:
> >
> >> If you use IntersectionObservers, the callback is only invoked when the
> >> observed element comes into view. The beauty of the
> IntersectionObservers
> >> is that it doesn’t matter how the element comes into view. It can be by
> any
> >> kind of scrolling, window resize, or even by changing the visibility of
> it.
> >> It’s very elegant and much more performant than listening to scroll
> events.
> >>
> >>> On Apr 26, 2023, at 12:32 PM, Hugo Ferreira <hferreira...@gmail.com>
> >> wrote:
> >>>
> >>> But, don't forget that the user can grab the scroll bar and drop
> >> somewhere.
> >>
> >>
>
>
