meltygui 0.1.3__tar.gz → 0.1.8__tar.gz

meltygui-0.1.8/.gitignore

@@ -0,0 +1,12 @@
+.venv/
+__pycache__/
+*.pyc
+.pytest_cache/
+dist/
+build/
+*.egg-info/
+.melty/
+.DS_Store
+.idea/
+meltygui/core/rendering/_gui_native*.so
+meltygui/core/rendering/_gui_native*.pyd

meltygui-0.1.8/PKG-INFO

@@ -0,0 +1,177 @@
+Metadata-Version: 2.5
+Name: meltygui
+Version: 0.1.8
+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 :: MacOS :: MacOS X
+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; sys_platform != 'ios'
+Requires-Dist: httpx>=0.27
+Requires-Dist: jedi>=0.19
+Requires-Dist: libcst>=1.4
+Requires-Dist: mcp>=2.0
+Requires-Dist: meltygui-imgui<2.0.4,>=2.0.3
+Requires-Dist: numpy>=1.26
+Requires-Dist: packaging>=24
+Requires-Dist: paramiko>=3.5
+Requires-Dist: pillow>=10
+Requires-Dist: psutil>=6; sys_platform != 'ios'
+Requires-Dist: pygments>=2.18
+Requires-Dist: pyopengl-accelerate>=3.1.7; sys_platform != 'ios'
+Requires-Dist: pyopengl>=3.1.7; sys_platform != 'ios'
+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: claude
+Requires-Dist: claude-agent-sdk>=0.2.152; extra == 'claude'
+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.3,>=2026.2; (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).
+
+Linux x86-64 uses Python 3.11, 3.12 or 3.13 and OpenGL 4.3. The UI and editor
+also run on Apple Silicon macOS with Python 3.12, OpenGL 4.1 and Retina
+rendering. CUDA tensor rendering 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).
+CUDA rendering is unavailable on macOS.
+
+## Public render functions
+
+Every module-level function decorated with `@render_func` in the library is
+automatically available as `meltygui.<function_name>`, including
+`meltygui.draw_bool(True)`. No export list needs updating when adding a renderer.
+Discovery reads source on the first render-function lookup or `dir(meltygui)`;
+individual view modules still load only when accessed. Newly added functions
+are discovered on the next interpreter run. `dir(meltygui)` and `__all__` include
+the discovered names; static IDE completion may not enumerate these dynamic exports.
+
+Render function names must be unique across library modules. Duplicate names
+raise an error identifying both modules. Nested functions, class methods and
+bundled examples are not package-level library exports.
+
+## Use ImGui directly
+
+The bundled ImGui bindings are public as `meltygui.imgui` (also available with
+`from meltygui import imgui`). They load on first access and share the same
+ImGui context as MeltyGUI. Call drawing functions inside a window callback:
+
+```python
+import meltygui
+
+@meltygui.glfw_window
+def some_window():
+    meltygui.imgui.text("Hello")
+```
+
+## 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.8/README.md

@@ -0,0 +1,128 @@
+# 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).
+
+Linux x86-64 uses Python 3.11, 3.12 or 3.13 and OpenGL 4.3. The UI and editor
+also run on Apple Silicon macOS with Python 3.12, OpenGL 4.1 and Retina
+rendering. CUDA tensor rendering 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).
+CUDA rendering is unavailable on macOS.
+
+## Public render functions
+
+Every module-level function decorated with `@render_func` in the library is
+automatically available as `meltygui.<function_name>`, including
+`meltygui.draw_bool(True)`. No export list needs updating when adding a renderer.
+Discovery reads source on the first render-function lookup or `dir(meltygui)`;
+individual view modules still load only when accessed. Newly added functions
+are discovered on the next interpreter run. `dir(meltygui)` and `__all__` include
+the discovered names; static IDE completion may not enumerate these dynamic exports.
+
+Render function names must be unique across library modules. Duplicate names
+raise an error identifying both modules. Nested functions, class methods and
+bundled examples are not package-level library exports.
+
+## Use ImGui directly
+
+The bundled ImGui bindings are public as `meltygui.imgui` (also available with
+`from meltygui import imgui`). They load on first access and share the same
+ImGui context as MeltyGUI. Call drawing functions inside a window callback:
+
+```python
+import meltygui
+
+@meltygui.glfw_window
+def some_window():
+    meltygui.imgui.text("Hello")
+```
+
+## 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.