FROM : j o a r
DATE : Mon Nov 18 22:49:27 2002
On Monday, Nov 18, 2002, at 13:43 Europe/Stockholm,
<<email_removed>> wrote:
>> I'm not sure that I agree with using just one table view for
>> displaying 20.000 records
> 20,000 is an example. Most real life situations will require a lot
> more.
As long as you don't turn into that guy over at Mac OS X Dev that
wanted to display 37 million rows in a table view... ;)
(Thread: "Maximum size for NSTableView?")
>> That said, NSTableView is provided as a general purpose control -
>> not suited for very large tables with a high frequency of updates.
>
> OK, fine, sure. Then what control does NS have for large tables?
NSTableView is the only one - but I wouldn't nessecarily rule it out
already.
>> In our main application we've created our own table view optimized
>> for our particular needs and this might be something that you need
>> to do if NSTableView cannot keep up properly.
>
> Yeah, I'm getting that picture. My complaint isn't so much with the
> view itself, but with the lack of tidy memory management underneath.
> That's where the clocks are saved.
>
> The picture I am getting is that Apple/NS are unsurpassed at graphics,
> but that types of business things are a bit unfamiliar for them. I
> would hate to give MS the win on this one, but it looks like their
> crummy listview, coupled with Cutler's memory management, wins this
> round.
Weren't the Cocoa frameworks created for use in the enterprise? I know
that we've successfully used them for heavy lifting for years and years
on a wide variety of platforms - still going strong actually - and the
streams of data we have to deal with in real time is quite something.
I think that Alex and Andreas suggestions on memory management might be
a good thing to look into. Is the memory management "a la Cutler" you
mentioned a Windows only thing, or something that you could use also on
Mac OS X?
j o a r
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
DATE : Mon Nov 18 22:49:27 2002
On Monday, Nov 18, 2002, at 13:43 Europe/Stockholm,
<<email_removed>> wrote:
>> I'm not sure that I agree with using just one table view for
>> displaying 20.000 records
> 20,000 is an example. Most real life situations will require a lot
> more.
As long as you don't turn into that guy over at Mac OS X Dev that
wanted to display 37 million rows in a table view... ;)
(Thread: "Maximum size for NSTableView?")
>> That said, NSTableView is provided as a general purpose control -
>> not suited for very large tables with a high frequency of updates.
>
> OK, fine, sure. Then what control does NS have for large tables?
NSTableView is the only one - but I wouldn't nessecarily rule it out
already.
>> In our main application we've created our own table view optimized
>> for our particular needs and this might be something that you need
>> to do if NSTableView cannot keep up properly.
>
> Yeah, I'm getting that picture. My complaint isn't so much with the
> view itself, but with the lack of tidy memory management underneath.
> That's where the clocks are saved.
>
> The picture I am getting is that Apple/NS are unsurpassed at graphics,
> but that types of business things are a bit unfamiliar for them. I
> would hate to give MS the win on this one, but it looks like their
> crummy listview, coupled with Cutler's memory management, wins this
> round.
Weren't the Cocoa frameworks created for use in the enterprise? I know
that we've successfully used them for heavy lifting for years and years
on a wide variety of platforms - still going strong actually - and the
streams of data we have to deal with in real time is quite something.
I think that Alex and Andreas suggestions on memory management might be
a good thing to look into. Is the memory management "a la Cutler" you
mentioned a Windows only thing, or something that you could use also on
Mac OS X?
j o a r
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| Related mails | Author | Date |
|---|---|---|
| Rixstep | Nov 18, 06:28 | |
| Alex Rice | Nov 18, 08:54 | |
| Alex Rice | Nov 18, 09:11 | |
| Andreas Mayer | Nov 18, 10:28 | |
| <rixstep000 | Nov 18, 13:43 | |
| <rixstep000 | Nov 18, 14:10 | |
| <rixstep000 | Nov 18, 16:27 | |
| Alex Rice | Nov 18, 20:14 | |
| Andreas Mayer | Nov 18, 22:07 | |
| j o a r | Nov 18, 22:49 | |
| j o a r | Nov 18, 23:34 | |
| David Remahl | Nov 19, 00:23 | |
| Terrence Asselin | Nov 19, 01:39 | |
| Kevin Elliott | Nov 19, 18:27 | |
| Alex Rice | Nov 19, 19:16 | |
| Clark S. Cox III | Nov 19, 22:20 | |
| Rosyna | Nov 20, 07:25 |






Cocoa mail archive

