I am currently implementing a project using asp.net, C # and the MVP (Model-View-Presenter) template. The main goal of this solution is to provide a schedule for the consumer to be used by various systems. This is basically a custom graph server.
The browse page in this particular case has an MSChart control on it, which should be dynamically populated and configured based on the parameters in the QueryString. This can be as diverse as completely different types of datasets, display modes, etc., using the many properties of a chart control.
Many of these properties again relate to the types that are characteristic for controlling a chart, and will require the same dependencies as the chart control itself, if they must be set by the master.
I am trying to figure out how to best show the properties of the leader so that he can deal with his magic.
Should I:
- Just output the entire chart object and live depending on the type of system.web in the presenter project?
- Set access and translation properties for all chart management properties so that I don't have a dependency, but add a lot of complexity?
- Another thing I did not think about?
, MVP , , DTO , , , , .
- , MVP?