And if you can push your client to use Safari or Chrome, you can build a table without using <table>, but do everything in css
you could use <ul> and <li> see css "display" propertiy http://www.w3schools.com/css/pr_class_display.asp Amedeo On 27/apr/2011, at 00.14, Chuck Hill wrote: > I see that you have a few options: > > 1. Fire your client. > 2. Educate your client. > 3. Figure out what they really need to do (NEED vs Implementation aka Excel) > and deliver an interface that meets their needs in a far, far more effective > way than scrolling in Excel. > 4. Torture your client with a painfully low and ineffective UI > 5. Use pure client side JavaScript as Mike suggested > 6. Switch to divs so that the UI renders faster and you can update individual > rows. > > > Chuck > > > On Apr 26, 2011, at 2: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 <ch...@global-village.net> wrote: >> >>> From: Chuck Hill <ch...@global-village.net> >>> Subject: Re: AjaxUpdateContainer ? >>> To: "Theodore Petrosky" <tedp...@yahoo.com> >>> Cc: webobjects-dev@lists.apple.com >>> 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 >>> >> > > -- > Chuck Hill Senior Consultant / VP Development > > Come to WOWODC this July for unparalleled WO learning opportunities and real > peer to peer problem solving! Network, socialize, and enjoy a great > cosmopolitan city. See you there! http://www.wocommunity.org/wowodc11/ > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/amedeomailing%40insigno.it > > This email sent to amedeomail...@insigno.it --------------------------------- Amedeo Mantica WOWODC 2011 : July 1-2-3, Montreal. wowodc.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
