Re: AjaxUpdateContainer ?
Re: AjaxUpdateContainer ?
- Subject: Re: AjaxUpdateContainer ?
- From: Faizel Dakri <email@hidden>
- Date: Wed, 27 Apr 2011 14:46:12 -0500
If you can't use a batching table, can you maybe split your data set into groups and then wrap each group in a tbody tag, which you can then mark as an update container (or wrap it in an update container). That way you don't have to have one update container per row, but you're also not forcing an update of thousands rows at a time. You just need to set a useful group size, say 50 or so rows.
F
On 2011-Apr-26, at 04:33 PM, Theodore Petrosky wrote:
> I guess I should have started off by saying that my user demands that all rows of data be visible all the time (because this is what it looks like in excel). I even have a boolean to not show old data but she insists that all data (including legacy data) is important and she needs to see it all the time (so nothing gets marked as 'complete').
>
> I think it sucks big time, but what can I do? I have been dragging my feet for 3 weeks already and the only solution I have found was to wrap every row in an UpdateContainer.
>
> Ted
>
> --- On Tue, 4/26/11, Chuck Hill <email@hidden> wrote:
>
>> From: Chuck Hill <email@hidden>
>> Subject: Re: AjaxUpdateContainer ?
>> To: "Theodore Petrosky" <email@hidden>
>> Cc: email@hidden
>> Date: Tuesday, April 26, 2011, 1:56 PM
>>
>> On Apr 26, 2011, at 5:16 AM, Theodore Petrosky wrote:
>>
>>> 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)?
>>
>
>
>> It is probably not much worse than a 1000 row table, a 1000
>> row table is pretty bad already. :-) That is a
>> terrible interface, IMO. You need to batch the data
>> and keep the table small. See AjaxGrid for one way to
>> do this.
>>
>>
>> Chuck
>>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden