blocks|key|4479244|text|您必须记住，.h是一个公共标头。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4479245|所以把你的IBOutlet放在那里，如果它们应该被其他类访问的话。|offset|length|style|CODE|4479246|然而，即使你能做到这一点。我要说的是，在公共标头中公开IBOutlet不是一个好的做法(从面向对象的角度来看)，因为您正在公开一些实现细节，这些细节应该只对关心的人可见。|4479247|简而言之，将IBOutlet放在.m的类扩展中是一种很好的做法。|4479248|entityMap^0|0|5|8|0|R|8|0|6|8|G|2|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@$D|V|E|W|F|G]|$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|M|$]]

You have to keep in mind that .h is a public header.

So place your <code>IBOutlet</code>'s there if they should be accessible by other classes.

However, even though you can do that. I would say that exposing the <code>IBOutlet</code>'s in a public header is not a good practice (From object orientation perspective) since you are exposing some implementation details that should be only visible to whom is concerned about.

In short, placing the <code>IBOutlet</code>'s in a class extension in the <code>.m</code> is a good practice.

blocks|key|4479177|text|来自苹果的Resource+Programming+Guide:+Nib+Files|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4479178|4479179|出口通常被认为是定义类的私有属性；除非有理由公开该属性，否则应将属性声明隐藏为类扩展。|blockquote|4479180|4479181|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/LoadingResources/CocoaNibs/CocoaNibs.html^0|5|11|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|V|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

From Apple's <a href="https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/LoadingResources/CocoaNibs/CocoaNibs.html" rel="noreferrer">Resource Programming Guide: Nib Files</a>:

<blockquote>
 Outlets are generally considered private to the defining class; unless there is a reason to expose the property publicly, hide the property declarations a class extension.
</blockquote>

blocks|key|4479124|text|如果你不想公开这个出口，那么类扩展是最好的地方。您的.h应该整洁干净，并且应该只包含那些公共的方法或属性(可供其他程序员使用)。这样，您就不会因为在.h文件中没有不必要的ivars和方法减速而使您的队友感到困惑|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4479125|这一切都是为了管理代码，减少混淆，否则Objective-C中就没有私有方法/属性了|4479126|此外，如果你检查任何苹果样本，它们都遵循相同的模式。例如，LoadingStatus.m有代码|4479127|#import+"LoadingStatus.h"

@interface+LoadingStatus+()

@property+(nonatomic,+strong)+UIActivityIndicatorView+*progress;
@property+(nonatomic,+strong)+UILabel+*loadingLabel;

@end|code-block|syntax|javascript|4479128|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/ios/samplecode/PhotoMap/Listings/PhotoMap_LoadingStatus_m.html#//apple_ref/doc/uid/DTS40011109-PhotoMap_LoadingStatus_m-DontLinkElementID_4^0|Q|2|22|2|0|0|T|F|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|J|3|K|5|L|7|16|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

Class extension is the best place if you don't want to expose that outlet publicly. Your <code>.h</code> should be neat and clean and should only contain those methods or properties which are public (available for other programmers).
In this way you won't confuse your teammate by not having unnecessary ivars and methods deceleration in <code>.h</code> file

It's all about managing the code and making less confusion, otherwise there are no private methods/properties in Objective-C

Also if you check any sample of apple they follow the same pattern. e.g. <a href="https://developer.apple.com/library/ios/samplecode/PhotoMap/Listings/PhotoMap_LoadingStatus_m.html#//apple_ref/doc/uid/DTS40011109-PhotoMap_LoadingStatus_m-DontLinkElementID_4" rel="nofollow">LoadingStatus.m</a> has code 

<pre><code>#import "LoadingStatus.h"

@interface LoadingStatus ()

@property (nonatomic, strong) UIActivityIndicatorView *progress;
@property (nonatomic, strong) UILabel *loadingLabel;

@end
</code></pre>

blocks|key|4479100|text|假设这是一个视图控制器，选项b更好，因为您不应该公开插座以供其他类直接交互。他们应该被认为是你的私人知识。你的控制器应该公开一个不同的更合适的接口。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4479101|如果它是一个视图，那么你应该如何处理这个问题就有点灰色了，因为MVC会引导你暴露插座，允许控制器使用它们。MVVM将引导您隐藏插座，以便将视图传递给视图模型对象并在内部配置插座。|4479102|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Assuming that this is for a view controller, option b is better as you shouldn't be exposing the outlets publicly for other classes to directly interact with. They should be considered your private knowledge. Your controller should expose a different and more appropriate interface.

If it's a view it's a bit more grey how you should approach the problem as MVC would lead you towards exposing the outlets to allow the controller to use them. MVVM would lead you towards hiding the outlets so that the view is passed a view model object and internally configures the outlets.

blocks|key|949401|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|949402|+@接口可以出现在.h文件(公共属性)和.m文件(私有属性)中。应该在.m文件中声明IBOutlets。|blockquote|949403|949404|949405|如果你对此感兴趣，请阅读+topic。|offset|length|style|BOLD|949406|干杯!|949407|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/28806489/iboutlet-declaration-place^0|0|0|0|0|D|6|D|5|0|0|0|3|0^^$0|@$1|2|3|-4|4|5|6|V|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|W|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|X|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|Z|7|@$H|10|I|11|J|K]]|8|@$H|12|I|13|1|14]]|9|$]]|$1|L|3|M|4|5|6|15|7|@$H|16|I|17|J|K]]|8|@]|9|$]]|$1|N|3|-4|4|5|6|18|7|@]|8|@]|9|$]]]|O|$P|$4|Q|R|S|9|$T|U]]]]

<blockquote>
 The @interface can appear in both the .h file (public properties) and the .m file (private properties). The IBOutlets should be declared in the .m file.
</blockquote>

If you are interested read this <a href="https://stackoverflow.com/questions/28806489/iboutlet-declaration-place">topic</a>.

Cheers!

I would like to know which place is best for placing the IBOutlets from storyboards:

a) In the header file (.h)

b) In a class extension created on the .m file

Thank you

Regards

IBOutlet best practices

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想知道哪个地方最适合放置故事板中的IBOutlets：a)在头文件(.h)中b)在.m文件上创建的类扩展中谢谢问候

问IBOutlet最佳实践
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问IBOutlet最佳实践EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问IBOutlet最佳实践
EN