The default runtime directory for Moqui Framework
Moqui Runtime 3.0.0 is a major new feature and bug fix release with some changes that are not backward compatible, in parallel with the release of Moqui Framework.
In this release there is a new render mode (qvt) and apps screen wrapper (/qapps) that is like vuet and /vapps but uses the Quasar project, a Vue JS component library based on Google Material Design. The new Vue JS component library in Moqui (in WebrootVue.qvt.js) takes a big step toward more client rendering and better use of Vue JS components and events, making it far easier to extend with dynamic behavior (vs the vuet and html render modes).
There are various small improvements to the System and Tools apps, and some new screens like an interactive Groovy Shell screen and a Table Stats screen that shows the number of records in each entity's table.
This is a brief summary of the changes since the last release, for a complete list see the commit log:
https://github.com/moqui/moqui-runtime/compare/v2.1.3...v3.0.0
Moqui Runtime 2.1.2 is a patch level new feature and bug fix release, in parallel with the release of Moqui Framework.
There are only minor changes and fixes in this release. For a complete list of changes see:
https://github.com/moqui/moqui-runtime/compare/v2.1.2...v2.1.3
Moqui Runtime 2.1.2 is a patch level new feature and bug fix release, in parallel with the release of Moqui Framework.
This release includes JavaScript library updates including Bootstrap 3.4.1, jQuery 3.4.1, jsTree 3.3.8, Moment.js 2.24.0, and Vue JS 2.6.10. This was done mainly for security reasons and updates to JS code in this repository have been done to fix issues from the updates.
There are various improvements to System and Tools app screens for usability and to better handle larger databases.
There are only minor changes and fixes in this release. For a complete list of changes see:
https://github.com/moqui/moqui-runtime/compare/v2.1.1...v2.1.2
Moqui Runtime 2.1.1 is a patch level new feature and bug fix release, in parallel with the release of Moqui Framework.
In this release there are significant refinements and fixes for the Vue JS based vuet/vapps mode and it is now the default (ie default under webroot is /vapps instead of /apps). The standard HTML mode is still available under /apps and there are still links to switch on the app list screen. There is also now support for Vue component based XML Screens using a .js file and optional .vuet file that gets merged into the Vue component as the template. For an example see the DynamicExampleItems.xml screen in the example component.
Moqui has an improved look and feel with simplified and less cluttered CSS styling. These changes are implemented as overrides in a section at the bottom of webroot-theme.css so they can be easily changed or overridden.
QZ Tray is now supported (only in vuet mode, QZ connection maintained across screens) with a print options dialog in the header. Screens can use QZ Tray in custom JavaScript to print, communicate with devices, etc.
Various screens in the System and Tools apps have been improved and modernized using newer XML Form functionality. There are also some improvements to work better in vuet/vapps mode (now the default).
HTML and JavaScript generated for html and vuet render modes has a few output encoding fixes which fixes the rendering of screens in various conditions (especially under vuet) for HTML and JS reserved characters, and for XSS mitigation.
See the complete release notes at:
https://github.com/moqui/moqui-runtime/blob/master/ReleaseNotes.md
Moqui Runtime 2.1.0 is a minor new feature and bug fix release, in parallel with the release of Moqui Framework.
This release introduces the new 'vuet' render mode for applications that uses a Vue JS based single-page application shell and supports hybrid client/server HTML rendering. The Vue shell (router, etc) is accessible on /vapps while the server rendered HTML is still on /apps. The benefit is a significantly better user experience with existing XML Screens and a foundation for fully client-rendered screens for dynamic in-browser interactivity. Even with hybrid client/server rendering using XML Screens page loads are faster and there is less load on the server, along with better error handling and improved widgets (user interface elements).
See the complete release notes at:
https://github.com/moqui/moqui-runtime/blob/master/ReleaseNotes.md
Moqui Runtime 2.0.0 is a major new feature and bug fix release, in parallel with the release of Moqui Framework.
In this version the CSS and JS libraries used are significantly simplified and refined, along with JS and CSS for cleanups and workarounds in widgets and styling (including layout, etc).
XML list forms (form-list) have been improved in various ways to make it a functional reporting tools with various options to parameterize reports and support light user customization of reports including column layout configuration, saved finds, etc.
There are various new System and Tools app screens for system status details, multi-instance management, service job admin and history, seeing active users summary, database snapshots, and query statistics.
This is a release candidate for public review. See the release notes at:
https://github.com/moqui/moqui-runtime/blob/master/ReleaseNotes.md
Moqui Runtime 1.6.2 is a minor new feature and bug fix release, in parallel with the release of Moqui Framework.
New Features
Moqui Runtime 1.6.1 is the first release of the runtime repository separate from the rest of Moqui Framework.
Version numbers of this repository will match those of moqui-framework, the two are developed in parallel. They are separate to make it easier to use your runtime directory separate from the rest of the framework (for configuration, custom UI, etc). The easiest way to do this is generally to fork from this repository (moqui/moqui-runtime).