Enyo 2.0 beta 4!

unwiredben

Our end-of-April refresh of things is out, a.k.a Enyo 2.0 beta 4. See the blog post about it for more details and check our detailed release notes too.

rafa_bernad

Every night I plan to go to bed early, the Enyo Team comes with something like this...

andregarzia

Yay!!!! Thanks Team!

fxspec06

Where is the virtual list control? I don't see it in the documentation.

azakus

List is in the layout library.

ekdikeo

That List demo is great .. although it seems that the scroller speed might be screen size dependent to some degree -- it seems to be a bit slower on larger screens, and not just due to the volume of stuff on the display, the scrolling action and everything looks fine, it just doesn't scroll as fast.

Who can I bribe into porting this scrolling to Enyo 1? :)

fxspec06

FlyweightRepeater.js line 117 is erroring. Getting some weird mouseover error.

After investigation, it's because n.id is undefined 1 out of 100 times. The while loop shouldn't be iterating, but it is. To fix:

On 115, insert "&& n.id" to the while loop. (sans quotes)

benluo

what's the difference between repeater and list?

azakus

@benluo: Basically, Repeater renders everything at once, while List paginates.

Repeaters are good for small lists, but fall over when the list gets too large (if we had more time, we could probably write a white paper on the interactions of list size and GPU accelerated compositing).

List paginates itself seamlessly so that the actual DOM content should be below the performance-destroying threshold, and therefore allows for an infinitely large list that performs quickly. However, to maintain proper event flows and paginate correctly, Lists have to have consistent and knowable item sizes, while Repeater can have anything inside of it.

Hope that sheds some light there.

unwiredben

@fxspec06: your issue is filed at https://github.com/enyojs/layout/issues/2

minego

Has anyone else had issues with the new list kind and refresh? When I call this.$.list.refresh() my list often disappears.... I'm very confused.

unwiredben

Would love to see more debugging on this, @minego. Refresh does three things: invalidate the current HTML content on display, call update with the current scroll position, and then make the scroller superkind stabilize.

Internally, the list keeps two pages, HTML controls that hold part of the visible list content. It has a strategy of keeping one page on screen while having the other one available for scrolling. When you see the list disappear, is your onSetupRow event handler still being called?

waynetam

Lists definitely seem faster and less glitchy than enyo1 lists on android, but I am comparing a test app with a full app with more complex lists.

Are there plans for the enyo2 lists to support more of the enyo1 list features like acquirePage, swipeableItems and drawers? I know the last two can be implemented with what's already available in enyo2, but it would be nice to not have to write them ourselves.

Also, I've only tested on a CM9 Touchpad and I'm wondering if anyone can tell me if the performance is better on a "real" android tablet.

ekdikeo

I would say that on a CM7 touchpad, the performance looks to be quite a bit better than Enyo 1. However, it does appear to be dropping events - multiple rapid swipes move it slower and slower on CM7/Android 2.3, but in webOS and iOS it just flies along at the same speed the whole time (albeit slower on a tablet than on a handheld)

katratxo

Hi all,

Is the list suppose to work on mobile browsers? I just tested the flyweightRepeater.html example, and I got some strange behavior on an Android device (Samsung Galaxy S II - ICS 4.0.3):

- The default browser: doesn't detect always the row "tap" event, and when is detected, the row index is not correct
- Chrome Beta for Android: Works until the 10th row (the first visible ones), when you scroll (11+ row) the tap event stops working

Any ideas?

Thanks,

unwiredben

Problems with Chrome for Android are a known issue, but I don't think we have a fix yet. I'm not sure about the row detection issue -- I just fixed one problem last night involving margins between row elements, but I don't think that's what your reporting.

I have filed this in our bug system as https://github.com/enyojs/layout/issues/3 and https://github.com/enyojs/layout/issues/4.

katratxo

@unwiredben
Thanks, I'll pull the latest changes and try again

minego

@unwiredben I worked around it by using reset() and fix the scroll position and selection afterwards.