The Taligent Programming Model for .Net

Has anyone created a control architecture using the taligent programming model as follows?

http://www.wildcrest.com/Potel/Portfolio/mvp.pdf

The question is how do you implement or map the IInteractor concept (Page 9) to a .net interface? Currently the guess is to use the IInputElement interface as a the event source for all UI input controls.

If anyone has already implemented the taligent pattern in .net I would like to know if it is applies to both Silverlight and WPF? If yes does it apply to the union of their interfaces.

Finally this represents the unified fractal abstract architecture and can displace PresentationFramework.dll. If you see this applies as a control architecture please comment.

From stackoverflow

• That depends on what you mean by ".net". The term covers many kinds of applications. Web apps, Web Services, Windows Forms apps, WPF apps, etc...

  MVP is used a lot in ASP.NET Web apps. See:

  http://msdn.microsoft.com/en-us/magazine/cc188690.aspx

  Fire Garden : You don't get it. A unified architecture would compile to all those

  Mystere Man : Not really. There is an inherant difference between a stateful and stateless architecture, ala web vs GUI. It would be quite difficult, and likely highly inefficient to try and unify them.

  Fire Garden : Actually web and gui are converging. You just dont see it man. Sorry.

  Mystere Man : Of course they are converging. But that doesn't mean they can be treated the same from a programming perspective. They are fundamentally different backend concepts, even if you treat them the same on the front-end.

  Fire Garden : No they are not. You are confusing REST with RPC

• The article How to: Implement the Model-View-Presenter Pattern of the MSDN patterns & practices section seams to be what you are looking for...

  Fire Garden : Thank you for the comment however this does not address a number of interfaces in the taligent pattern such as ISelection, ICommandOn<> and IInteractor. Basically no one is doing this right now and it will displace PresentationFramework.dll (puke layer) leaving PresentationCore.dll or System.windows

• We have created a complete MVP framework for .NET, based on the Taligent ideas. It took us some time to get right but now we can create applications by writing business classes, creating a new form and drag-dropping the properties of a class onto the form.

  The framework is very sophisticated and allows for the customisation of forms at runtime, as well as automatically hooking up validation in the business classes to edits on the form.

  We also wrote an OPF (Object Persistence Framework) to complement it, so avoiding the need to manage database code as well.