mvp

问题 From last few days i have been searching the optimal architecture for my new web application, which would be devloped in ASP.Net using C#. Until now, i only find and study following 3 Three Tier Architecture (Note: By Tier i mean logical layer) Model View Controller (MVC) Model View Presenter (MVP) Now folling are my questions: 1) As far as i understand 3 Tier Architecture and MVP can I say that MVP and 3 Tier are the same thing? If not, then what is the difference bewtween both? (Note: I

问题 I have a Presenter that takes a Service and a View Contract as parameters in its constructor: public FooPresenter : IFooPresenter { private IFooView view; private readonly IFooService service; public FooPresenter(IFooView view, IFooService service) { this.view = view; this.service = service; } } I resolve my service with Autofac: private ContainerProvider BuildDependencies() { var builder = new ContainerBuilder(); builder.Register<FooService>().As<IFooService>().FactoryScoped(); return new

问题 I recently read Phil Haack's post where he gives an example of implementing Model View Presenter for ASP.NET. One of the code snippets shows how the code for the view class. public partial class _Default : System.Web.UI.Page, IPostEditView { PostEditController controller; public _Default() { this.controller = new PostEditController(this, new BlogDataService()); } } However, here the view constructs the instance of the BlogDataService and passes it along to the presenter. Ideally the view

问题 In my MVP applications I use code such as the following to wire my Presenter and View: View view = new View(); Presenter presenter = new Presenter(view); view.setPresenter(presenter); The View class is constructed in a temporarily invalid state, which the call to setPresenter rectifies. I have some code in the View class that throws an IllegalStateException if the View is used without the Presenter being configured. I was hoping Spring could wire this relationship together with a

问题 I am creating an Android application which basically calls an web service and shows back the response; and I am following the MVP pattern to accomplish it. So the biggest & basic challenge is to check the internet status before every call. I was thinking to create an Abstract layer between the Presenter & the API . So the API request will pass first from the Abstract Internet Layer and if it passes successfully then only the API will get called. Creating a separate layer looks a better

问题 I am new to the whole MVP thing and slowly getting my head around it all. The a problem I am having is how to stay consistent with the MVP methodology when populating GridViews (and ddls, but we will tackle that later). Is it okay to have it connected straight to an ObjectDataSourceID? To me this seems wrong because it bypasses all the separation of concerns MVP was made to do. So, with that said, how do I do it? How do I handle sorting (do I send over handler events to the presentation layer

问题 I would like to implement the MVP pattern in my web application using Vaadin. I am using the Vaadin Navigator and the CDIViewProvider, something like so: //MyUI.java public class MyUI extends UI { @Inject CDIViewProvider viewProvider; Navigator navigator; @Override protected void init(VaadinRequest vaadinRequest) { //UI setup navigator = new Navigator(this, someContainer); navigator.addProvider(viewProvider); getNavigator().navigateTo("myView"); } } //MyViewImpl.java @CDIView("myView") public

问题 Is it a popular techinque to use the Model View Presenter (MVP) design pattern when creating Web Parts for SharePoint? It seems (to me) that this pattern is applied more often in the custom application space. So, if you have any thoughts on this, please share... [Edit] Perhaps the more important question is, if MVP is less popular in a SharePoint WebPart than in a custom application, why do you think this is (what factors contribute to this observation)? 回答1: It's probably not popular, but it

问题 I have this web application which I have made with MVC pattern, however I am trying to adapt the MVP pattern. I am using the GWTPlatform library which I have migrated some of the codes already, mainly to the Presenter and the View . However I have not seen any comprehensive material to explain how to actually deal with the Model part. In my MVC pattern I have the model in the controller (in MVC) and the Views listen to changes in the Model to update the views. The model is updated by the

问题 What is common practice, one presenter for View view and one for Edit view, or should it be all in one presenter. 回答1: The rule of thumb which I follow is... - 1 Presenter 1 View But for common controls you could share the presenter if the presentation logic is same... For eg... You have a Dialog control for "Confirmation dialog", "Operation Complete dialog!", and many other variants... For this I had this control realize from a common view interface and had one presenter serving the whole