Ok, since you said "the list component never reaches 50/60 fps even when its itemRender is well optimized", I though the purpose was to reach the highest possible performance, not to study the different parameters.
If so, your code is perfectly ok (expect for the assignment of a boolean to opaqueBackground :) And yes, "LabelItemRenderer label is *BASED* on StyleableTextField", but does a thousand things more that you don't really need :) But again, if you're not trying to prove that you don't really need 4 different frameworks to get a decently fluid app, it's ok. Cheers! :) On Tue, Apr 8, 2014 at 4:03 PM, After24 <vinc...@after24.net> wrote: > I'm sorry Javier but I don't understand your response, would you please be > more specific. > > << NOT using labelitemrenderer, but StyleableTextField directly >> > > What do you mean ? the LabelItemRenderer label is based on > StyleableTextField. In fact I use this framework class because it's written > in AS3 (not MXLM) and very well optimized. The autoDrawBackground property > is not used in this particular ItemRenderer (and commenting the > drawBackground call in the updateDisplayList method doesn't seem to improve > performance significantly). > > Concerning the fps monitor, I agree that I could have used a more simple > process but this one is handy and it's not the update method (< 1ms in > scout) which degrades performance. By the way the purpose of this test is > not to get the highest fps possible but to study the effect of different > parameters on the list scrolling performance. > > > > > Javier Guerrero García wrote > > I'm talking about: > > > > 1. NOT using labelitemrenderer, but StyleableTextField directly > > 2. Setting the opaqueBackground property to anything (btw, it's a uint > > color, not a boolean :) > > 3. Setting the autoDrawBackground to false > > 4. And yes, in the new custom itemrenderer, set cacheAsBitmap to true > > > > All of that with rendermode=direct, in a ONE plain file, without two > > thousand packages and classes and functions and setters and getters, and > > avoiding setting CSS styles and rendering htmlText, converting colors to > > hex strings, managing LoremIpsums, and so on... EACH time you calculate > > the > > FPS :) > > > > 4-5 tags in ONE plain MXML file would be more than enough for such > > benchmark :) Max 1-2k's uncompressed :) > > > > > > On Mon, Apr 7, 2014 at 5:01 PM, After24 < > > > vincent@ > > > > wrote: > > > >> You have a very single way to communicate, anyway... > >> > >> When you say : "wait until you enable caching and disable backgrounds ;) > >> " > >> are you talking about the cacheAsBitmap property ? if it's the case I'm > >> just > >> saying that this property is set to true in the constructor of the > >> LabeItemRenderer. > >> > >> And why are you talking about a 300k component ? it's only 150 loc. > >> > >> > >> Javier Guerrero García wrote > >> > Questioning.stop(); > >> > Trying.start(); > >> > > >> > ;) > >> > > >> > And you should use stagetext instead, but thats just my opinion ;) > >> > > >> > El lunes, 7 de abril de 2014, After24 < > >> > >> > vincent@ > >> > >> > > escribió: > >> > > >> >> I don't understand is this not the already the case with the > >> >> LabelItemRenderer ? (cacheAsBitmap is set to true in the > constructor). > >> >> > >> >> > >> >> > >> >> > >> >> Javier Guerrero García wrote > >> >> > :) wait until you enable caching and disable backgrounds ;) > >> >> > > >> >> > El lunes, 7 de abril de 2014, After24 < > >> >> > >> >> > vincent@ > >> >> > >> >> > > escribió: > >> >> > > >> >> >> Javier, > >> >> >> > >> >> >> Setting renderMode to direct has a significant impact, scrolling > >> fps > >> >> is > >> >> >> now > >> >> >> comprise between 40 and 46 fps. > >> >> >> I'm using The spark LabelItemRenderer which is based on > >> >> >> StyleableTextField > >> >> >> for the label. > >> >> >> > >> >> >> > >> >> >> > >> >> >> -- > >> >> >> View this message in context: > >> >> >> > >> >> > >> > http://apache-flex-users.2333346.n4.nabble.com/Coding-a-better-flex-mobile-app-tp5888p6054.html > >> >> >> Sent from the Apache Flex Users mailing list archive at > Nabble.com. > >> >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> View this message in context: > >> >> > >> > http://apache-flex-users.2333346.n4.nabble.com/Coding-a-better-flex-mobile-app-tp5888p6057.html > >> >> Sent from the Apache Flex Users mailing list archive at Nabble.com. > >> >> > >> > >> > >> > >> > >> > >> -- > >> View this message in context: > >> > http://apache-flex-users.2333346.n4.nabble.com/Coding-a-better-flex-mobile-app-tp5888p6062.html > >> Sent from the Apache Flex Users mailing list archive at Nabble.com. > >> > > > > > > -- > View this message in context: > http://apache-flex-users.2333346.n4.nabble.com/Coding-a-better-flex-mobile-app-tp5888p6073.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. >
