Re: Inspector window
Re: Inspector window
- Subject: Re: Inspector window
- From: Guy English <email@hidden>
- Date: Tue, 22 Mar 2005 02:01:16 -0500
Anton Kiland <email@hidden> wrote:
> You just take an NSTableView and fill up the entire window. Then you
> have NSMutableDictionaries in every object
> in your application containing it's properties and their values. And
> you just list them in that window with cocoa bindings.
If you're making some in house editor then, yeah, I think it'll do if
you've got a pretty technical audience. I've done similar nasty things
with Python scripts and a game content editor - but it was all our own
in-game UI toolkit no Cocoa stuff. My experience with that suggests
that if you've got some patient level designers they'll appreciate you
gave 'em a crummy UI because you're too busy fixing all the other bugs
that make 'em blue. :)
If you're planning on shipping this to people who can't come by your
desk and complain then I'd really suggest doing a proper inspector UI.
That said if you can advertise your properties with enough meta-data
that you can dynamically create a nice inspector by stacking specific
property editing views then more power to you. So, if your heart is
set on it you want to expose an array of dictionaries. Each dictionary
names the property, tells the code which editor view to use, which
accessors and validators to call, and maybe some help text explaining
what the property does. For each property in the array you create a
new view and add it as a subview to the inspector view, resizing the
inspector window or using a scroll view as you see fit.
Guy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden