GNUstep/Objective-c 和 nib 文件
我认为我不完全理解对象及其源文件如何与 Gorm 交互。当您对 NSObject 这样的类进行子类化时，它似乎会根据您如何使用插座和操作配置该对象来存储该对象的快照。
我的第一个问题是这个类存储在哪里（在将其实例化到笔尖之前，因为它不是实现文件并且还不在笔尖中？
AppController（我的自定义子类）的配置存储在上图中，它是临时文件吗？因为它在实例化之前就存在
。是该类的快照，但您还没有实现它，那么它是如何冻干到笔尖的，如果您可以在保存 *.gorm 文件后进行配置
？ .sstatic.net/v83Ev.png" alt="在此处输入图像描述">
上图中，AppController的图标似乎是对象，但我还没有写实现，所以在什么时候以及如何两者是绑定在笔尖上的AppController。充当对象的代理，或者在编译时将对象序列化到笔尖中？
抱歉，如果这令人困惑，我会尽力解释我的问题。我非常感谢任何帮助。 :-)
I don't think I fully understand how the objects and their source file interact with Gorm. When you subclass a class like NSObject, it seems to store a snapshot of that object according to how you configure it with outlets and actions.
My first question is where is this class stored (before it's instantiated into the nib, because it's not the implementation file and it's not in the nib yet?
Where is the configuration for AppController (my custom subclass) stored as it is located in the image above? Is it a temporary file, because it exists before instantiation.
Now once it is instantiated it seems to be a snapshot of that class, but you haven't implemented it yet, so how is it freeze dried into the nib, if you can configure after you have save the *.gorm file?
In the picture above, the icon for AppController seems to be the object, but I haven't written the implementation yet, so at what point and how are the two bonded. Is AppController in the nib act like a proxy for the object, or is the object serialized into the nib when I compile it?
Sorry if this is confusing, I tried to explain my question as good as I could. I greatly appreciate any help. :-)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当笔尖在运行时加载时，它们被绑定。 nib 包含类的名称（不是持久化实例）；加载笔尖时将创建一个实例。作为其中的一部分，nib 加载程序还将将该新实例与您告诉它应该连接到它的任何操作连接起来。
They are bonded whe the nib is loaded at runtime. The nib contains the name of the class (not a persisted instance); an instance will be created whe the nib is loaded. As part of that, the nib loader will also connect that new instance up with any actions you've told it should be connected to it.