Re: Cocoa UI
Re: Cocoa UI
- Subject: Re: Cocoa UI
- From: Shawn Erickson <email@hidden>
- Date: Wed, 13 Dec 2006 08:03:07 -0800
NIBs don't contain compiled code but serialized object graphs (some
of which are placeholders resolved at load time). So yes you could
modify, replace, or selectively load those to change how your
application looks if you design your nibs and core code to allow for
that type of flexibility.
An application on Mac OS X is the whole bundle directory (.app) which
includes the application binary and resources (nibs, images, icons,
etc.). Application bundles should never be modified as part of normal
application use for a few reasons... 1) the application could be used
in a shared environment (multiple users use it and possibly
concurrently), 2) a user may not have (ideally shouldn't) write
permissions to the application bundle, 3) would invalidate code
signing both on disk and in RAM, etc.
Likely the best way to go about this is to selectively load
preexisting nibs from your applications bundle or a supported plugin
directory when your application first launches.... of course it still
isn't clear exactly what you are looking for.
-Shawn
On Dec 13, 2006, at 7:25 AM, Jerrod Fowkes wrote:
"application that modifies itself" Well it wouldn't do that per-
say. The application binary and in memory wouldn't be modified at
runtime. I wouldn't comprimize that stability for this feature. I
just want the ability to modify the presentation layer of the
application before it starts up so that it will have a different
look and feel but it would still sit on top of the core application
but just subscribe to the core program using bindings (basically
modifying a nib without compiling the actual program since the nib
is just a resource). -Jerrod
Michael Watson <email@hidden> wrote: If you're suggesting
writing an application that modifies itself, you
should rethink this approach. You can't guarantee that a user will
have write access to an application, among other concerns.
--
m-s
On 13 Dec, 2006, at 10:03, Jerrod Fowkes wrote:
Let me attempt to almost anwser my own question. in Xcode, you
include your nibs and they end up being put together as a resource
part of the compilation. However on the filesystem, the end result
of the program is actually a folder or a directory. The nibs are
part of that folder as a resource. I suppose if you really wanted
to, you could open up that folder and rip out the nibs, change
them, and then put them back. However I don't think this is really
a standard way. Need some guidance here. -Jerrod Fowkes
_______________________________________________
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:
40yahoo.com
This email sent to email@hidden
---------------------------------
Want to start your own business? Learn how on Yahoo! Small Business.
_______________________________________________
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:
This email sent to email@hidden
| References: | |
| | >Re: Cocoa UI (From: Jerrod Fowkes <email@hidden>) |