I don't like repeaters.  They are too clumsy.  The biggest drawback is an 
inability to access values after the repeater has finish executing.  It's not 
the same as, for example, looping over values and generating static HTML using 
ColdFusion.  I seem to always end up having to navigate up and down through the 
parents/children of the objects and storing values I need in properties like 
name, automationName, etc.  This is clumsy and messy.

As an example, I have a section of my application where I want to list the 
names of people from a table, and for each person generate a set of checkboxes 
that designate access to certain areas of the application.  For example: 
http://www.ubeek.com/images/staffrepeater.jpg

That is one main repeater that loops through the staff (records returned from 
remoteObject) and inside that repeater two other repeaters (also from 
remoteObjects) that generate the checkboxes.

I can't simply pass the primary key of the staff for which the Save button was 
clicked, by putting click="saveClick({staffRepeater.currentItem.SEQ})" into the 
button object.  When I do that and click it I get an error about "repeater is 
not currently executing" or something like that.

I don't want to resort to a datagrid and then "click to edit" then bring up a 
form kind of process.  I want it as few clicks as possible.

Is there a better way to display data in a custom way like this, without using 
repeaters, so that I can more easily access the child objects and their 
properties?

Thanks,
Paul

Reply via email to