There might be some posts on my blog that might help Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui
From: [email protected] [mailto:[email protected]] On Behalf Of Christopher McArthur Sent: Friday, September 04, 2009 9:35 AM To: [email protected] Subject: RE: [flexcoders] Why never create an item renderer? Can anyone recommend any good reading material on this? Im having some memory issues with my itemrenderers lately ;) From: [email protected] [mailto:[email protected]] On Behalf Of Alex Harui Sent: Thursday, September 03, 2009 11:53 PM To: [email protected] Subject: RE: [flexcoders] Why never create an item renderer? It is good enough if you shipped it and got paid :) If you want to post the code for a renderer, we can offer opinions on the pros and cons of your implementation. It might be good education for many. I don't have time to judge dozens of renderers so we can just start with one of yours and discuss it. There is usually a trade-off of ease of programming vs performance and memory optimization. The smaller and faster you want it to be, the more work you have to do. If you're only gonna have 7 renderers on screen, it doesn't matter as much as if you are creating DataGrid renderers for a 20x20 grid. Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: [email protected] [mailto:[email protected]] On Behalf Of Wesley Acheson Sent: Thursday, September 03, 2009 3:29 PM To: [email protected] Subject: Re: [flexcoders] Why never create an item renderer? I've created a few. I've recreated a few working ones because I want to understand the framework better. I guess my problem is how do I know if the item renderers i've created are "Correct". I've far too often seen programming as a religion. I've just as often seen people just make things work. I can't stand by either of these sometimes you need things to just work, however if you don't worry about practices you've got unmaintainable code. So how do I know if what I've written is good enough. Regards, Wesley Acheson On Thu, Sep 3, 2009 at 9:38 PM, Tracy Spratt <[email protected]<mailto:[email protected]>> wrote: It is not always given as advice. I give that when I see that a developer does not have his head around the issues. It is usually quite obvious when that is the case. I think it is better advice than RTFM. An example will get a newbie further faster. When that advice does not apply to you, you will know it. Tracy Spratt, Lariat Services, development services available ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Wesley Acheson Sent: Thursday, September 03, 2009 2:36 PM To: flexcoders Subject: [flexcoders] Why never create an item renderer? I've seen this adivse a lot reciently on the list. Don't create an item renderer modify an existing example. I don't really understand why. I mean their not that difficult to get your head arround so long as you reset all internal variables that need to be reset. Why is this always given as advise? Regards, Wesley Acheson
