Javascript Architectural Model
Are there any obvious flaws to this OO architectural model which I intend to implement using javascript? It is similar to the MVP model but instead the role of the model is broken down into three modules:
MVP Implementation at the UserControl Level
I’m trying to figure out how MVP should be implemented at the UserControl level. I thought I had it, but I ended up reading a blog post that pretty much shut me down. Now I’m back at the start and with no idea how to proceed.
design in agile process
Recently I had an interview with dev team in a company. The team uses agile + TDD.
The code exercise implements a video rental store which generates statement to calc total rental fee for each type of video (new release, children, etc) for a customer. The existing code use object like:
Loose Coupling Presenter to View in MVP
We work in a Java shop here and our web application uses an implementation of the MVP architectural pattern. Our manager comes from a .NET world, where he has been exposed to the MVVM design pattern. Our manager is advocating changes in our MVP implementation, including that the Presenters should be decoupled from (or loosely coupled to, depending on your interpretation) its Views via the Observer design pattern, in tradition with MVVM. I am more of the opinion that the Presenter and the View work together to achieve a common goal, and as such should be coupled.
Designing storage service data structure for decoupled models sharing same data
Surely most of you remember the Norton Commander application where similar (sometimes the same) data is displayed in separate decoupled views.
Designing storage service data structure for decoupled models sharing same data
Surely most of you remember the Norton Commander application where similar (sometimes the same) data is displayed in separate decoupled views.
Designing storage service data structure for decoupled models sharing same data
Surely most of you remember the Norton Commander application where similar (sometimes the same) data is displayed in separate decoupled views.
Designing storage service data structure for decoupled models sharing same data
Surely most of you remember the Norton Commander application where similar (sometimes the same) data is displayed in separate decoupled views.
Designing storage service data structure for decoupled models sharing same data
Surely most of you remember the Norton Commander application where similar (sometimes the same) data is displayed in separate decoupled views.
How much segregation is too much in this design?
We are working on ASP.NET webforms application developed using WCSF (MVP pattern). In the application, there is a search screen that allows the user to enter some fields and display the results.