Re: Advice sought for properties editor
Re: Advice sought for properties editor
- Subject: Re: Advice sought for properties editor
- From: Yuhui <email@hidden>
- Date: Fri, 20 Jun 2003 18:46:15 -0500
Hi Florent,
By UI element, I assume that you mean every button, slider, checkbox,
window, etc. that your program uses?
Based on what I've learned from my own experience and discussing it
with on the list, you should have one NIB per window, so if you program
has five windows, you should have five NIBs. This isn't a hard-and-fast
rule, though. Dividing the program into multiple NIBs allows for
dynamic loading, so if a window isn't used often, like an About window,
then it can be placed in its own NIB and won't take up resources at
runtime until the user opens the About window.
But if there are a few windows that the user will almost always use,
then I think it would make sense to put them in one NIB, so as to
reduce what little time it would require if the window/NIB had to be
dynamically loaded at request.
Hope that helps.
Yuhui
I'm writing a UI constructor for Palm software. Right now all the
back-end is done and some of the UI is up.
I need some advice on each UI element's properties editing: is it
better to create one different view for each UI element, or a generic
property editor that would look clumsier than a specialized view per UI
element ?
I'd definitely appreciate any insight you experts have on this. I
especially would like to know the pros and cons of having 1 nib per UI
element type (I have about 15 of them to cover), or if have one nib
files containing all the distinct views with a single controller view
that would be loaded once and for all...
Florent
_______________________________________________
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.