定制应用程序框架 [英] Custom application framework

问题描述

作为开发将提供给第三方开发人员的自定义应用程序框架的团队的一部分，我需要提出一个简单而完整的解决方案，以使开发人员可以自定义视图(A)和我们解决方案的主应用程序布局(B).

对于 B ，我们将使用自定义UI组合方法(类似于Prism，但更简单)，其中主应用程序布局将由第三方配置.

至于 A ，我们将创建需要自定义的UserControl，这些控件可能由第三方完全覆盖".

建议的解决方案:

i)给出主布局文件和用户控件(A和B)的XAML代码.在A的情况下，第三方开发人员将能够使用默认的UserControl(位于视图"/默认值"中)，或者通过在视图/自定义"中创建相同的控件来完全覆盖它.

ii)给出主布局文件和UserControls(A和B)的XAML代码，并使用IoC(例如Unity)交换/扩展它们.

我的问题:

1.-对提议的解决方案有何评论?还有其他想法吗?
2.-你知道有人开发过这样的东西吗?


此外，无论我们想出什么，它都可以在 WPF ， Silverlight 和 ASP.net 上工作，因为该框架支持这三种技术.通过这种技术的重用，我的意思是发布"机制，而不是在WPF/SL/ASP之间重用XAML文件(没有任何意义！)

谢谢，

As part of the team developing a custom application framework that will be given to 3rd party developers, I need to come up with a simple yet complete solution in order to let the developers customize views (A) and the main application layout (B) of our solutions.

For B, we will be using a custom UI composite approach (similar to Prism, but simpler), where the main application layout will be configurable by the 3rd parties.

As for A, we will create UserControls that need to be customized and perhaps completely "overridable" by the 3rd parties.

Proposed solutions:

i) Giving out the XAML code of the main layout file and the the UserControls (A and B). In the case of A, the 3rd party developers will be able to use a default UserControl (located lets say in Views/Default) or to completely override it by creating the same control in Views/Custom.

ii) Giving out the XAML code of the main layout file and the UserControls (A and B) and use IoC (Unity for example) to swap/extend them.

My questions:

1.- Any comments regarding the proposed solutions? Any other idea?
2.- Do you know of anyone who has developed something like this?


Besides, whatever We come up with it should work on WPF, Silverlight and ASP.net, as the framework support those three technologies. By this reuse of technologies, I mean the "publishing" mechanism, not reusing the XAML files among WPF/SL/ASP (makes no sense!)

Thanks,

推荐答案

XAML的一个子集适用于WPF和silverlight. XAML不适用于ASP.NET，或者远程具有与WPF一样丰富的ASP.NET.因此，如果您想要统一的支持，则必须接受WPF应用程序将非常la脚，只能达到ASP.NET表单的水平.

A subset of XAML works for WPF and silverlight. XAML does not work for ASP.NET, or is ASP.NET remotely as rich as WPF. Therefore, if you want uniform support, you have to accept that you WPF apps will be pretty lame, being only as good as an ASP.NET form can be.

的确如此.我可能忘了提及所提出的解决方案的范围仅是WPF/Silverlight.对于ASP.net，应使用其他名称(如果可能，则使用类似的想法).

Indeed. I might have forgotten to mention that the scope of the proposed solutions is just WPF/Silverlight. For ASP.net something else (if possible using a similar idea) shall be used.

这篇关于定制应用程序框架的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！