Duilib Source Code Analysis (i) overall framework

Duilib Interface Library is an open-source library developed by Hangzhou Crescent Moon Network Technology Co., Ltd. to develop on the basis of the Uilib library under the Viksoe project (and thereafter the source analysis of the Uilib library); Through the XML layout interface, the user interface and processing logic are completely separated, Greatly improve the development efficiency of the user interface. Generally used to develop small projects Windows desktop client software, whose child window is not created as a window handle, just a logical window, drawn on the parent window. The current open source agreement to the BSD release, can be used for commercial applications, well, other more detailed introduction, please check its official website or Baidu.

SOURCE Access:

At present, Duilib is not maintained, basically the network of various duilib versions are personal maintenance, the original Duilib source code can be obtained in github:https://github.com/disable/duilib; Also the more active version: Https://github.com/redrains/DuiLib_Redrain; and Https://github.com/duisharp/DuiLib_Ultimate In addition, an extended version: HTTPS://GITHUB.COM/SHAOYUAN1943/DUILIB_EXT; To facilitate understanding of the Dullib project, we will use the original version of the Duilib source code analysis.

Source File organization:

Source files are mainly divided into: Duilib Library, the Duidesigner Designer for XNL script configuration, the DOC documentation primer, the bin compiled designer and Duilib.dll, and the XML resources required for each demo, various use case demos, and a list of properties containing various controls . XML, other non-important files;

Off-topic-"Source code Analysis steps:

Basically, the steps to analyze the source code should be roughly:

1. Read the official profile to understand its features, functions, and application scenarios;

2. Obtain a series of documentation such as source Code and development documentation;

3. Consider how the project should be structured, functional implementation, etc.

4. Compile the source code, execute the procedure smoothly, observe the execution effect, and follow the procedure from the entry point;

5. First understand the approximate operation mode of the project, the structure of the module, experience the design patterns which can be learned;

6. Learn from the details of the use of the customary usage, kinky skills;

7. Compare with the 3rd step and feel the similarities and differences between the project realization and their own ideas;

8. In the course of learning to make notes, sketches, and if there is time to suggest that you can try to achieve the project, copy some of the source code to step learning is also a good way.

In fact, everyone learns differently, some people start with a development document or a starter manual, and some people start to understand the use of the demo use case.

Later will be the Dullib library file analysis instructions, other such as designers please self-view the Getting Started manual and use, because the designer will produce a lot of useless code and there is a bug, post-configuration xnl can be filled in manually, after filling out can be a simple designer to see the effect can:

Dullib Library:

File structure:

Core: Kernel components (renderer, container, builder, parser, control base class);

Layout: Interface component (horizontal, vertical, child control, tab, etc.);

Utils: Auxiliary Tools related (decompression, image, window base class, delegation, etc.);

Control: Various controls (Button, Combox, label, checkbox, List, etc.);

Duilib Source Code Analysis (i) overall framework