Overview of XAF-UI elements, xaf-ui Overview

Overview of XAF-UI elements, xaf-ui Overview

XAFBased on the business model, the FrameworkAutomatically generate the default UI. Generally, you can use the default user interface, but if it does not meet your requirements, you can customize it. To do this, you should know what elements the UI consists of and what elements you can customize to implement replacement or adding functions.

General information about this is provided in this topic. For more information about each element, see other topics in this help section.

InIn the XAF frameworkAnd defines some abstract elements. On the actual platform, the abstract elements are used to draw the true elements, that is, the abstract elements describe the content of the actual elements.

The following figure shows the abstract UI elements and corresponding controls in Windows Forms and ASP. NET Web application versions.

To put it simply, the annotation text in is some objects (classes) defined in XAF ).

What is an image extraction element?

This control does not exist in web/win. XAF defines a class, such:

DetailViewItem (PropertyEditor) refers to the class encapsulated by controls such as TextBox and DropDownList, that is, TextBox is generated by PropertyEditor.

I already have a lot of controls. Why should I create another PropertyEditor? So many concepts are annoying ....

Cause: textbox implementation in web/win/mobile is different. For example, win control is used in win, html input is used in web, and cannot be controlled in a centralized manner, unified Definition.

For another example, we need to set a required field for verification. In XAF, we write [RuleRequiredField] directly on BO (Business Object), no matter what type of attribute, you can do this.

So how does XAF enable the control to have the verification function?

The answer is to wrap the control once. In the packaging, it is required to set how to verify the features of each control.

 

The following list provides the summary of the UI element.

• Window)
  It uses the Template to display the UI. It inherits the Frame class and aims to include WindowController.
• Frame
  It can be understood that this is a view container. There is only one view in a Frame, and the Frame contains a set of controllers, that is, the controllers in the Frame. You can set a view for a Frame.
• Template)
  It refers to the final Interface Template, and specific controls are usually formulated in the module. For example, XAF win has a ribbon as the main control template, and also has a common toolbar form.
• View)
  Currently, XAF has three main types of views:
  • DetailView is used to add and edit data. The display attribute corresponds to a control.
  • ListView is used to display multiple data items, including Grid, tree, and calendar.
  • DashboardView is similar to DetailView, but its function is to combine multiple views into one view. For example, two detailviews are displayed together. Of course, the quantity is unlimited.
• ViewItem)
  ViewItem refers to a small control, such as TextBox and DropDownList. Of course, an Excel table editing control is large, but it can also be a view, but it is only applied to DetailView and DashboardView, used to modify a certain attribute value of a business object.
• Action (button)
  The abstraction of the buttons on the interface, where you only need to write logic. For example, you can click a button to perform data operations or interface operations. For example, a dialog box is displayed, display a view or save data changes.
• ActionContainer
  The button container, that is, the button is displayed here.