Use the display-p3-linear color space on the color() function in CSS
PaySwarm Payment Processor
A high-performance color library with extended support for modern color spaces including OKLCH, OKLAB, Display-P3, and more
A precision-crafted P3 color system designed for modern UIs
P3 JSON PRC Controller
JSONPath, JSON Pointer and JSON Patch
P3 SDK for Node.js and the browser
* Handling L1/L2/L3 tickets * Handling P1/P2/P3 incidents * Developing
**Now supports Tailwind v4, P3 display, and opacity at the same time!**
Node-RED nodes for Tibbo-Pi P3
A simple Yeoman website generator to start lightweight P3 client projects
React color picker that supports Color Module 4, wide color gamut (WCG), and Display-P3 using WebGL for monitor-accurate colors. Powered by colorjs.io.
Color utilities (css, p3, hex, hsl, hsv, hwb, lab, lch, xyz, okhsl, okhsv, oklab, oklch, hpluv, hsluv, lchuv, bytes) for PEX.
A color palette library based on [Radix Colors](https://www.radix-ui.com/colors) with support for both sRGB and Display P3 color spaces.
PostCSS plugin to use Helmlab color spaces in CSS — helmlab(), helmlch(), helmgen(), helmgenlch() with rgb() fallback plus @supports-wrapped color(display-p3 …) and color(rec2020 …) overrides
DIP protocol executor with harness testing. Generate P1/P2/P3 docs and auto-generate tests that verify agent behavior.
Generate a random display-p3 color.
Gamut map css colors to fit display specific gamuts
A simple, easy-to-use library for connecting to the Mikesoft P3 network.
Use oklab() and oklch() color functions in CSS
A simple, easy-to-use library for connecting to the Mikesoft P3 network.
CLI for streaming Sveriges Radio (P1, P2, P3)
Miden variant of Goldilocks field with public const constructors.
Shared development utilities (benchmarks, test fixtures) for p3-miden crates
Miden-specific AIR traits and utilities for Plonky3.
Miden-specific FRI implementation with configurable folding factor, based on Plonky3's FRI.
AIR traits for the Miden lifted STARK protocol, with symbolic constraint analysis.
Example AIRs wrapped for the lifted STARK prover.
Lifted FRI PCS (DEEP quotient + FRI).
Lifted STARK prover and verifier (LMCS-based).
Lifted Matrix Commitment Scheme (LMCS) for matrices with power-of-two heights.
Miden-specific STARK prover built on Plonky3.
Stateful sponge-like hashers for cryptographic hashing
Transcript channels for Fiat-Shamir protocols with raw field/commitment storage
Simplified PPP for serial comms between ruby host and microcontroller -- framed packets, library
Organize and rename your TV Shows. Automatically find links to missing shows. Includes Command-Line Utility 'p3tv'
Parses EZTV.ag's HTML as they do not have a clean REST API
Search thetvdb.com's database with this api ( requires thetvdb.com registration )
Transmission RPC API
A simple hello world gem
JSONPath following RFC 9535
P3 Library bundle for other Engines
Inserts P3P header
Gemita para la p3 de ttps ruby UNLP
## A mirror API for Ruby In various [research][p1] [projects][p2] the advantages of having a [mirror API][p3] to separate reflection from a language implementation have been discussed, and "industry grade" implementations exist for [Java][p4] and [C#][p5]. This project aims at providing a number of specs and classes that document a mirror API for Ruby. The mirror implementation that is part of this project will use only those language facilities that are available across Ruby implementations. The specs, however, will also test behavior that cannot be provided in such a manner. The idea here is that in time, all implementations provide their own implementation of the mirror API, and all implementations collaborate on this one spec. Why do this, you ask? Because Ruby needs tools, and those tools need to be written in Ruby. If they are not, then people will be excluded from tinkering with their tools, thus impeding innovation. You only have to look at Emacs or Smalltalk to see what's possible when programmers can extend their tools, all tools, in a language they feel comfortable in. If we have a standard mirror API, all tools that are written **for** Ruby, **in** Ruby, can be shared across implementations, while at the same time allowing language implementers to use the facilities of their platform to provide optimal reflective capabilities without tying them to internals. [p1]: http://www.cs.virginia.edu/~lorenz/papers/icse03/icse2003.pdf "Pluggable Reflection: Decoupling Meta-Interface and Implementation" [p2]: http://bracha.org/newspeak-spec.pdf "Newspeak Programming Language Draft Specification, Version 0.06, pages 40 onward" [p3]: http://www.hpi.uni-potsdam.de/hirschfeld/events/past/media/100105_Bracha_2010_LinguisticReflectionViaMirrors_HPI.mp4 "Linguistic Reflection Via Mirrors" [p4]: http://bracha.org/mirrors.pdf "Mirrors: Design Principles for Meta-level Facilities of Object-Oriented Programming Languages" [p5]: http://oreilly.com/catalog/progcsharp/chapter/ch18.html "See esp. 18-3, highlighting how C# reflection works on assembly rather than VM objects"
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.