ContainedDocument allows you to nest NSDocument instances inside of abstract containers. These can be anything you need, including other NSDocument instances. This turns out to be a very tricky thing to do, and requires careful management of an NSDocumentController to make it possible.
Supporting the full range of NSDocument operations and interactions is challenging. I was able to pull off many of them, but the coordination still requires subclassing both NSDocument and NSDocumentController.
dependencies: [
.package(url: "https://github.com/ChimeHQ/ContainedDocument", from: "1.0.0")
]ContainedDocumentController
An NSDocumentController subclass that manages the NSDocument life-cycle and relationship to your containers. To use it, you must override the three container-document association methods. Restorable state is supported, but is optional.
open func associateDocument(_ document: NSDocument, to container: Container)
open func disassociateDocument(_ document: NSDocument)
open func documentContainer(for document: NSDocument) -> Container?
open func encodeRestorableState(with coder: NSCoder, for document: NSDocument)
open func restoreState(with coder: NSCoder, for document: NSDocument)
// ...Also, don't forget that an NSDocumentController is global to your AppKit process. You must instantiate your subclass as soon as possible to ensure it is being used.
ContainedDocument
This is an NSDocument subclass that makes it possible to support document duplication and window restoration.
I would love to hear from you! Issues or pull requests work great. A Matrix space is also available for live help, but I have a strong bias towards answering in the form of documenation.
I prefer collaboration, and would love to find ways to work together if you have a similar project.
I prefer indentation with tabs for improved accessibility. But, I'd rather you use the system you want and make a PR than hesitate because of whitespace.
By participating in this project you agree to abide by the Contributor Code of Conduct.