RE: [flexcoders] Re: better option than repeater?

2009-07-27 Thread Battershall, Jeff
27, 2009 2:22 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: better option than repeater? I don't quite get what you are trying to do. Create a component. This component will display each staff member. Create a public variable to hold each staff record (Value Object) and pass that

[flexcoders] Re: better option than repeater?

2009-07-27 Thread valdhor
I don't quite get what you are trying to do. Create a component. This component will display each staff member. Create a public variable to hold each staff record (Value Object) and pass that record to the component inside the repeater. The example I posted shows how to do this. So, there is on

[flexcoders] Re: better option than repeater?

2009-07-23 Thread postwick
Sorry, link should have been http://www.ubeek.com/Flex/testrend.txt --- In flexcoders@yahoogroups.com, "postwick" wrote: > > OK, thanks to the below example, I have made some progress on setting up > my first custom itemRenderer. Code can be viewed here: > http://www.ubeek.com/Flex/testrend.mxm

[flexcoders] Re: better option than repeater?

2009-07-23 Thread postwick
OK, thanks to the below example, I have made some progress on setting up my first custom itemRenderer. Code can be viewed here: http://www.ubeek.com/Flex/testrend.mxml As I mentioned before, my goal is to display a list of Staff. One of the fields (moduleAccess) in the Staff record is a list of

[flexcoders] Re: better option than repeater?

2009-07-20 Thread postwick
Thanks for the example. I know that I could make certain things a lot easier by setting up classes and components, but I don't have a lot of practice at it. Hopefully this will get me started and I'll get it figured out. I know it would simplify my code - there are many places where I repeat

[flexcoders] Re: better option than repeater?

2009-07-20 Thread valdhor
As a quick and dirty... http://www.adobe.com/2006/mxml"; layout="vertical" xmlns:custom="Components.*"> CheckBoxComponent.mxml: http://www.adobe.com/2006/mxml"; creationComplete="onCreationComplete()"> Person.as: package

Re: [flexcoders] Re: better option than repeater?

2009-07-20 Thread claudiu ursica
maybe you can send me your data structure and I'll mock something on that ... C From: postwick To: flexcoders@yahoogroups.com Sent: Monday, July 20, 2009 9:54:46 PM Subject: [flexcoders] Re: better option than repeater? Can you give me a brief example o

[flexcoders] Re: better option than repeater?

2009-07-20 Thread postwick
killers for > perormance even when you tell them to cache children > > C > > > > > > From: valdhor > To: flexcoders@yahoogroups.com > Sent: Monday, July 20, 2009 9:45:44 PM > Subject: [flexcoders] Re: better option than repeater?

Re: [flexcoders] Re: better option than repeater?

2009-07-20 Thread claudiu ursica
I'd use lists with custom item renderers. Repeaters are killers for perormance even when you tell them to cache children C From: valdhor To: flexcoders@yahoogroups.com Sent: Monday, July 20, 2009 9:45:44 PM Subject: [flexcoders] Re: better option

[flexcoders] Re: better option than repeater?

2009-07-20 Thread postwick
Can you give me a brief example of code that would achieve the part where you say "create a component"? Keep in mind the number of checkboxes and their labels is not static. There are three tables involved: staff, modules, and queues. The checkboxes are created dynamically from the records re

[flexcoders] Re: better option than repeater?

2009-07-20 Thread valdhor
I use repeaters quite a lot and like them. What I do is to create a component (Which sometimes contains other components) and the repeat that. In your situation, I would create a component with all of your check boxes and save button. This component would have all of the functionality to displa