FROM : Dirk van Oosterbosch
DATE : Thu Apr 21 13:49:57 2005
Hi Julien,
AFAIK the standard way to deal with multiple types of documents and
multiple different UI's is to make multiple different subclasses of
NSDocument.
These then are set in the corresponding nib to be the File's Owner, you
override - (NSString *)windowNibName to return the appropriate nibname
and you change the NSDocumentClass keys in your Info.plist so the
NSDocumentController knows which NSDocument subclass to use to open
your files with.
or review the documentation again
http://developer.apple.com/documentation/Cocoa/Conceptual/Documents/
index.html?http://developer.apple.com/documentation/Cocoa/Conceptual/
Documents/Tasks/SubclassNSDocument.html
I believe then everything is managed for you and you don't have to
concern about releasing of the nib's
HTH
Best,
dirk
On 21-apr-05, at 11:05, Julien Palmas wrote:
> I have a document based app with only one window per document.
>
> This application can open a large variety of different documents, so I
> decided to create several nib files, each containing the corresponding
> view for the document.
>
> When opening the document, I check its kind and load the according
> nib. This helps reduce the application footprint and the load time, as
> I don't open all the nibs ...
>
> Still, This is my first document based app and I have issues about the
> files owner. For each different nib, I created a subclass of NSObject
> and set it as the file owner when I load the nib with [NSBundle
> loadNibNamed:] This owner has several IBOultets, but not for every
> single element in the nib.
>
> The thing is that when I release the owner, I don't think the nib is
> released as well, as my nib owner is not a sub-class of
> NSWindowController. But as I only have one window (that already has
> its NSWindowController), I didn't wanted to use a sub-class of
> NSWindowController for the nib owner.
>
> How could I do to make sure my nib is released ?
>
> Some "good-coding" advices would be greatly appreciated.
>
> Julien
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list (<email_removed>)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>
>
>
-----------------------------
Dirk van Oosterbosch
de Wittenstraat 225
1052 AT Amsterdam
the Netherlands
T ++ 31 20 7765565
M ++ 31 6 48401910
W http://labs.ixopusada.com
-----------------------------
DATE : Thu Apr 21 13:49:57 2005
Hi Julien,
AFAIK the standard way to deal with multiple types of documents and
multiple different UI's is to make multiple different subclasses of
NSDocument.
These then are set in the corresponding nib to be the File's Owner, you
override - (NSString *)windowNibName to return the appropriate nibname
and you change the NSDocumentClass keys in your Info.plist so the
NSDocumentController knows which NSDocument subclass to use to open
your files with.
or review the documentation again
http://developer.apple.com/documentation/Cocoa/Conceptual/Documents/
index.html?http://developer.apple.com/documentation/Cocoa/Conceptual/
Documents/Tasks/SubclassNSDocument.html
I believe then everything is managed for you and you don't have to
concern about releasing of the nib's
HTH
Best,
dirk
On 21-apr-05, at 11:05, Julien Palmas wrote:
> I have a document based app with only one window per document.
>
> This application can open a large variety of different documents, so I
> decided to create several nib files, each containing the corresponding
> view for the document.
>
> When opening the document, I check its kind and load the according
> nib. This helps reduce the application footprint and the load time, as
> I don't open all the nibs ...
>
> Still, This is my first document based app and I have issues about the
> files owner. For each different nib, I created a subclass of NSObject
> and set it as the file owner when I load the nib with [NSBundle
> loadNibNamed:] This owner has several IBOultets, but not for every
> single element in the nib.
>
> The thing is that when I release the owner, I don't think the nib is
> released as well, as my nib owner is not a sub-class of
> NSWindowController. But as I only have one window (that already has
> its NSWindowController), I didn't wanted to use a sub-class of
> NSWindowController for the nib owner.
>
> How could I do to make sure my nib is released ?
>
> Some "good-coding" advices would be greatly appreciated.
>
> Julien
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list (<email_removed>)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>
>
>
-----------------------------
Dirk van Oosterbosch
de Wittenstraat 225
1052 AT Amsterdam
the Netherlands
T ++ 31 20 7765565
M ++ 31 6 48401910
W http://labs.ixopusada.com
-----------------------------
| Related mails | Author | Date |
|---|---|---|
| Julien Palmas | Apr 21, 11:05 | |
| Dirk van Oosterbos… | Apr 21, 13:49 | |
| Julien Palmas | Apr 22, 02:26 | |
| Ondra Cada | Apr 22, 03:35 | |
| Julien Palmas | Apr 22, 08:44 | |
| j o a r | Apr 22, 09:22 | |
| Ondra Cada | Apr 22, 12:30 |






Cocoa mail archive

