meltygui 0.1.0__tar.gz

meltygui-0.1.0/.gitignore

@@ -0,0 +1,10 @@
+.venv/
+__pycache__/
+*.pyc
+.pytest_cache/
+dist/
+build/
+*.egg-info/
+.melty/
+
+.idea/

meltygui-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

meltygui-0.1.0/PKG-INFO

@@ -0,0 +1,143 @@
+Metadata-Version: 2.5
+Name: meltygui
+Version: 0.1.0
+Summary: Immediate-mode Python UI, live inspection, HDR and tensor visualization
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: <3.14,>=3.11
+Requires-Dist: anthropic>=0.40
+Requires-Dist: freetype-py>=2.4
+Requires-Dist: glfw>=2.10
+Requires-Dist: httpx>=0.27
+Requires-Dist: jedi>=0.19
+Requires-Dist: libcst>=1.4
+Requires-Dist: mcp>=1.0
+Requires-Dist: meltygui-imgui[glfw]<2.0.1,>=2.0.0.post1
+Requires-Dist: numpy>=1.26
+Requires-Dist: packaging>=24
+Requires-Dist: pillow>=10
+Requires-Dist: psutil>=6
+Requires-Dist: pygments>=2.18
+Requires-Dist: pyopengl-accelerate>=3.1.7
+Requires-Dist: pyopengl>=3.1.7
+Requires-Dist: pyte>=0.8
+Requires-Dist: rich>=13
+Requires-Dist: rtree>=1.2
+Requires-Dist: symspellpy>=6.7
+Requires-Dist: tomlkit>=0.13
+Requires-Dist: uvicorn>=0.30
+Requires-Dist: watchdog>=4
+Provides-Extra: input
+Requires-Dist: evdev>=1.7; (sys_platform == 'linux') and extra == 'input'
+Requires-Dist: pynput>=1.7; extra == 'input'
+Provides-Extra: profile
+Requires-Dist: line-profiler>=4; extra == 'profile'
+Provides-Extra: tensor
+Requires-Dist: meltygui-pycuda<2026.2,>=2026.1.post1; (sys_platform == 'linux') and extra == 'tensor'
+Requires-Dist: torch>=2.2; extra == 'tensor'
+Description-Content-Type: text/markdown
+
+# MeltyGUI
+
+Low latency tensor visualization for PyTorch.
+
+MeltyGUI is an open source data visualization toolkit for PyTorch, designed to render massive tensors in-place on the GPU at an interactive framerate. The purpose of this project is to make PyTorch code easier to understand and faster to debug. Along with its core tensor rendering components, MeltyGUI is bundled with a Blender inspired UI framework designed to make interacting with high dimensional tensors feel fast and intuitive. 
+
+MeltyGUI is capable of rendering tensors exceeding 64GB in size. The primary challenge with visualizing data this large is moving it around. MeltyGUI skips the data movement entirely, and ray-marches tensors directly from CUDA memory.
+
+<img width="2410" height="2018" alt="Image" src="https://github.com/user-attachments/assets/82ffae2c-ec0a-456c-b781-5428c54009f8" />
+
+## Getting started
+
+MeltyGUI is not yet published to PyPI. For now, install from a checkout using
+[the setup guide](docs/DEVELOPMENT.md#setup).
+
+The current setup targets Linux x86-64 with Python 3.11, 3.12 or 3.13 and a
+working OpenGL 4.3 context. CUDA tensor rendering also requires PyTorch, an
+NVIDIA GPU, a CUDA toolkit, and MeltyGUI's GL-enabled CUDA binding. The native
+bindings install as prebuilt wheels on those targets; elsewhere installers
+compile them, see [when no wheel matches](docs/SUPPORT_WHEELS.md#when-no-wheel-matches).
+
+## Visualize a tensor
+
+Create a small volume on the GPU and tag `draw_voxels` as an OS window with
+`glfw_window`:
+
+```python
+import torch
+import meltygui
+
+axis = torch.linspace(-1.5, 1.5, 40, device="cuda:0")
+x, y, z = torch.meshgrid(axis, axis, axis, indexing="ij")
+volume = torch.exp(-4 * ((torch.sqrt(x * x + y * y) - 0.85) ** 2 + z * z))
+
+meltygui.glfw_window(
+    meltygui.draw_voxels, name="Torus", value=volume, width=850, height=700
+)
+```
+
+Save this as `tensor_demo.py` and run it with the Python from your configured
+environment:
+
+```sh
+.venv/bin/python tensor_demo.py
+```
+
+`glfw_window` turns a view into a native window: `name` is the window title,
+`width` / `height` its content size, `value` the view's input, and every other
+keyword argument goes to the view. The window loop starts automatically after
+the module finishes defining its windows. The CUDA renderer reads the volume on
+its own GPU and transfers the rendered 2D image for display.
+
+To compose several views in one window, decorate your own function instead. It
+runs each frame, so create the tensor outside it to avoid reallocating the
+volume on every frame:
+
+```python
+@meltygui.glfw_window(name="CUDA tensor", width=850, height=700)
+def draw_frame():
+    # Interactive widget, rendered in a loop. This function will be called wheneven
+    # the rendered image is invalidated
+    meltygui.draw_voxels(volume, name="Torus", width=800, height=630)
+```
+
+`draw_voxels` chooses CUDA for CUDA tensors and OpenGL for CPU tensors, NumPy
+arrays and GL textures. Select a renderer explicitly with the framework's
+`view_func` override (or call either renderer directly):
+
+```python
+meltygui.draw_voxels(volume, view_func=meltygui.draw_voxels_opengl)
+meltygui.draw_voxels(volume, view_func=meltygui.draw_voxels_cuda)
+```
+
+`draw_voxels_opengl` accepts tensors directly, including CUDA tensors; it slices
+and uploads the displayed volume to a GL texture. `draw_voxels_cuda` requires a
+CUDA tensor and reads it in place. Both expose the same camera, mapping and
+shading controls. Backend selection no longer uses the obsolete `cuda_march`
+parameter.
+
+See [the tensor and live-code example](examples/tensor_live.py) for a tensor
+viewer alongside an editable function view.
+
+## Build an app
+
+Use the bundled UI framework to add controls, editors, and additional windows.
+[Building an app](docs/APPS.md) covers persistent view state, render functions,
+and window lifecycle.
+
+For framework design, feature ownership and render-function patterns, see
+[Contributing](CONTRIBUTING.md). [Development](docs/DEVELOPMENT.md) covers setup,
+checks and packaging; [Architecture gaps](docs/ARCHITECTURE_DEBT.md) tracks the
+remaining migration work.
+
+## License
+
+MeltyGUI is licensed under [Apache 2.0](LICENSE). Bundled third-party code and
+assets retain their own licenses. The separate commercial IDE is not part of
+this distribution.

meltygui-0.1.0/README.md

@@ -0,0 +1,98 @@
+# MeltyGUI
+
+Low latency tensor visualization for PyTorch.
+
+MeltyGUI is an open source data visualization toolkit for PyTorch, designed to render massive tensors in-place on the GPU at an interactive framerate. The purpose of this project is to make PyTorch code easier to understand and faster to debug. Along with its core tensor rendering components, MeltyGUI is bundled with a Blender inspired UI framework designed to make interacting with high dimensional tensors feel fast and intuitive. 
+
+MeltyGUI is capable of rendering tensors exceeding 64GB in size. The primary challenge with visualizing data this large is moving it around. MeltyGUI skips the data movement entirely, and ray-marches tensors directly from CUDA memory.
+
+<img width="2410" height="2018" alt="Image" src="https://github.com/user-attachments/assets/82ffae2c-ec0a-456c-b781-5428c54009f8" />
+
+## Getting started
+
+MeltyGUI is not yet published to PyPI. For now, install from a checkout using
+[the setup guide](docs/DEVELOPMENT.md#setup).
+
+The current setup targets Linux x86-64 with Python 3.11, 3.12 or 3.13 and a
+working OpenGL 4.3 context. CUDA tensor rendering also requires PyTorch, an
+NVIDIA GPU, a CUDA toolkit, and MeltyGUI's GL-enabled CUDA binding. The native
+bindings install as prebuilt wheels on those targets; elsewhere installers
+compile them, see [when no wheel matches](docs/SUPPORT_WHEELS.md#when-no-wheel-matches).
+
+## Visualize a tensor
+
+Create a small volume on the GPU and tag `draw_voxels` as an OS window with
+`glfw_window`:
+
+```python
+import torch
+import meltygui
+
+axis = torch.linspace(-1.5, 1.5, 40, device="cuda:0")
+x, y, z = torch.meshgrid(axis, axis, axis, indexing="ij")
+volume = torch.exp(-4 * ((torch.sqrt(x * x + y * y) - 0.85) ** 2 + z * z))
+
+meltygui.glfw_window(
+    meltygui.draw_voxels, name="Torus", value=volume, width=850, height=700
+)
+```
+
+Save this as `tensor_demo.py` and run it with the Python from your configured
+environment:
+
+```sh
+.venv/bin/python tensor_demo.py
+```
+
+`glfw_window` turns a view into a native window: `name` is the window title,
+`width` / `height` its content size, `value` the view's input, and every other
+keyword argument goes to the view. The window loop starts automatically after
+the module finishes defining its windows. The CUDA renderer reads the volume on
+its own GPU and transfers the rendered 2D image for display.
+
+To compose several views in one window, decorate your own function instead. It
+runs each frame, so create the tensor outside it to avoid reallocating the
+volume on every frame:
+
+```python
+@meltygui.glfw_window(name="CUDA tensor", width=850, height=700)
+def draw_frame():
+    # Interactive widget, rendered in a loop. This function will be called wheneven
+    # the rendered image is invalidated
+    meltygui.draw_voxels(volume, name="Torus", width=800, height=630)
+```
+
+`draw_voxels` chooses CUDA for CUDA tensors and OpenGL for CPU tensors, NumPy
+arrays and GL textures. Select a renderer explicitly with the framework's
+`view_func` override (or call either renderer directly):
+
+```python
+meltygui.draw_voxels(volume, view_func=meltygui.draw_voxels_opengl)
+meltygui.draw_voxels(volume, view_func=meltygui.draw_voxels_cuda)
+```
+
+`draw_voxels_opengl` accepts tensors directly, including CUDA tensors; it slices
+and uploads the displayed volume to a GL texture. `draw_voxels_cuda` requires a
+CUDA tensor and reads it in place. Both expose the same camera, mapping and
+shading controls. Backend selection no longer uses the obsolete `cuda_march`
+parameter.
+
+See [the tensor and live-code example](examples/tensor_live.py) for a tensor
+viewer alongside an editable function view.
+
+## Build an app
+
+Use the bundled UI framework to add controls, editors, and additional windows.
+[Building an app](docs/APPS.md) covers persistent view state, render functions,
+and window lifecycle.
+
+For framework design, feature ownership and render-function patterns, see
+[Contributing](CONTRIBUTING.md). [Development](docs/DEVELOPMENT.md) covers setup,
+checks and packaging; [Architecture gaps](docs/ARCHITECTURE_DEBT.md) tracks the
+remaining migration work.
+
+## License
+
+MeltyGUI is licensed under [Apache 2.0](LICENSE). Bundled third-party code and
+assets retain their own licenses. The separate commercial IDE is not part of
+this distribution.

meltygui-0.1.0/docs/APPS.md

@@ -0,0 +1,103 @@
+# Building an app
+
+Install the framework into the same environment that runs the app. Both the
+package name and import name are `meltygui`. There is no `src` package and no
+requirement to launch from the framework checkout.
+
+When contributing reusable features to the library, also follow the
+[ownership and render-function contracts](../CONTRIBUTING.md).
+
+```python
+import meltygui
+from meltygui.core.core_render import render_func
+from meltygui.core.conversion.dict_conversion import DictConversion
+
+class EditorState(DictConversion):
+    def __init__(self):
+        super().__init__()
+        self.text = "Hello"
+
+@meltygui.glfw_window(name="Editor", app_id="my-editor", width=900, height=700)
+@render_func(use_cache=False)
+def editor(input_value=None, state: EditorState = None):
+    changed, state.text = meltygui.draw_text(state.text)
+    return changed, input_value
+```
+
+The loop starts after the main module finishes defining its windows.
+Injected state persists across frames and sessions. Call render functions every
+frame, returning `(changed, value)`. For nested windows, pass `closable=True` and
+an `open_requested` event to the same call every frame. Use `glfw_window=True` to
+host a child in a native window; its lifecycle follows the same rules.
+
+## Common imports
+
+```python
+from meltygui import draw_text, draw_voxels, glfw_window, imgui
+from meltygui.core.core_render import render_func
+from meltygui.core.rendering.core_decoration import defaults, no_save
+from meltygui.core.conversion.dict_conversion import DictConversion
+from meltygui.core.conversion.render_host import RenderHost
+from meltygui.view.code_view import draw_function_live
+from meltygui.graphics import Filter
+from meltygui.chat import draw_chat_interface, register_chat_backend
+```
+
+`meltygui.persisted(name, factory, app_id=...)` retains app-owned objects in
+addition to automatically retained view state. Keep an existing app's `app_id`
+when migrating so its session file remains the same.
+
+## Tiled editors
+
+Mark an editor with `@render_func(multi_instance=True)` to offer it in every
+tile's editor dropdown. Registration happens when its module is imported; the
+flag does not open a window. A `Tile` in the app model owns the selected function
+reference and its `input_value`. `Tile` and `Split` are `DictConversion` models,
+so the normal app/session persistence saves the layout and function references.
+
+```python
+from meltygui.model.tile_model import Split, Tile
+
+@render_func(multi_instance=True, tint=(0.2, 0.4, 0.6))
+def draw_scene(input_value: Scene, state: ViewportState = None):
+    ...
+    return changed, input_value
+
+# Store this on your app model. A layout always has a Split root.
+app_model.tiles = Split("x", [
+    Tile(render_func=draw_scene, input_value=scene),
+    Tile(render_func=draw_scene, input_value=scene),
+])
+```
+
+The host declares `multi_instance_renderers=()` to receive the eligible
+function references from core, and passes that parameter to `draw_tiles` along
+with its injected `TileManagerState`. The selected editor receives the tile's
+input unchanged: the app supplies a compatible value, or the editor accepts
+`None` and uses injected model/state. Choosing another editor does not construct
+or convert model data.
+
+Each tile has independent injected view state. Switching editors and switching
+back restores that tile's editor state. Splitting inherits the renderer and
+shares the input value, while creating a new view instance. See
+`examples/tile_manager.py` for a runnable demo with counters and notes.
+
+Hosted renderers can declare `instance` and `layout_frame` parameters. These
+receive the tile's existing conversion identity and its four shared frame edges,
+so instance-targeted commands and nested column layouts stay within that tile.
+An editor created by a corner split first renders when the drag ends, after its
+initial size is known.
+
+Files in an installed library are read-only to the live editor. App source roots
+are registered from the app's entry point and decorated functions. An editable
+framework checkout can also be edited; an ordinary wheel in site-packages cannot.
+
+## Native binding imports
+
+MeltyGUI uses a namespaced ImGui binding. Low-level app code should use
+`from meltygui import imgui` (or `import meltygui_imgui as imgui`). Mixing contexts from
+upstream `imgui` with MeltyGUI's binding is unsupported. The upstream packages
+can coexist because the support wheels install different Python namespaces.
+
+The optional tensor backend similarly uses `meltygui_pycuda`. A child project's
+own `pycuda` dependency remains independent of MeltyGUI's internal backend.