We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(2)
据我所知,文档不存在(除了代码本身)。
有些控件只是简单的包装器,可以为您进行本地化(即仅设置
Text
属性,不要使用ResourceKey
)。某些控件使用相应的 Telerik 控件,向控件应用外观(简单外观加上来自 DNN 外观的潜在控件特定 CSS),并执行本地化(1)。如果您没有 Telerik 许可证,这些包装器是您对捆绑的 Telerik 控件的唯一访问权限。
一些控件是更具规范性的控件组合。
我的假设是 DNN 将开始专门使用这些控件,因此使用它们将有助于站点的一致性。然而,这并不是一个巨大的优势(或官方宣布的),所以在更容易忽略它们的地方,不要太担心。
(1)需要注意的一点是,DnnGrid 中存在一些定位不良的问题,这些问题已在 DNN 5.6 中得到修复。
Documentation is non-existent, so far as I can tell (outside of the code itself).
Some of the controls are just simple wrappers which do localization for you (i.e. just set the
Text
property, don't useResourceKey
).Some of the controls use the corresponding Telerik control, apply a skin to the control (Simple skin plus potential control-specific CSS from the DNN skin), and also do the localization(1). If you don't have a Telerik license, these wrappers are your only access to the bundled Telerik controls.
Some of the controls are more prescriptive combinations of controls.
It is my assumption that DNN is going to start using these controls exclusively, so it will help the uniformity of your site to use them. However, it's not a huge advantage (or officially announced), so where it's easier to ignore them, don't get too worried.
(1)One thing to note is that there are some issues with bad localization in the DnnGrid which is fixed in DNN 5.6.
将有一个风格指南来描述所有可用的控件,DevConnections(由 Shaun)提到过。它还涉及一些最佳实践。
我知道它在 DNN Corp 内部和一些 UX 茶上流传,但我不确定它什么时候会公开。
There will be a style guide that describes all of the controls available, it was mentioned at DevConnections (by Shaun). It also touches on the some best practices too.
I know it is floating around internally @ DNN Corp and to some on the UX teas but I am not sure when it will be publicly made available.