Re: Newbie: Dynamically filling NSTableView
Re: Newbie: Dynamically filling NSTableView
- Subject: Re: Newbie: Dynamically filling NSTableView
- From: Brian Ganninger <email@hidden>
- Date: Wed, 7 Mar 2007 15:10:34 -0600
Tableviews are meant to handle large data sets (with the caveat that
you can hit the roof of numerical restraint, i.e., max out row count
due to 32 bit limitations) and your concerns would be easily tested
by creating a test app to exercise your questions (loop 100,000 times
creating a new string each time, bind array to a table and see what
happens - or be more advanced, use a dictionary for entry and add
multiple keys that will in turn be bound to each column)
On Mar 7, 2007, at 10:40 AM, jordibares wrote:
Hi, is funny because I am at this moment looking for something
similar so I
just though to pile in.
I am trying to use a Table view as a log and give the user the
capability of
sorting messages, filtering and all that. Hope that makes sense to
all.. My
questions are
If you are worried about it and performance metrics (from Shark) bear
out that using convenience technologies (like Cocoa Bindings, Core
Data, and others) is having an impact you can drop down and use
manual control for filtering (by handling it all yourself), sorting
(provide your own sort function), and data management (as a data
source and delegate for the tableview.)
- In terms of performance will it be horrible if I arrive to 2000
entries or
more?
No. I've had 100,000 items sitting in a table with nary a problem.
The factor here isn't the tableview, it's the dataset. Tableviews are
simply efficient views for displaying tabular data.
- Would be better to use another kind of approach?
Not if tableviews are what you want to use. There's no technical
reason not to, its more design.
I am not familiar at all with Core data so I rather follow the
basic path of
handling it by hand as it is a small internal app.
How exactly did Core Data come into play? It's for managing object
persistence, not tableviews specifically (though you can view CD
results in a tableview) If you are not already on very solid ground
with your Cocoa experience you shouldn't be attempting to use Core
Data, as the documentation states on the first page of its guide.
Thanks in advance
Jb
On 26/2/07 11:13, "Ryan Harter" <email@hidden> wrote:
Thanks Julio-
I've looked at the Docs with Cocoa in the search grougs, but I will
check the Reference Library.
Ryan
On Feb 26, 2007, at 12:04 , Julio Cesar Silva dos Santos wrote:
Open the Documentation (Help Menu -> Documentation), make sure that
the Search Groups panel on the left has Reference Library selected,
type NSTableView on the search field at the upper right corner and
when the NSTableView Class Reference document appears, click on the
companion guide Table View Programming Guide and make sure you read
all the document to understand how tables work.
Julio Cesar Silva dos Santos
email@hidden
email@hidden
Blogjective-C
http://www.jcs.santos.nom.br/wp
FetchYourLyrics
http://www.jcs.santos.nom.br/fyl/fyl.html
On 26/02/2007, at 07:44, Ryan Harter wrote:
I've got the NSOpenPanel figured out, I'm just stuck on connecting
the table to an array, if that's the way I should do it. I used
the documentation to get the NSOpenPanel done, but haven't found
very good documentation on the NSTableView and data source linking.
The program is a video converter. I left that part out because I
have that working and didn't think it was important. In number 3,
when the user loads video files into the program, there will be a
status icon in one of the columns saying that the file is pending
conversion. As that file is being converted, there will be an
icon for "In Progress" and upon finishing, there will be a pretty
green check mark. I believe this would have to be done using key/
value coding since the status must correspond to the correct
file. I found some documentation on using NSDictionarys in
NSArrays to achieve this, perhaps this is not the right approach?
- Ryan
On Feb 26, 2007, at 07:49 , Scott Stevenson wrote:
On Feb 25, 2007, at 11:16 AM, Ryan Harter wrote:
1. User clicks the '+' button and an NSOpenPanel opens allowing
the user to select files.
Drag and drop can be added later with NSPasteBoard, I think.
2. User selects item(s) and the paths are extracted, converted
to NSStrings and added to the array connected to the table.
3. status is set to pending until the files are worked on.
4. NSTableView reloads data from the array and the file paths
are displayed.
Let me know if you have any ideas. Is this an accurate approach?
This all looks good, though I'm not sure what you mean by
number 3.
Which part are you stuck on? Have you read the documentation for
NSOpenPanel? I think it should give you everything you need.
- Scott
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden