惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

IT之家
IT之家
Microsoft Azure Blog
Microsoft Azure Blog
人人都是产品经理
人人都是产品经理
博客园 - 聂微东
博客园_首页
阮一峰的网络日志
阮一峰的网络日志
V
V2EX
小众软件
小众软件
F
Fortinet All Blogs
Microsoft Security Blog
Microsoft Security Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
H
Hackread – Cybersecurity News, Data Breaches, AI and More
量子位
Google DeepMind News
Google DeepMind News
Jina AI
Jina AI
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
aimingoo的专栏
aimingoo的专栏
B
Blog RSS Feed
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
宝玉的分享
宝玉的分享
有赞技术团队
有赞技术团队
J
Java Code Geeks
WordPress大学
WordPress大学
The Cloudflare Blog

博客园 - Ellipse

Design by Contract what's interface Provider, Manager, Helper - Ellipse Build your own CAB #13 - Embedded Controllers with a Dash of DSL Build your own CAB#12 - Rein in runaway events with the "Latch " Build your own CAB#11 - Event Aggregator Build your own CAB Part #9 - Domain Centric Validation with the Notification Pattern Build your own CAB Part#8 - Assigning Responsibilities in a MVP pattern Build your own CAB Par#7 - what's the Model? Having a break Build your own CAB Part #6 - View to Presenter Communication Build your own CAB Part #4 - The Passive View Build your own CAB Part #3 - The Supervising Controller Pattern Build your own CAB Part #1 - The Preamble(Jeremy D. Miller) Build your own CAB Part #2 - The Humble Dialog Box -- Jeremy D. Miller Gridview 的RowCommand Reading Build your own CAB (1) -- Jeremy D. Miller ActionList Webpage redirection
Layer supertype for MVP - Ellipse
Ellipse · 2007-10-11 · via 博客园 - Ellipse

Presenter: public interface IPresenter
    {
        
/// <summary>
        
/// Binds the view.
        
/// </summary>
        
/// <param name="view">The view.</param>
        void BindView(object view);
        
/// <summary>
        
/// Binds the model.
        
/// </summary>
        
/// <param name="model">The model.</param>
        void BindModel(object model);
        
/// <summary>
        
/// Gets the type of view.
        
/// </summary>
        
/// <value>The type of view.</value>
        Type TypeOfView { get; }
        
/// <summary>
        
/// Gets the type of model.
        
/// </summary>
        
/// <value>The type of model.</value>
        Type TypeOfModel { get; }
    }

 

the common actions for presenter is that: know the IModel and IView

 public abstract class Presenter<ViewType, IModelType> : IPresenter
        
//where IModelType : IServiceInterface
    {
        
/// <summary>
        
/// The view
        
/// </summary>
        protected ViewType view;/// <summary>
        
/// The model
        
/// </summary>
        protected IModelType model;/// <summary>
        
/// Gets a value indicating whether this <see cref="Presenter&lt;IViewType,
IModelType&gt;"/>
is initialized.
        
/// Only when both view and model are binded, a presenter is initialized.
        
/// </summary>
        
/// <value><c>true</c> if initialized; otherwise, <c>false</c>.</value>
        public bool Initialized
        {
            
get
            {
                
return view != null && model != null;
            }
        }
#region IPresenter Members/// <summary>
        
/// Binds the view.
        
/// </summary>
        
/// <param name="view">The view.</param>
        public void BindView(object view)
        {
            Check.Require(view 
!= null"view could not be null.");
            Check.Require(
typeof(ViewType).IsAssignableFrom(view.GetType()),
"
view's type does not match Presenter's view type.");
            
this.view = (ViewType)view;
        }
/// <summary>
        
/// Binds the model.
        
/// </summary>
        
/// <param name="model">The model.</param>
        public void BindModel(object model)
        {
            Check.Require(model 
!= null"model could not be null.");
            Check.Require(
typeof(IModelType).IsAssignableFrom(model.GetType()),
 
"model's type does not match Presenter's model type.");
            
this.model = (IModelType)model;
        }
/// <summary>
        
/// Gets the type of the view.
        
/// </summary>
        
/// <value>The type of the view.</value>
        public Type TypeOfView
        {
            
get
            {
                
return typeof(ViewType);
            }
        }
/// <summary>
        
/// Gets the type of the model.
        
/// </summary>
        
/// <value>The type of the model.</value>
        public Type TypeOfModel
        {
            
get
            {
                
return typeof(IModelType);
            }
        }
#endregion
    }

likewise, you can have several IModel for a presenter as well.

then we can have a PresenterFactory responsible for the action "BindModel" and "BindView"