I am presenting a table to my user and I am noticing that the number of rows that they want to keep current is growing to more than 1k.
One of the UI issues is to color individual rows that signify specific meta data (ie. row is red so it is important, green is something else). Currently, I have one AjaxUpdateContainer wrapping the whole table. If the user updates the row color, I fire the container update. But with over 1k rows, this is starting to take time (10 - 15 seconds). So I thought that I would wrap the individual row in its own update container. Before I jump into this, I thought I would ask. If I had 1000 update containers on my page, am I shooting myself in the foot? Or is this what the AjaxUpdateContainer is made for? Or do I have to update the whole table for the row color to update (with CSS)? Ted _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
