QMSH

Overview

Welcome to the tool repository for the quick-mesh kernel and scripting language.

Here you'll find pre-compiled binaries for the various applications in the quick-mesh eco-system along with detailed information describing the functionality implemented and the hardware and platform requirements for each.

This tool repository acts as a complement to the project's homepage by providing a means for mesh-makers to access the full catalogue of publicly available tools.

In other words the project's homepage displays a key subset of the eco-system (i.e. the flagship applications) whilst this repo lists the full extended tool-set (including some of the experimental and esoteric and less often used utilities).

The anticipation is that the vast majority of new (first-time) and returning (updating) mesh-makers should find their needs met by the simplified core tool downloads on the homepage. However more experienced mesh-makers and technically adept first-timers (with specialist requirements and/or the desire for further detail on the nature of these tools) may benefit from the greater depth of information provided here.

Notes

Versioning

The tools in this repository follow the project's two-tier (mainline, auxiliary-line) version numbering system. The mainline (currently at V:0.2.5) maps to the primary development branch and spans all tools that move in sync with the kernel.

For clarity mainline tools (such as QMSH:CLK, QMSH:EI, QMSH:IDE, QMSH:MK and QMSH:XMPL) are updated simultaneously such that revisions to the kernel (and tools that embed or rely upon the kernel) appear uniformly across all the primary usage contexts. The mainline increments the version number for each release such that higher version numbers correspond to more recent updates.

Note: the experimental web-sandbox and entity-exchange are also (currently) considered mainline tools - and hence are also updated in sync with the kernel.

The auxiliary-line maps to the supplementary development branches that exhibit irregular or out-of-sync release cycles. Most notably this includes the tools designed to be stable over kernel updates and revisions. In other words auxiliary-line tools (including the visual-editor, launcher and plugin) move at their own pace which may or may not coincide with mainline revisions. Typically auxiliary-line tools are updated less frequently than mainline tools, however they still also increment their tool-specific (rather than project-wide) version number with each release.

Note: the two-tier system emerged out of practicality more so than anything else. In particular it makes logical sense to minimise the release latency amongst each platform for the kernel - so to maintain functional parity particularly in terms of the accessibility of grammatical constructs. However for ancillary tools such as the launcher - which, as an example (strictly speaking) only needs to change in response to the addition of newer tools - it would be somewhat wasteful to push an update or release just to maintain version number equivalence. As such the project supports both approaches - the mainline method in which updates across Linux, MacOSX, Windows, RPi-OS, Android and the web appear synchronously - and the auxiliary-line method in which tool-specific out-of-sync updates are permitted.




Omissions

Presently the script collection (QMSH:XMPL) and the engine plugin have yet to be added to this repository. In the case of the script collection this is largely due to the requirement to add a suitable (i.e. a safe and reliable) payment processing method - along with coordinating the legal and financial aspects of distributing a paid collection. Beyond administrative concerns - there are also logistical pre-requisites to the relaunch that are currently being resolved - including the addition of features such as automatic updates, alongside implementing the infrastructure enabling mesh-makers to submit feedback, report issues and request features easily.