ASP. NET MVC4 creates a set of UI and background emphasis-general permission system rapid development framework + exquisite UI interface second kill EasyUi, Ext

I. Preface

It has been several years since we started the software development industry. We did a lot of repetitive things before we sorted out this development framework. Every time you have a new project, it will always take a lot of time on the UI, permissions, and general system modules. I am so tired that the boss is still not efficient. In order to improve the development efficiency, and also get more bonuses and save more private money, I started to develop a fast development framework based on permission management. Not asking for functions to be used in all projects must at least greatly improve development efficiency.

Ii. Demand Analysis

According to the requirements of various customers on the permission module, General modules, and UI in the projects we have done together in those years, I have made clear what needs to be implemented in this system.

 

1. OrganizationMulti-level tree display, easy to operate at a glance

2. UsersAll permissions are finally assigned to the user. If permissions are assigned by the user, the system administrator is exhausted. The system first creates a role, assigns permissions to the role, and adds the user to the role members. Of course, some users have the same permissions. If you do not want to create too many roles in the system, you can assign permissions to users. A set of role permissions and user permissions.

3. RoleA set of permissions.

4. ModulesIt can also be called a menu. It can be a page in the system, or the page addresses of other systems can be integrated into the same permission system for maintenance.

5. Buttons

6. PermissionsPermission assignment mode: 1) grant permissions to roles, which facilitates permission allocation.

2) Flexibility in user permission allocation and permission allocation.

Permission control type: 1) module permission: the purchaser has the permission of the procurement module and the inventory View module.

2) click the button to authorize the buyer to click the Add button to add a purchase order. The purchase manager can click the review button to review the purchase order.

3) Data permissions Each clerk can only view his or her own customer information.

4) Field permission accounting can view all fields in the inventory report, and the Warehouse administrator cannot see the amount field in the report.

5) File Permission: only the general manager and members of the Sourcing Department have the permission to purchase documents from the Sourcing Department.

7. LogsLogon logs, operation logs, and system exception logs

8. Database ManagementView database information and database backup on the front-end page

9. Access Control

10. dynamic interfacesThe interface mentioned here is the communication interface with other systems or devices. It is generally provided in the form of Webservice, WCF, and Webapi. Only one interface is exposed in the system. You do not need to modify programs when you add or modify interfaces.

11. UIFront-end framework: Uses Jquery UI, which features powerful scalability and flexibility without worrying about copyright issues.

Multiple style interfaces: accordion navigation style, desktop style, and touch screen Style

12. System Parameters

13. Code GeneratorGenerate interface and background code as needed

 

Iii. Design implementation

 

2. Program Design

The program is basically implemented in Jquery + Ajax + factory mode, with nearly 0.1 million lines of code. The subsequent modules will be explained in detail.

3. User Experience UI design

UI is like a woman's face for a software. What others see first is your face. Good people, ugly faces, must always have Singles' Day. A set of program UI beautiful program class will naturally go up. No picture, no truth. The following provides some main interfaces. The detailed implementation will also be provided in the blog below.

　　

1) system Style

A) desktop Style

B) Accordion style

C) Touch Screen Style

2. Employee management

Expand organizational unit on the left and manage employees on the right

3. Organization Management

Tree-based organizations with clear organizational structure

4. Organizational Structure

The organizational structure automatically generated by the Organization

5. Role permission Control

Role member: the user who owns the role.

Module permission: Which modules can this role operate on.

Button permission: Which buttons in this module can be operated by a role.

Data permission: the data to which the role has operation permissions.

File Permission: the role has the operation permission on which files.

6. Module button Management

Drag the button to change the display position of the button in the module.

The check status button is displayed in the module.

 

 

 

Of course, the picture will be posted here first! If you think you can understand the design ideas of these images and think they will be used in the future, please add them to your favorites,I recommend it!

I can only say that your aesthetic level must be improved if I want to say three words "Destroy three views" to him after reading some interfaces, IT is a trendy industry. If you are not busy, you will not be able to stand out. Opportunities will often leave you a place! What do you say?

 

The online test is ASP. NET.

Http: // 223.86.105.239: 801 touch screen Style

Http: // 223.86.105.239: 802 Accordion style

Http: // 223.86.105.239: 803 desktop Style

Http: // 223.86.105.239: 805 Code Generator