Re: [IB] Cells vs Controls in the Library
Re: [IB] Cells vs Controls in the Library
- Subject: Re: [IB] Cells vs Controls in the Library
- From: Stéphane Sudre <email@hidden>
- Date: Tue, 24 Aug 2010 13:07:44 +0200
On Aug 24, 2010, at 12:05 PM, Christiaan Hofman wrote:
[...]
To remove some clutter from the Library so that you can find the
object you're looking for faster.
You would not get that. The cells are generally setup in a far
different way than the controls, because it should be appropriate
for a table rather than a stand-alone control. So you would still
need two objects. Gain nothing, lose a lot of information, and in
fact confuse things because you now lose the context of cells when
you need a cell, but get a larger number of "controls or cells."
Library != Inspector
Well, that's my point. The drop target knows what to accept because
it is told what to expect in the drop and therefore can choose
whether to accept. Now you're saying to confuse and remove the
information about what it's getting from the drop (is it a cell? is
it a control? it's superman!) and it won't be able to make that
choice anymore (there's no NSMaybeCellOrControl object, they're in
very different parts of the object hierarchy, and see my remark
below).
It is generally a very bad idea for generic operations (like
dropping an objects) to require knowledge about specific
peculiarities (like this thing about controls and cells.)
Last time I checked, it was possible to add multiple
representations of an object in the pasteboard for a drag
operations. So would there be something really bad about having for
instance both the cell and the control representations in the
pasteboard and then let the layout controller decide which one
should be used?
Because the layout controller may not be able to make the choice, as
I said below.
See the last part.
Moreover it's not supported by the generic way the IB plugins work.
That's quite possible. But this is what updates are for.
Moreover, the drop target could in fact accept both controls and
cells, and you'd be screwed, for instance when you want it to be a
top level object (which is really not such a weird thing.)
I would be interested by a good example. For instance, AFAIK, you
would need to use a custom view said to be a NSImageView to have a
NSImageView accepts a NSButton as a subview in IB.
A top level object that can be swapped in using code. There are many
cases where this may be useful. Generally, if you don't use it it
does not mean it doesn't exist or is not useful.
Code is not a valid example in my opinion as this is outside IB scope.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden