A small utility library for dealing with Perforce
[`nano-css`](https://github.com/streamich/nano-css) configuration for P4.
Design system for P4
[**Launch Storybook**](http://infrastructure.production.ci.onp4.com.s3.amazonaws.com/builds/p4-universal/master/storybook/index.html)
External P4 UI References
P4 Plan MCP (Model Context Protocol) Server
A Model Context Protocol (MCP) server that provides a clean interface for Perforce (P4) operations in Claude Desktop. This server wraps P4 commands to make them more reliable and easier for Claude to use, eliminating issues with interactive prompts and co
Node-RED nodes for Tibbo-Pi P4
A package to control P4 from the command line.
Heat map for P4 changes
P4 sidebar bot
Typed TypeScript helpers for the Perforce p4 CLI
Node.js SDK for the P4 Rust core C ABI
Enterprise-grade MCP (Model Context Protocol) server for Perforce P4 integration with AI assistants. Includes 59 MCP tools, native-style batch and flag support, rich review/search workflow helpers, and comprehensive security controls such as audit logging
You can use this bot on [P4](https://peefour.com) directly from NPM. Just go to the stream where you want to use this bot and in the URL field enter `p4-bot-blog@x.x.x/dist.js`.
MCP server for P4 Compara - management accounting SaaS for Japanese SMEs
Yeoman generator for Foundation 6 + Sass + Gulp + Webpack + Composer + PHP
A small object-oriented utility library for dealing with Perforce
Screenshot Bot P4 bot
generate patch file from p4 command line
perforce client api for node.js
Portable parallel processing pipelines
perforce plugin for gulp
jspm perforce endpoint
no_std async Ethernet MAC driver for ESP32-P4 RMII designs (embassy-net compatible)
All-Rust 1st-stage bootloader for ESP32-P4. Replaces IDF v5.3 bootloader.bin (which has hard architectural assumptions about app segment layout that no_std Rust apps don't satisfy). ROM loads us from flash@0x2000; we init the chip, read the partition table, locate the factory app, verify its appended SHA256, load segments via cache, and jump to its entry.
ESP32-P4 Octal/Hex PSRAM bring-up — clean Rust port of IDF v5.4's `esp_psram_impl_ap_hex.c`. Programs MSPI_2/MSPI_3 controllers, PSRAM mode registers (vendor/density read, X16 + page-mode + fixed-latency write), cache-side OPI/Hex DDR config, MMU 32 MB window mapping. Hardware-validated end-to-end on Waveshare ESP32-P4-ETH (vendor=0x0D, 32 MB).
ESP32-P4 hardware bring-up: BOD/WDT/PMU/MPLL/PVT/MSPI/cache/MMU init. Drop-in replacement for the chip-init portion of an IDF 2nd-stage bootloader, in pure Rust, for `--ram --no-stub` boot or as the chip-init module of a custom 1st-stage bootloader.
P4 API (wraps CLI)
Python bindings for laddu
A (WIP) library for writing P4 controller in Rust.
Segment rustc-dev.target.x86_64-pc-windows-msvc part p4
Proto crate for Rusty-p4. Using p4runtime from PI repo.
A developer-friendly, high-performance 3D rendering engine written in Rust.
Raw Rust FFI bindings for Espressif ESP-NN
Amplitude analysis made short and sweet
p4 command wrapper with some custom functions for easy use
Provides a base set of HTTP calls to execute Perforce commands.
Submit changes made to a Git repository into to Perforce
The P4 Web API provides a simple HTTP interface for many p4 operations. This provides a simple ruby client to that interface.
Submit changes made to a Git repository into to Perforce
Ruby extensions to the C++ Perforce API.
The p4util command itself provides other commands, see 'p4util help' after install. This allows you to things like download a p4d, start it, kill it, etc mostly for quick setup of testing systems.
Simple command line tool to run custom perforce commands.
P4B Common Library.
## 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.