How "bad" are views compared to cells
How "bad" are views compared to cells
- Subject: How "bad" are views compared to cells
- From: Francisco Tolmasky <email@hidden>
- Date: Sat, 27 Sep 2003 01:51:07 -0700
Ok, currently I have a view that has inside of it a series of matrices
containing any number of different input cells, to make an html-style
form. The problem is, I have often make different matrices to satisfy
the different sizes of the differing cells, for example, one run might
product a view holding something like this:
[matrix]
[nstextfieldcell]
[nstextfieldcell]
[/matrix]
[matrix]
[nspopupbuttoncell]
[/matrix]
[matrix]
[nstextfield]
[/matrix]
// ... so on
I have actually gotten this to work pretty well, and I assume it is
pretty efficient. The problem is though, complicated formatting
(putting two cells next to eachother horizontally, etc.) becomes quite
difficult using this method. The matrix can not have a checkbox next
to a pop up menu for example, since the sizes would be distorted. My
best solution has been to simply have the largest cell determine the
cell size of all the cells in a matrix, which can product some awkward
results (imagine a pop up menu of 200 pixels, with a preceding checkbox
that only needs about 100 pixels and thus there is an unnecessary space
between them).
My question is, should I continue to try to find an nscell solution to
my problem, or is it in this case worth it to just use there view
counterparts and position them at will? Are the views really that
"bad" compared to cells? Take into account that there is no way to
know ahead of time how many input fields there will be, since it is
user defined.
Any help is greatly appreciated,
Francisco Tolmasky
email@hidden
http://users.adelphia.net/~ftolmasky
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.