MiniGUI

A modern and proven cross-platform window system for embedded systems or smart IoT devices.

TABLE OF CONTENTS

TABLE OF CONTENTS
INTRODUCTION
NEW FEATURES IN VERSION 5.0.x
NEW FEATURES IN VERSION 4.0.x
NEW FEATURES IN VERSION 3.2.x
THE RUNTIME MODES OF MINIGUI
A BRIEF BUILDING INSTRUCTION
Othere Resources
- MiniGUI Components
- Open Source Apps Based-on MiniGUI
HISTORY
AUTHORS AND COPYING
- Special Statement
- Not Free for Commercial Use
A LITTLE FAQ

INTRODUCTION

What's MiniGUI

MiniGUI aims to provide a fast, stable, full-featured, and cross-platform windowing and GUI support system, which is especially fit for embedded systems or smart IoT devices based-on Linux/uClinux, eCos, and other traditional RTOSes, such as RT-Thread, FreeRTOS, RTEMS, VxWorks, ThreadX, Nucleus, pSOS, uC/OS-II, OSE, and others.

This is the source tree of MiniGUI Core, which provides the windowing and graphics interfaces as well as a lot of standard controls (toolkit).

MiniGUI is released under GPLv3 and the dual-licensing applies to commercial use. In December 1998, the initiator of FMSoft, Vincent Wei, began to develop MiniGUI under the GNU General Public License (GPL). In September 2002, the core developers of MiniGUI founded FMSoft and started the commercial marketing with the free software. By now, FMSoft still continues to release MiniGUI as a free software project.

For the live demos, source tarballs, and cases of MiniGUI, you can refer to the following website:

http://www.minigui.com

HVML App Framework on MiniGUI

MiniGUI and its components provide a lot of controls/widgets to help your develop GUI apps in C/C++ programming language. However, alternatively, you can use the following software to develop your apps in an easy-to-use programming language HVML.

HVML is a descriptive programming language proposed and designed by Vincent Wei.
PurC is the prime interpreter of HVML written in C lauguage.
xGUI Pro is a full-featured HVML renderer based on the tailored WebKit engine.

In short, the above software suite provides an Electron-like solution that can help people develop cross-platform applications using web front-end technology. The difference is that the solution replaces JavaScript with HVML and Node.JS with PurC. It provides an entirely new application framework that isolates the interpreter and renderer from running in separate processes, which brings several benefits. It greatly reduces the size and resource consumption of the entire solution, improves the overall performance, promotes the interactive responsiveness, and provides a simpler mechanism to integrate existing C/C++ code modules.

MiniGUI and HybridOS

HybridOS is another large open source project initiated by FMSoft. It is an open source operating system designed for embedded/AIoT devices and cloud computing environment.

HybridOS provides the complete software stack and the app framework based on HVML for embedded systems. You can easily develop your products which has rich functions and excellent expressiveness by using HybridOS.

In practice, MiniGUI and the software which are used to integrated with GPU constitute the graphics stack of HybridOS.

HybridOS uses MiniGUI as the underlying windowing system, and the members of HybridOS project are now maintaining the whole graphics stack. The following chart shows the graphics stack of HybridOS:

  -----------------------------------------------
 |               MiniGUI/HVML Apps               |
 |-----------------------------------------------|
 |           |         (Graphics Stack)          |
 |           |              ---------------------|
 |           |              | hiMesa             |
 |           | hiCairo      |  ------------------|
 |           | MiniGUI      |  | EGL for MiniGUI |
 | C++ libs  | hiDRMDrivers |  | GL, GLES, VG    |
 | C libs    | libDRM       |  | GPU drivers     |
 |-----------------------------------------------|
 |  Linux Kernel                                 |
 |            -----------------------------------|
 |           |        DRI and DRI Drivers        |
  -----------------------------------------------

As shown in the chart above, the HybridOS graphics stack consists of the following software:

libDRM provides some user land APIs for Linux Direct Rendering Infrastructure.
hiDRMDrivers contains the drivers (user land drivers, not kernel drivers) for MiniGUI DRM engine. The drivers implement the basic hardware accelerated 2D graphics operations of various GPUs for MiniGUI.
hiMesa is the Mesa derivative for HybridOS, while Mesa is the open source implementation of OpenGL and other graphics APIs, including OpenGL ES (versions 1, 2, 3), OpenCL, OpenMAX, and Vulkan. It contains the following components:
- The implementation of OpenGL, OpenGL ES (v1, 2, 3), and other graphics APIs.
- The EGL implementation for MiniGUI platform.
- The graphics drivers for various GPUs and a software driver called swrast.
hiCairo is the Cairo derivative for HybridOS. Cairo is a 2D vector graphics library for Gtk. We provide support for MiniGUI backend in hiCairo.

For more information about HybridOS, please refer to:

https://hybridos.fmsoft.cn/

Source Code Repositories

FMSoft had created the public repositories for MiniGUI Core, MiniGUI components, HybridOS, and other open source apps on GitHub. You can visit them on:

https://github.com/VincentWei

We now maintain all documents about MiniGUI on the following public repo:

https://github.com/VincentWei/minigui-docs

You can download the source code tarballs of MiniGUI Core, MiniGUI components, and the dependent libraries from the download zone of the site:

http://www.minigui.com/download

NEW FEATURES IN VERSION 5.0.x

In version 5.0.0, we introduced some exciting new features, and refactored a lot basic modules of MiniGUI Core.

Compositing Schema

In this version, we enhanced the MiniGUI-Processes runtime mode to support the compositing schema. Under compositing schema, regardless a main window is created by the server (mginit) or a client, it renders the content in a separate rendering buffer, and the server composites the contents from all visible main windows to the ultimate scan-out frame buffer according to the z-order information.

On the contrary, the legacy schema of MiniGUI-Processes uses the same frame buffer for all processes (and all main windows) in the system. So the legacy schema is also called the shared frame buffer schema.

By enabling the compositing schema, MiniGUI now can provide a better implementation for multi-process environment:

Easy to implement advanced user interfaces with rounded corners, alpha blending, blurring, and so on.
Easy to implement animations for switching among main windows.
Better security. One client created by different user cannot read/write contents in/to another windows owned by other clients.

New Main Window Types

In this version, we also enhanced the window manager of MiniGUI Core to support some special main window types.

Before 5.0.0, you can create a topmost main window with the style WS_EX_TOPMOST in order to show the main window above all normal main windows, and if you use MiniGUI-Processes runtime mode, the server (mginit) will always create global main windows, which are shown on other main windows created by clients.

Since 5.0.0, we introduce a concept of z-order levels for main windows. There are eight levels in MiniGUI from top to bottom:

The tooltip level (WS_EX_WINTYPE_TOOLTIP).
The system/global level (WS_EX_WINTYPE_GLOBAL).
The screen lock level (WS_EX_WINTYPE_SCREENLOCK).
The docker level (WS_EX_WINTYPE_DOCKER).
The higher level (WS_EX_WINTYPE_HIGHER).
The normal level (WS_EX_WINTYPE_NORMAL).
The launcher level (WS_EX_WINTYPE_LAUNCHER).
The desktop or wallpaper.

This enhancement allows us to create a special app which acts as screen lock, docker, or launcher.

Virtual Window

You know that we can post or send a message to other windows which may run in another thread under MiniGUI-Threads. The MiniGUI messaging functions such as PostMessage(), SendMessage(), SendNotifyMessage(), and the window callback procedure provide a flexible, efficient, safe, and flexible data transfer and synchronization mechanism for your multithreaded applications.

For example, you can send or post a message to a window from a general purpose thread which may download a file from a remote server under MiniGUI-Threads.

But can we use the MiniGUI messaging mechanism under MiniGUI-Processes and MiniGUI-Standalone runtime modes for multithreading purpose? For example, we may download a file in a general thread and inform a window when the file is ready.

Furthermore, if we want to use the MiniGUI messaging mechanism in a general thread to handle messages from other threads, how to do this?

The virtual window provides a solution for the requirements above. A virtual window is a special window object which does not have a visible window area. But after you create a virtual window in a different thread, you can use the MiniGUI messaging mechanism to post or send messages between the current main window thread and the new thread.

This enhancement provides a very useful facility to you in order to develop a well-designed multithreaded application.

Other Enhancements

We also tune or enhance the following modules of MiniGUI Core:

Enhanced timer support. MiniGUI now manages the timers per message thread. Under MiniGUI-Threads runtime mode, you can set up 32 (64 on 64-bit architecture) timers for each GUI threads. If you enabled virtual window, you can also do this for each message thread.
Support for listening a file descriptor as long as the underlying system has the select() system call for all runtime modes. Now you can call RegisterListenFD() to register a file descriptor to be listened, and handle MSG_FDEVENT in your window callback procedure to read/write from/to the file descriptor. Before this version, this feature only available for MiniGUI-Processes runtime mode.
Support for local data of windows. You can now set or retrieve a local data which is bound with a string name for a window. This will give you an easy-to-use interface to manage various data of a window.
Support for hardware cursors under compositing schema. MiniGUI now can utilize the hardware cursors if your graphics device support it. You can also load a cursor from a PNG file.
Support for loading icon from a bitmap file. You can now load an icon from a bitmap file such as a PNG file.
Unified the message hook functions for all runtime modes. MiniGUI now provides the consistent message hook functions for all runtime modes.
Use the update regions for cumulative updating the screen. This will eliminate the flickers due to the frequently redrawing of controls.

Obviously, this version brings the largest improvement since MiniGUI 3.0.0. We did our best to ensure backward compatibility of the existed APIs so that the old applications can smoothly migrate to the new version. However, there are still some slight changes you need to take care. For more information, please refer to RELEASE-NOTES.md file:

https://github.com/VincentWei/minigui/blob/rel-5-0/RELEASE-NOTES.md

NEW FEATURES IN VERSION 4.0.x

In this version, we enhanced and tuned the APIs related to text rendering, in order to support [HybridOS Foundation Class Library].

Since 4.0.2, MiniGUI provides support for RTEMS, RT-Thread, and FreeRTOS.
MiniGUI now provides complete APIs for Unicode characters processing. These APIs conform to Unicode 12.0.
MiniGUI also provides new APIs to lay out, shape, and render glyphs from complex and mixed scripts, such as Arabic, Thai, and Indic.
We tuned and optimized MiniGUI's logical and device font interfaces to support the new features above.
MiniGUI now is enhanced to support input events which may be generated by input devices other than standard mouse (or single-touch panel) and keyboard, such as multi-touch panel (gesture), joystick, tablet tool, table pad, and switch. In MiniGUI 4.0, we introduce MSG_EXIN_XXX messages to support the input events from devices other than standard mouse and keyboard. We call these messages as 'extra input messages'.
The NEWGAL engine of dri to support modern DRI/DRM-driven graphics cards or GPUs on Linux.
The IAL engine of libinput to support all modern input devices including mouse, keyboard, joystick, switch, multiple touch panel, gesture, tablet tool, and table pad on Linux.
We introduced a Slice Memory Allocator for fast concurrent memory chunk allocation.
Cleanup and tune code for GCC 7.3.

For more information, please refer to RELEASE-NOTES.md file:

https://github.com/VincentWei/minigui/blob/rel-4-0/RELEASE-NOTES.md

Because of the changes of some APIs, we recommended strongly that you use this version for new projects.

NEW FEATURES IN VERSION 3.2.x

We introduce some new features in MiniGUI Version 3.2.x:

The support for 64-bit platform. Note that some APIs have changed to support 64-bit platform.
Some enhancements and optimizations.

For more information, please refer to RELEASE-NOTES.md file:

https://github.com/VincentWei/minigui/blob/rel-3-2/RELEASE-NOTES.md

THE RUNTIME MODES OF MINIGUI

You can configure and compile MiniGUI as one of three runtime modes:

MiniGUI-Threads: A program running on MiniGUI-Threads can create multiple cascaded windows in different threads, and all the windows belong to a single process. MiniGUI-Threads is fit for some real-time systems on Linux/uClinux, eCos, uC/OS-II, VxWorks, pSOS, ThreadX, and OSE.
MiniGUI-Processes: A program running on MiniGUI-Processes is an independent process, which can also create multiple windows. MiniGUI-Processes is fit for some complex embedded systems, such as PDAs, Thin-Clients or STBs. This mode is only useful for full-featured UNIX-like operating systems, like Linux.
MiniGUI-Standalone: A single process version of MiniGUI. This mode is useful for some small systems, like uClinux or RTOSes.

The original MiniGUI (version 1.0) run in MiniGUI-Threads mode. It is based on POSIX-compliant thread library. And this thread-based architecture of MiniGUI is very fit for most traditional embedded operating systems, such as eCos, uC/OS-II, and VxWorks. However, if you use embedded Linux, the architecture like X Window will have better stability and scalability, because of the independent memory address space of every process.

Since version 2.0, we provides a new runtime mode called MiniGUI-Processes. You can use MiniGUI-Processes to run more than one MiniGUI-based program in the form of UNIX process at the same time. MiniGUI-Processes is a full-featured multi-process version of original MiniGUI -- You can run a program based on MiniGUI-Processes from a program called mginit. Just like X Window, the former process is called a client, and the latter the server.

Clients connect to the server via UNIX domain socket, and the server receives and responses requests from clients. The server provides shared resources for clients, manage window objects, and sends mouse (or touch screen) and keyboard events to the active top-most client. If a client exits or dies for some reasons, it will not damage other clients and the server.

A BRIEF BUILDING INSTRUCTION

Building Whole MiniGUI

If you are anxious to see the comprehensive demo of MiniGUI Core and MiniGUI components, please fetch one of the following repositories from GitHub and follow the instructions to build MiniGUI Core, MiniGUI components, the samples, and the demonstration programs:

Build MiniGUI 5.0

Build MiniGUI 4.0

Build MiniGUI 3.2

Building MiniGUI Core

We recommend that you use a latest Linux distribution with long term support, for example, Ubuntu Linux LTS 16.04 or 18.04.

On Ubuntu Linux LTS 16.04 or 18.04, you should run apt install <package_name> to install the following packages:

Building tools:
- autoconf
Dependent libraries (all are optional):
- libjpeg64-dev
- libpng12-dev (use libpng-dev on Ubuntu Linux 18.04 LTS)
- libfreetype6-dev

MiniGUI Core uses GNU autoconf/automake scripts to configure and build the project.

Run

$ ./configure; make; sudo make install

to configure, make, and install the headers and the libraries. If there is not configure file, please run

$ ./autogen.sh

to generate the script.

MiniGUI Core also provides some configuration options to customize the features. For more information, please run

$ ./configure --help

Unit Tests

Since MiniGUI 4.0.0, we organize the unit test code of MiniGUI APIs in the following repository:

https://github.com/VincentWei/mg-tests

If you are interested in hacking the MiniGUI code, please visit this repository.

Othere Resources

MiniGUI Components

Besides MiniGUI Core, FMSoft also provides some components for the developers to develop app much easier:

mGUtils: A MiniGUI component which contains miscellaneous utilities like ColorSelectionDialogBox, FileOpenDialogBox, and so on.
mGPlus: A MiniGUI component which provides support for advanced graphics functions like path, gradient, anti-aliased stretch, and color combination.
mGEff: mGEff provides an animation framework for MiniGUI app. It also provides some popular UI/UE special effects.
mGNCS: This component provides a new control set for MiniGUI app.
mGNCS4Touch: This component provides some new controls, which are compliant to the new control API spec of mGNCS, for devices with touch screens.

There are also some legacy MiniGUI components. But we will not maintain these components since MiniGUI v3.2.0:

mGi: An input method component for MiniGUI. This component provides some typical input methods (such as soft keyboard, hand-writing, and predict text input for mobile phone) for MiniGUI apps.
mGp: A printing component for MiniGUI. By using mGp, you can print out the graphics created by MiniGUI app to general-purpose printers.
mG3d: A simple three-dimension component for MiniGUI. This component provides a simple 3D API for app. You can use mG3d to create simple 3D UI.

Open Source Apps Based-on MiniGUI

FMSoft also releases some open source apps for MiniGUI on the site above, for examples:

mDolphin, licensed under Apache 2.0, is a full-featured WEB/WAP browser, which is developed based on the open source browser core WebKit and uses MiniGUI as its underlying graphics support system.
mGallery, licensed under Apache 2.0, intends to provide a total solution for PMP (Portable Multimedia Player), which uses MiniGUI as the graphics platform.
mSpider, licensed under GPL 3.0, intends to provide a light-weight MiniGUI-based web browser (HTML 3.2 and part JavaScript)
mEagle, licensed under GPL 3.0, is an embedded GIS development platform which addresses the needs of map browse, query, analysis, etc

HISTORY

21 years have pasted since MiniGUI was initially created at the end of 1998, and now it becomes much reliable and stable. During the past years, many remarkable changes have taken place in the MiniGUI project.

At the original, the version 0.2.xx was based on SVGALib and PThread (LinuxThreads). Then the version 0.3.xx had many enhanced features including Graphics Abstract Layer (GAL), Input Abstract Layer (IAL), and the support for multiple charsets and multiple fonts.

In version 1.0.00, we designed MiniGUI-Lite, which was more fit for some complex embedded systems, such as PDAs, Thin-Clients, or STBs. MiniGUI-Lite made the embedded systems more stable and efficient. The version 1.0.00 provided the native fbcon engine based on Linux frame buffer device directly as well.

In the development of version 1.1.00, we re-wrote the GAL and GDI interfaces, and provided some advanced video features, such as raster operation, transparent blitting, alpha blending, and video hardware acceleration. We also provided some important GDI functions, such as Ellipse, Arc, Polygon, and FloodFill.

In the development of version 1.6.0, we added advanced 2D graphics functions to MiniGUI. It provides the abstract logical pen and brush objects, and can be used to render advanced graphics objects.

In the development of version 2.0.x, we developed MiniGUI-Processes.

In the development of version 3.0.x, we introduced Look & Feel Renderer, BIDI text support, Non-rectangular window, double-buffer window, and other main features.

In the development of version 4.0.x, we introduced the support for complex writing systems (scripts), such as Arabic, Thai, and Indic.

In the development of version 5.0.x, we introduced some new and exciting features such as compositing schema and virtual window.

A brief history description of the development progress is listed as follow:

1994 ~ 1996: MiniGUI DOS version.
Dec, 1998: Began to write.
Apr, 1999: The skeleton of MiniGUI, windowing sub-system and basic graphics device interfaces.
May, 1999: Timer, menu, and the skeleton of control sub-system.
Jun, 1999: Chinese input method (by Kang Xiaoning).
July, 1999: GIF and JPG loading support (by LI Zhuo).
Aug, 1999: Some standard controls (Portion by Zhao Jianghua).
Sep, 1999: Dialog boxes and message boxes.
Sep, 1999: Snapshot of screen or window.
Jan., 2000: VCOnGUI (Virtual Console on MiniGUI) version 0.2.02.
Mar., 2000: Linux distribution installer based-on MiniGUI for HappyLinux 1.0.
Jun., 2000: Began to develop version 1.0.xx.
Sep., 2000: MiniGUI version 0.3.06 released.
Oct., 2000: MiniGUI version 0.9.00 released.
Nov., 2000: MiniGUI version 0.9.96 released.
Jan., 2001: MiniGUI version 0.9.98 released. You can build MiniGUI-Lite from this version.
Jan., 2001: MiniGUI version 1.0.00Beta1 released.
Feb., 2001: MiniGUI version 1.0.00Pre1 released.
Apr., 2001: MiniGUI version 1.0.00 released (2001/04/16).
Sep., 2001: MiniGUI version 1.1.0Pre1 released (2001/09/12).
Sep., 2001: MiniGUI version 1.0.9 released (2001/09/17), this will be the last version of source branch 1.0.x.
Oct., 2001: MiniGUI version 1.1.0Pre4 released (2001/10/22). This version have new GAL and GDI interfaces.
Mar., 2002: MiniGUI official version 1.1.0 released (2002/03/08). MiniGUI API Reference documentation version 0.9 released.
Mar., 2002: MiniGUI API Reference documentation version 1.0 released.
Apr., 2002: MiniGUI the new stable version 1.2.0 released (2002/04/11).
Sep., 2002: The main developers of MiniGUI founded a new software corporation: Beijing FMSoft Technology Co., Ltd.. And the development and maintenance of MiniGUI changes from loosely-knit team to business organization.
Mar., 2003: MiniGUI official version 1.2.5 released (2003/03/23).
May., 2003: MiniGUI official version 1.2.6 released (2003/05/18).
Sep., 2003: MiniGUI official version 1.3.1 released (2003/09/11).
Jan., 2004: MiniGUI official version 1.5.1 released (2004/01/18).
Feb., 2004: MiniGUI tested on eCos and uC/OS-II.
Jun., 2004: MiniGUI tested on VxWorks.
Jan., 2005: MiniGUI tested on ThreadX and pSOS.
Feb., 2005: MiniGUI official version 1.6.1 released.
Aug., 2005: MiniGUI beta version 2.0.0 released.
Sep., 2005: MiniGUI official version 1.6.8 released.
Oct., 2005: MiniGUI official version 2.0.2 released.
Jun., 2006: MiniGUI provides support for OSE.
Jul., 2006: MiniGUI official version 2.0.3/1.6.9 released.
Nov., 2007: MiniGUI official version 2.0.4/1.6.10 released.
Apr., 2009: MiniGUI official version 3.0.2 released.
Oct., 2009: MiniGUI official version 3.0.4 released.
Jan., 2010: MiniGUI official version 3.0.6 released.
May., 2010: MiniGUI official version 3.0.8 released.
Aug., 2010: MiniGUI official version 3.0.10 released.
Oct., 2010: MiniGUI official version 3.0.12 released.
Aug., 2017: FMSoft released the latest source code of MiniGUI under GPL 3.0.
Aug., 2017: FMSoft released the latest source code of mDolphin under Apache 2.0.
Dec., 2017: FMSoft updated MiniGUI and miniStudio for latest Linux distributions.
Feb., 2018: FMSoft released MiniGUI version 3.2.0.
Apr., 2019: FMSoft released MiniGUI version 3.2.2.
Jul., 2019: FMSoft released MiniGUI version 4.0.0.
Mar., 2020: FMSoft released MiniGUI version 5.0.0.
May., 2021: FMSoft released MiniGUI version 5.0.6.
Jan., 2022: FMSoft released MiniGUI version 5.0.9.
Sep., 2022: FMSoft released MiniGUI version 5.0.10.

AUTHORS AND COPYING

The original author of MiniGUI is Vincent Wei, and now MiniGUI is maintained by FMSoft. For more information, please refer to http://www.fmsoft.cn.

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.

Or,

As this program is a library, any link to this program must follow GNU General Public License version 3 (GPLv3). If you cannot accept GPLv3, you need to be licensed from FMSoft.

If you have got a commercial license of this program, please use it under the terms and conditions of the commercial license.

For more information about the commercial license, please refer to http://www.minigui.com/blog/minigui-licensing-policy/.

Special Statement

The above open source or free software license does not apply to any entity in the Exception List published by Beijing FMSoft Technologies Co., Ltd.

If you are or the entity you represent is listed in the Exception List, the above open source or free software license does not apply to you or the entity you represent. Regardless of the purpose, you should not use the software in any way whatsoever, including but not limited to downloading, viewing, copying, distributing, compiling, and running. If you have already downloaded it, you MUST destroy all of its copies.

The Exception List is published by FMSoft and may be updated from time to time. For more information, please see https://www.fmsoft.cn/exception-list.

Not Free for Commercial Use

As stated above, MiniGUI and its components are licensed under GPL. So any links about MiniGUI must follow GPL. If you cannot accept GPL, you need to be licensed from FMSoft.

We provide you the commercial license of MiniGUI according to the number of the run-time binary copies of MiniGUI. If you are interested in the commercial license of MiniGUI, please write to [email protected].

A LITTLE FAQ

Q: Which operating systems does MiniGUI support?
A: MiniGUI can run on Linux/uClinux, uC/OS-II, eCos, ThreadX, pSOS, VxWorks, ThreadX, OSE, and even Win32. Any other real-time OSes can be supported theoretically.

Q: Which architecture does MiniGUI support?
A: x86 32/64-bit, ARM 32/64-bit (e.g., ARMv7 and ARM Cortex-A7), PowerPC, MIPS, DragonBall, ColdFire, Blackfin, and so on.

Q: Does MiniGUI offer the support for grey LCD with 4bpp (bits per pixel)?
A: Yes, it offers. It even offers the support for 1bpp and 2bpp LCD.

Q: Can I get the tech support from MiniGUI team?
A: Yes, FMSoft can provide you with guaranteed commercial technical support services. Please send messages to [email protected].

VincentWei/MiniGUI

VincentWei

Reviews

Repository Details