Results for arrangeable

Real-time music synthesizer and composition engine with dynamic playback control, advanced audio effects, and optional GPU-accelerated synthesis via WGPU. Designed for on the fly compositing.

Real-time music synthesizer and composition engine written with dynamic playback control and advanced audio effects. Designed for on the fly compositing.

Convenience functions for populating an array with values from a range.

Statically bounds-checked (machine-word-abstracting? TBD) ranged types as zero or low-runtime overhead abstractions providing safe (no unintentional overflow) arithmetic.

Chicago TDD testing framework and tools for Rust projects

Testing library that provides some tools to apply "Advanced" Arrange-Act-Assert testing design.

A cross-platform window manager crate for Tauri applications

An easy to use library for building beautiful tables with automatic content wrapping

Build beautiful tables. Supports content wrapping, alignment and cell spanning.

Generate, count, and sample chess back-rank arrangements under composable constraints (Chess960, Chess2880, custom presets)

An API for creation and management of rich (as in rich-text) musical-ish projects.

surge synthesizer -- moog filter

Arrangeable provides an organized and seamless way to sort your ActiveRecord objects by different attributes.

Friendly and easy sort

Receives queries from RoQua, sends them to Mirth, and translates Mirth's responses back into Rubyland.

Library to organize my MP3 collection

An easy way to follow the "Arrange, Act, Assert" pattern in your Ruby on Rails tests

Collect and arrange some outdated libraries for several platforms

Arranges content into a fixed number of columns using a bin packing algorithm.

A tiny mocking framework focused on the Arrange-Act-Assert test pattern. Grasshopper is heavily modeled after Mockito.

Restores and arranges multiple SciTE sessions within KDE

Prepare a musical arrangement from a score by assigning instruments to parts.

treestore stores two different types of data: 1) values, which are stored according to their SHA-1 hashcode 2) trees, which are sets of values and/or other trees, stored via a SHA-1 hashcode In addition, there are references that allow you to 'bookmark' a SHA-1 hashcode for easier lookup. If you think of the core git, but on any key-value backend store (like the included Redis one), you've got the right idea.

You can arrange error object before rescue_from handles.