Introduction to open Source Gui-microwindows

*************************************************************************************************************** ************
Easywave Time: 2014.06.07

Category: Open source GUI system-microwindows Introduction statement: Reprint, please keep the link

Note: If there is an error, please correct me. These are the journal articles I studied ...

*************************************************************************************************************** ************

A: microwindows introduction

        Microwindows is a well-known open source embedded GUI software designed to bring the graphical Windows environment to small devices and platforms running Linux. As a replacement for X window, microwindows can use less RAM and file storage space (100k-600k) to provide features similar to X window. Microwindows allows designers to easily add a variety of display devices, mice, touch screens and keyboards. The portability of the microwindows is very good, basically implemented in C, and only some of the key code uses the assembly to improve speed. Microwindows supports ARM chips. Although Microwindows fully supports Linux, its internal portable architecture is based on a relatively simple screen device interface that can be run on many different RTOs and bare metal.

Microwindows's graphics engine can run on any system that supports Readpixel, Writepixel,drawhorzline, Drawvertline, and SetPalette. Supported by the underlying function, the upper layer implements bitmap, font, cursor, and color support. The system uses an optimized drawing function so that the user can provide a better response when moving the window. The implementation of graphics drawing and moving in memory makes screen drawing appear smooth, which is particularly useful when displaying animations, polygon drawing, arbitrary area fills, and clipping. The microwindows supports the new Linux kernel frame cache (FrameBuffer) architecture, which currently provides support for 1, 2, 4, 8, 16, 24, and 32 bits per pixel, plus support for color and grayscale display, where color display includes true Color (15, 16, and 32 bits per pixel) and color palettes (1, 2, 4, and 8 bits per pixel) are two modes. In the color display mode, all colors are given in RGB format, and the system converts it to the most similar display color, while in monochrome mode it is converted to different grayscale levels. The Microwindows supports window overlay and Subwindow concepts, full window and client area cut, scale, and fixed fonts, as well as font and bitmap file processing tools. Microwindows adopts a layered design approach. At the bottom, the screen, mouse/touch screen, and keyboard drivers provide access to physical devices. In the middle tier, a portable graphics engine is implemented that supports line drawing, area filling, clipping, and color modeling. On the upper level, a variety of APIs are implemented to suit different application environments.

II: Microwindows case

Because Microwindows uses a message to drive the display of the UI, and the Minigui and WIN32 of the early GUI of the message mechanism is the same, so long as the master of the Microwindows, basically mastered the Minigui. Below is an example picture of an actual GUI [from the network]

This section only intends to analyze the architecture of the open source Microwindows, and how to transplant and apply the problem, do not intend to analyze the domestic open source Minigui. The reason for this is that Minigui commercialization requires money, as shown below:

Therefore, it is not intended to analyze Minigui in depth, only to analyze the Microwindows architecture!