change version to 4.9.0

Doxyfile.procs

@@ -38,7 +38,7 @@ PROJECT_NAME           = "MiniGUI API Reference (MiniGUI-Processes)"
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = v4.0.4
+PROJECT_NUMBER         = v4.9.0
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a
@@ -58,7 +58,7 @@ PROJECT_LOGO           =
 # entered, it will be relative to the location where doxygen was started. If
 # left blank the current directory will be used.
 
-OUTPUT_DIRECTORY       = doc-api-ref-minigui-procs-4.0.4
+OUTPUT_DIRECTORY       = doc-api-ref-minigui-procs-4.9.0
 
 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
 # directories (in 2 levels) under the output directory of each output format and

Doxyfile.sal

@@ -38,7 +38,7 @@ PROJECT_NAME           = "MiniGUI API Reference (MiniGUI-Standalone)"
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = v4.0.4
+PROJECT_NUMBER         = v4.9.0
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a
@@ -58,7 +58,7 @@ PROJECT_LOGO           =
 # entered, it will be relative to the location where doxygen was started. If
 # left blank the current directory will be used.
 
-OUTPUT_DIRECTORY       = doc-api-ref-minigui-sa-4.0.4
+OUTPUT_DIRECTORY       = doc-api-ref-minigui-sa-4.9.0
 
 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
 # directories (in 2 levels) under the output directory of each output format and

Doxyfile.ths

@@ -38,7 +38,7 @@ PROJECT_NAME           = "MiniGUI API Reference (MiniGUI-Threads)"
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = v4.0.4
+PROJECT_NUMBER         = v4.9.0
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a
@@ -58,7 +58,7 @@ PROJECT_LOGO           =
 # entered, it will be relative to the location where doxygen was started. If
 # left blank the current directory will be used.
 
-OUTPUT_DIRECTORY       = doc-api-ref-minigui-ths-4.0.4
+OUTPUT_DIRECTORY       = doc-api-ref-minigui-ths-4.9.0
 
 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
 # directories (in 2 levels) under the output directory of each output format and

RELEASE-NOTES.md

@@ -1,16 +1,69 @@
 # Release Notes
 
-## Version 4.1.0
+## Version 4.9.0
 
-The MiniGUI development team announces the availability of MiniGUI 4.1.0.
+The MiniGUI development team announces the availability of MiniGUI 4.9.0.
 This is a unstable release to test some new and exciting features.
 We recommend that you test this version and report any bugs and
 incompatibilities in
 
-<https://github.com/VincentWei/minigui>
+<https://github.com/VincentWei/minigui/tree/dev-4-1>
 
 ### What's new in this version
 
+In the development of version 4.9.x, we introduced the following new and
+exciting features for MiniGUI:
+
+* ENHANCEMENTS:
+   - Support for compositing schema under MiniGUi-Processes runtime mode.
+     This feature brings the exciting visual effects which are popular
+     on modern desktop computers or smart phones to MiniGUI.
+   - 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.
+   - New main window types. You now can easily create some special main window
+     which acts as screen lock, docker, or lanucher. You can also use the common
+     global tooltip main window to show a tooltip.
+   - Virtual Window. You now can easily create message threads under all runtime
+     modes to exploit the messaging mechanism of MiniGUI in non GUI threads.
+   - Support for loading icon from a bitmap file. You can now load an icon
+     from a bitmap file.
+   - 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.
+   - Unified the message hook functions for all runtime modes. MiniGUI now
+     provides the unified message hook functions for all runtime modes.
+* ADJUSTMENTS:
+   - `g_rcScr` now is defined a macro calling function `GetScreenRect()`.
+   - `mgIsServer` now is define a macro calling function `IsServer()`.
+* CLEANUP:
+   - Cleaned up a lot of internal symbols (the external functions and
+     global variables) in order to avoid name polution.
+
+
+The following new features will be developed in version 4.9.x:
+
+
+* ENHANCEMENTS:
+   - New APIs for GPU integration, such as `IsMemDC`, `IsScreenDC`, `IsWindowDC`, `GetVideoHandle`, and `drmGetDeviceFD`.
+   - Add new operation for DRM engine: `create_buffer_from_prime_fd`.
+   - Use `dlopen` to load the external DRM driver.
+   - Add a new runtime configuration key for DRM engine `drm.exdriver` to define the external DRM driver.
+* MODIFICATIONS:
+   - Change the name of old `dri` NEWGAL engine to `drm`.
+   - Change the configuration option of DRM engine to `--enable-videodrm`.
+   - Change the macro for DRM engine to `_MGGAL_DRM`.
+   - Change the runtime configuration section for DRM engine to `drm`.
+
+### 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
@@ -57,7 +110,7 @@ Usage:
 In order to use the compositing schema on Linux-based system, we introduce
 some new APIs for your new apps.
 
-### New runtime configuration
+#### Runtime configuration for compositing schema
 
 ```
 [compositing_schema]
@@ -73,7 +126,7 @@ wallpaper_pattern_size=full
 compositor=my_compositor.so
 ```
 
-### Compositing types
+#### Compositing types
 
 You can call the following function to set the compositing type and argument
 of a main window:
@@ -125,6 +178,8 @@ the cursor. And you can use the following APIs to load a PNG file as the cursor:
 - `LoadCursorFromPNGFile`
 - `LoadCursorFromPNGMem`
 
+### Virtual Window
+
 ### Other new APIs
 
 - `ServerMoveClientToLayer`

Version.md

@@ -1,6 +1,6 @@
-Version 4.2.0 (2019/02/22)
+Version 4.9.0 (2019/02/28)
 
-This is a developing version, an unstable version.
+This is a developing version (target version: 5.0.0), an unstable version.
 
 It needs the following packages:
 

configure.ac

@@ -1,6 +1,6 @@
 dnl Process this file with autoconf to produce a configure script.
 AC_PREREQ(2.60)
-AC_INIT(libminigui, 4.1.0)
+AC_INIT(libminigui, 4.9.0)
 AC_CONFIG_SRCDIR(src/main/main.c)
 
 dnl Set various version strings - taken gratefully from the SDL sources
@@ -15,7 +15,7 @@ dnl Set various version strings - taken gratefully from the SDL sources
 # set MINIGUI_BINARY_AGE and MINIGUI_INTERFACE_AGE to 0.
 #
 MINIGUI_MAJOR_VERSION=4
-MINIGUI_MINOR_VERSION=1
+MINIGUI_MINOR_VERSION=9
 MINIGUI_MICRO_VERSION=0
 MINIGUI_INTERFACE_AGE=0
 MINIGUI_BINARY_AGE=0