-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transform to Document-Based application #11
Comments
That is a good idea. The plan is for CoreDataPro to edit the data and not just view it. Many of the features you mentioned above would be an advantage. |
The first way to do it is recreate xcode project with needed type. Another way - do it manually. Unfortunately, I dont know how to do it manually, so I suggest to recreate project and import all files. |
I think you are right the easiest way to make an MDI is to create a new project and import the files. I expect there will need to be some significant surgery to MFLMainWindowController. Are you planning on trying to code this up? |
I can do it, but not soon. |
I suggest create new branch to begin transforming to document-based app. |
Done. See "feature/multiDocSupport" |
I think we are almost done. Please, check my pull request in feature/multiDocSupport branch. Now it support saving/opening documents and other DBA-things. |
I gave it a try. When I try to create a new project I get stuck in the dialog. Neither the "open" or "close" buttons dismiss the dialog. Here are the steps I am performing:
Expected Result: The dialog should disappear and the project should open. |
It will be nice to create document based application.
http://developer.apple.com/library/mac/#documentation/DataManagement/Conceptual/DocBasedAppProgrammingGuideForOSX/Introduction/Introduction.html
The Cocoa document architecture provides your app with many built-in features, such as autosaving, asynchronous document reading and writing, file coordination, and multilevel undo support. In most cases, it is trivial to opt-in to these behaviors. If your app has particular requirements beyond the defaults, the document architecture provides many opportunities for extending and customizing your app’s capabilities through mechanisms such as delegation, subclassing and overriding existing methods with custom implementations, and integration of custom objects.
The text was updated successfully, but these errors were encountered: