Design and Development of the member Management System (3)-sharing the design ideas on the main interface and the main interface

Design and Development of the member Management System (3)-sharing the design ideas on the main interface and the main interface

After a period of intensive development, the member management system finally completed and released the software. During this period, I encountered many technical difficulties and accumulated many development experiences and experiences. This article continues to introduce the technical points in this development process. This chapter mainly introduces the member management, share some design ideas on the list main interface.

Sometimes, it is always easy to follow some fixed routines to do things. If there are some innovations and improvements in each place, it usually takes a lot of time, but innovation is positive, although you may encounter difficulties, it is worth doing. In the Winform interface design, although I can use the code generation tool to generate a relatively standard interface, I always like to refer to learning and improve some interface elements, therefore, I often spend some time studying some interface details, but it can be very pleasant after completion, and can also be used as a reference for subsequent projects.

1. Completed Member Management Interface

The member information management interface in this section is divided into the left and right sides. Some attributes and status categories of members are displayed on the left, and query conditions and list content are displayed on the right. Let's take a look at the view in the design status of its member information list interface, which is basically consistent with the running interface, but some content in the list is dynamically loaded at the runtime.

 

2. Interface Analysis and Design

We use this interface effect to push back how to achieve this effect, which may be more helpful and easy to understand.

1) Design of left/right splitting and folding Interfaces

The layout of the List interface is the left and right sides, and there is an arrow in it. Double-click the arrow attachment to fold the left side. So let's take a look at how this place is implemented.

First, you need to find the SplitContainerControl control in the VS toolbox, put it in the entire form, and set its Dock attribute to Fill the entire form.

Then, set the entire control tree as follows.

Finally, we can see the left and right patterns and fold the first panel.

Add a TreeView control in the left-side pane, set its Dock attribute, and add some Tree nodes at the design time to facilitate display and processing.

Through data binding of the background code, we can dynamically construct a tree list, and the data on the list interface can also be displayed on the right, in this way, we can get the main interface effect described above.

Sometimes, we may need to use the Panel split control to associate the records of the two tables in the master and slave tables for display.

The following interface shows a consumption information table, which includes both the total consumption information and the consumption details. However, when selecting the information of the left-side primary table, refresh the Details table on the right.

 

2) Implementation of the drop-down list button

Sometimes, placing too many buttons in the list interface will look messy. Sometimes the interface may be blocked or overlapped if it is scaled down, and the interface layout will be very bad, the DevExpress control group provides a drop-down list button group control, which is convenient for saving screen controls and grouping buttons. For convenience, I put some Member-related operations together and put them together in a drop-down list button. The effect is as follows.

How can we achieve the above button effect?

The toolbar of the DevExpress component contains a corresponding button control, as shown below.

However, if you drag it up, there is no corresponding property to set the button set in it. Instead, you need to use it with these three control objects.

ImageCollection is used to set the button icon. The other two need to be paired in this example. After adding the icon, BarManger adds the toolbar, menu bar, and status bar and deletes all the default items, then, set the Manager attribute of PopupMenu to barManager1.

After completing these steps, set the pop-up button set and add corresponding event processing, as shown in the following design interface.

3) list display interface

The list display content mainly refers to the interface and background code automatically generated by the Code Generation Tool Database2sharp. The page control is used for display. I will not repeat it again to see the interface effect as follows.

 

What should I do if I develop an android project?

Does android have similar things? Do you also need to consider frameworks and other things? Please help.
------ Solution --------------------------------------------------------
If the database is used locally, it is embedded with sqlite3. If you use a remote database, you can use it as needed.
I personally think the architecture is basically mvc, but it is best to discard the web ssh framework and re-learn the beautiful design pattern of Android.
------ Solution --------------------------------------------------------
Focus on the reusability of components.
------ Solution ---------------------------------------------------------- reference:
First, let's talk about the design concept:
1. First, design the database as needed, because almost all operations should refer to the data model. 1 million people/times per day
SQL Server or mysql.
2. Secondly, design the android interface, and design the business logic to be consistent.
3. create and implement the android object class again.
4. Finally, return the request sent by the front-end server design and processing.
The above four steps are generally involved.
As for the design pattern and framework:
Some tool classes on android can be used in a single example or factory.
The android end does not need the framework (not yet ...), In the background, we recommend that you use struts2 to control and process requests.
I think so much for the moment. If you don't understand it, ask again.

Outline of the graduation design of the emergency supermarket management system

Post an article to the landlord and receive points. The information on that website is comprehensive, and each topic is available. You can refer to the document and it should meet your requirements. Abstract
The software implements dynamic computing and management for the actual operation processes of supermarkets, such as procurement, sales, warehouses, funds, and accounts, this allows supermarket operators to quickly control the company's actual operation and make reasonable strategic decisions. Software-provided inventory of commodities, commodity sales, commodity accounts, accounting accounts and various reports can be effectively mitigated on the basis of improving the company's work efficiency, reducing human errors, and maximizing the blockage of Vulnerabilities labor intensity of personnel in procurement, sales, warehouse, finance, etc, it fully embodies the efficient work and relaxed environment atmosphere advocated by modern enterprise management theories.
Key words: supermarket management; reports; finance; VC ++

Contents
Total number of papers: 50
Thread 1
1.1 System Overview 1
1.1.1 business introduction 1
1.1.2 function Introduction 1
1.1.3 Scheme Planning 1
1.2 Development Method 2
1.2.1 introduction to Object-Oriented Design 2
1.2.2 principle of object-oriented design method 2
1.2.3 object-oriented design step 3
1.3 features 4
2 system design 5
2.1 feasibility analysis 5
2.1.1 Investigation and Analysis 5
2.1.2 Necessity Analysis 5
2.1.3 feasibility analysis 6
2.1.4 Development Goal 8
2.2 Requirement Analysis 8
2.2.1 writing objective 8
2.2.2 Function Analysis 9
2.2.3 Data Analysis 10
2.2.4 schematic 10
2.3 module design 10
2.3.1 module Introduction 10
2.3.2 module block 11
2.4 Outline Design 12
2.4.1 database-erfigure 12
2.4.2 module function analysis 14
2.5 project implementation period 16
2.5.1 Development Environment 16
2.5.2 schedule of work tasks 16
2.5.3 assignment of jobs and division of labor 17
2.5.4 key issues 18
2.5.5 runtime environment 18
2.6 detailed design 18
2.6.1 database design 18
2.6.2 Design of specialized classes (detailed code reference program) 19
2.6.2 Design of proprietary controls (detailed code reference program): 26
2.6.2 Interface Design: 30
2.6.3 Menu Design: 31
2.6.4 database management design: 33
2.7 testing and running 35
2.7.1 logon page: 37
2.7.2 Main Interface: 37
2.7.3 user management: 38
2.7.4 calculator: 38
2.7.5 report page: 39
2.7.6 print interface: 39
2.7.7 Test Summary: 40
2.8 Statement of operation 40
2.8.1 basic information 40
2.8.2 warehouse receiving management 41
2.8.3 sales management 41
2.8.4 inventory management 42
2.8.5 financial management 42
2.8.6 Common Tools 42
2.8.7 database management 42
2.8.8 system management 42
2.9 Chapter 42
Conclusion 44
Xie CI 45
References 45
Appendix 46 references: www.jsjpaper.org/vc/14001.html...xu full text>