FROM : mw
DATE : Fri Jan 03 16:02:18 2003
Hello,
I am not sure if I should make my application document-based or not. It
doesn't handle documents in the normal way, persay. There is a central
database per user that takes care of loading and unloading settings and
"documents" (that aren't really individual documents... this is hard to
explain) automatically. It isn't like TextEdit where its main window
revolves around typing and formatting and saving/opening/printing, etc.
However, there WILL be windows for typing in contents of things such as
emails, notes, etc.
So, the final question is: should I create my project as a document-based
app in PB, or should I just have a normal application. Oh, also, I want to
have complete control over which window appears at the startup of the
application (it won't be a main window or anything). In a document-based
app, I think I can overload
- (BOOL)applicationShouldOpenUntitledFile:(NSApplication *)theApplication
in my application delegate, but I haven't test to see if it actually keeps
Cocoa from automatically opening windows at startup or not.
TIA,
mw
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
DATE : Fri Jan 03 16:02:18 2003
Hello,
I am not sure if I should make my application document-based or not. It
doesn't handle documents in the normal way, persay. There is a central
database per user that takes care of loading and unloading settings and
"documents" (that aren't really individual documents... this is hard to
explain) automatically. It isn't like TextEdit where its main window
revolves around typing and formatting and saving/opening/printing, etc.
However, there WILL be windows for typing in contents of things such as
emails, notes, etc.
So, the final question is: should I create my project as a document-based
app in PB, or should I just have a normal application. Oh, also, I want to
have complete control over which window appears at the startup of the
application (it won't be a main window or anything). In a document-based
app, I think I can overload
- (BOOL)applicationShouldOpenUntitledFile:(NSApplication *)theApplication
in my application delegate, but I haven't test to see if it actually keeps
Cocoa from automatically opening windows at startup or not.
TIA,
mw
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| Related mails | Author | Date |
|---|---|---|
| mw | Jan 3, 16:02 | |
| Mike Ferris | Jan 3, 18:28 | |
| mw | Jan 3, 18:43 | |
| Alex Rice | Jan 3, 18:52 | |
| Chris Hanson | Jan 3, 22:41 | |
| mw | Jan 4, 14:41 |






Cocoa mail archive

