Silverlight enterprise application Quick Development Platform Framework Design (3) analysis-Page Model

We have analyzed 5 commonly used page parts.

Under normal circumstances, it is enough to have these five parts.

However, the preceding five parts have no significance for separate use. The five parts can be compared to raw materials,

Then we need to process the <general page model> (finished product) we need)

What general page models do we usually need?

As summarized here, the general enterprise database application system develops a 80% page model, such:

 

Ui1. List Model

Almost 60-80% of a project is like this.

The query results are displayed on the list based on the query conditions, and some operation functions are also provided.

Basic components include:

Example:

Example: A typical list Screen

It consists of three parts:

1. Functional buttons on the top ---- the component analyzed above is the "functional component"

2. The middle part is the query input box. The component analyzed above is the "query component"

3. The following section shows the list display function. The list parts are analyzed as follows"

 

Ui2. Edit the page model:

Page for adding and modifying data

Provides basic user input controls

Provides function buttons for human-computer interaction, such as saving, copying, and deleting.

The component composition diagram is as follows:

Example:

The editing page model shown in is very common in a project.

Since the repetition rate is so high, it is necessary to abstract such a page model.

Encapsulate the public parts in this model. Different parts can be done through configuration.

In this way, we have developed such a page model to respond to the 10, 20, or more editing images you will be able to face throughout the project.

The specific implementation will be discussed later. Here we find the page model to be abstracted.

 

Ui3. List editing Model

This is a simple combination model

Components include:

Example:

For example, this is a list editing page:

In fact, ui1 and ui2 are integrated into one screen.

In our software development process, such maintenance images may be required.

For pages with complicated maintenance content, we click Add or modify to jump to or bring up a new screen for data maintenance.

For some simple images, the customer may need to add, delete, modify, and query all the functions on the same page as before.

The composition of ui3 is ui1 + ui2

After ui2 is successfully saved, you must refresh the data in the ui1 list page model. The data coordination mechanism is completed by ui3.

 

Ui4. Tree Page Model

I have also analyzed the tree component. What is its use scenario? Don't worry

Ui4-tree page model structure:

Example:

For example, function menu maintenance is a typical tree model image.

Ui4-the tree-like page model is mainly used to maintain data with parent-child relationships.

For example, it is intuitive to use tree components on the left to display data.

On the right side, we do not develop code repeatedly. We directly use ui2 to edit the page model.

If <ui2-Edit page model> is a finished product, this is correct. It can indeed be used as a page for end users.

However, <ui2-Edit page model> can also be considered as a semi-finished product. For example, in <ui4 tree-like page model>, it is a component.

Nesting can be easily implemented, thanks to the strength of Silverlight.

Uielement can be customized.

 

Ui5-relationship Page Model

Link Page Model: as its name implies, it is a special page used to maintain links.

For example, maintain a role corresponding to a user

One user can have multiple roles

We usually provide the role data list control in this screen for you to select, the selected is the user role currently maintained

Explanation: for example, the editorial component is used to display the objects currently being maintained.

The query component is used to search and query roles. For example, you can enter specific query conditions to locate roles.

List parts, query results for selection

Perhaps, I noticed that this so-called relationship page model is very similar to that of the ui3 list editing page.

The only difference is the list part. After a query, the data rows of the objects whose data has been set must be checked automatically.

Ui6-Compound Model

In fact, you have also come into contact with a simple composite model, ui3-list editing model.

The composite page model mentioned here is a more complex and powerful page model.

All the page models summarized above can be used by composite models.

Diagram:

 

Example:

For example, a program is a typical application of a composite page model.

First, it combines: for example, the merging link header: ui2 editing Model

Combined: such as the merged component: uilist Model

And so on.

 

 

Now we have analyzed and summarized the above six page models that we need to develop.

After the six page models are developed, 80% of software coding problems can be solved

 

Therefore, according to the above analysis

We will focus on developing 5 components as shown in Figure 5.

 

Use the above five component components for our page model

For example, the control in the red box is a series of page models we have summarized. We can use it to implement the 80% software without coding. All of them are implemented using configuration.

We use the same configuration development platform for software configuration definition, and the final software configuration development platform will generate xml,

Then, the XML is handed over to the above page model. The page model will automatically generate the screen according to the description in the XML. You do not need to perform code development manually.