WPF组成/集合 [英] WPF Composition/Agregation

查看:79
本文介绍了WPF组成/集合的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在寻找有关在大型项目中组合和聚合用户界面的WPF最佳实践的文档。

I'm looking for documentation regarding WPF best practice for Compositing and agregating the user interface in a large project.

我来自一个视觉继承世界,使用的是Delphi和Winform。现在,我试图很好地复制这种模式,实际上是那些UI元素的可重用性。

I'm comming from a visual Inheriance world using Delphi and Winform. And I'm now try to replicate that kind of pattern well in fact reusability of those UI elements.

我愿意接受建议和阅读。

I'm open to suggestion and reading.

推荐答案

复合应用程序指南(有时称为 Prism)是合适的,尤其是在应用程序具有许多由不同团队开发的活动部件的情况下。

The Composite Application Guidance (sometimes called "Prism") is appropriate, especially if the application has a lot of moving parts developed by different teams.

我们已经使用了一段时间,虽然模式与您在Delphi中所体验的不太相似,但它们非常好,文档是优秀的。

We've been using this for a while and while the patterns aren't very similar to what you've experienced with Delp they are very good and the documentation is excellent. The functionality you get is pretty amazing.

此处提供更多信息: Codeplex上的复合应用程序指南

这篇关于WPF组成/集合的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆