I'm coming to end of my 1.0 release (using enyo 1.0 on Android with PhoneGap) and I have a very uneasy feeling about it. The performance is keeping me up at night (and that's based on what I see on my Galaxy Nexus -- what are the more modest devices gonna do?). It's not a huge app, in fact all the data is really simple.
I've got a carousel of views that is painfully slow to flick through. I've looked through forum posts to find a solution. I've found the code in the Scrolling ... post that fixes the dragging in ScrollStrategy. I don't think that will help (tried it). Is there any other known issues around carousels?
The other real annoyance is that when I'm flicking through the carousel, it doesn't animate the rest of the flick after I lift my finger up. That makes it really hard to detect visually whether or not it actually went to the next/prev view. Is there any fix for that?
The UI was fun to create - really easy to assemble. But these issues have got to be fixed before I ship this thing.
0 ·
Comments
I will post the code I have changed when I get home from work in a couple hours and you can try it out then.
https://github.com/appsbychris/enyo1scroller/blob/master/customscroller.js
I have it as its own JS file. I use a global variable (ISPHONE) in my app to adjust the scrolling on the phone vs touchpad.
Then you just replace your kind's with the Custom kinds.
Let me know how it goes. I am going to make the app i use this in run on android in the next month or so.
To me, the biggest issue is how slowly it responds to my initial swiping motion. Native controls respond pretty much immediately. I know that's a high bar to set, but that's what I'm going to be judged against.
The other biggie is the animation when dragging is done. I don't see any. It just snaps immediately. Would that be smoother in code or with a CSS transition?
I would go through the scroller code and tweak some of the variables and see what results it makes.
Last time I checked, Enyo2 was short on controls (no Panel, Carousel, Repeater, VirtualList, etc.). Maybe I'm missing something. Should I even be looking for the same controls or will they all have changed? Or does Enyo2 just replace base classes? I guess I'm not sure how to know when is a good time to invest the time to migrate.
The layout library provides panels and list, enyo.Repeater is in the base UI code, and you can do a carousel using the arrangers in the panels code.
Some of those changes to the draft are kind of vague... Guess I'll just have to wait and see what happens and react accordingly.
In general it sounds like migrating would be a hefty task for me. Converting flex layouts/boxes to something else. Carousels are now arrangers. Repeater has moved (changed API?). Is there any help for this anywhere? Blog post maybe?
@unwiredben: sorry will do next time