A searchable dropdown supporting single, multi, and checkbox modes.
Polyfill for making HTML5 drag and drop possible in all browsers.
Drag and drop SVG, HTML or Canvas using mouse or touch input.
Essential JS 2 DropDown Components
JavaScript library for reorderable drag-and-drop lists on modern browsers and touch devices. No jQuery required. Supports Meteor, AngularJS, React, Polymer, Vue, Knockout and any CSS library, e.g. Bootstrap.
Drag and drop sans the GUI
The definitive tree component for the Web
The definitive tree component for the Web
The core package for Pragmatic drag and drop - enabling fast drag and drop for any experience on any tech stack
This version of `sanity-plugin-media` is for Sanity Studio V3.
An optional package for Pragmatic drag and drop that enables the attaching of interaction information to a drop target
JSON parse with prototype poisoning protection
A comprehensive library for mime-type mapping
An optional Pragmatic drag and drop package that enables automatic scrolling during a drag operation
TypeScript implementation of debounce
Essential JS 2 DropDown Components for React
Inquirer search prompt
An optional Pragmatic drag and drop package containing react components that provide a visual indication about what the user will achieve when the drop (eg lines)
Essential JS 2 DropDown Components for Angular
Easily add ANSI colors to your text and symbols in the terminal. A faster drop-in replacement for chalk, kleur and turbocolor (without the dependencies and rendering bugs).
A ProseMirror plugin for drop indicator
A simple node js implementation of uuid v4 for use with Braintree's JS based SDKs.
Swizzle a little something into your require() calls.
Search functionality for the CodeMirror code editor
A fully-featured Ruby API client for Flapjack Search. Drop-in replacement for the algolia gem.
The OpenSearch Toolkit provides ASP.NET developers with drop-in support for OpenSearch. This lets you quickly and easily publish valid search suggestions to all the major browsers.
Sunspot::Padrino is a derived plugin that provides drop-in integration of the Sunspot Solr search library with Padrino. It is based on the original Sunspot ::Rails library located at https://github.com/sunspot/sunspot.
Drop-in ActiveRecord concern that keeps KakugoSearch indexes in sync with your models via save/destroy callbacks, plus a search class method.
Provides RobotLab::DocumentStore — a thread-safe, in-memory semantic search store backed by fastembed (BAAI/bge-small-en-v1.5). Store text documents by key and retrieve the closest matches to a natural-language query using cosine similarity. Works standalone or as a drop-in extension for robot_lab agents and networks.
A Splay Tree is a self adjusting binary search tree with the additional property that recently accessed elements are quick to access again. This makes it useful for caches because the most commonly accessed elements will be the fastest ones to access. This tree has an additional feature that allows it's maximum size to be restricted. When it exceeds it's maximum size, it will drop all of the nodes which are at the terminal ends of the tree structure, leaving many of the more commonly accessed nodes intact. This implementation is written in C++ with a Ruby wrapper.
PluginFactory is a mixin module that turns an including class into a factory for its derivatives, capable of searching for and loading them by name. This is useful when you have an abstract base class which defines an interface and basic functionality for a part of a larger system, and a collection of subclasses which implement the interface for different underlying functionality. An example of where this might be useful is in a program which talks to a database. To avoid coupling it to a specific database, you use a Driver class which encapsulates your program's interaction with the database behind a useful interface. Now you can create a concrete implementation of the Driver class for each kind of database you wish to talk to. If you make the base Driver class a PluginFactory, too, you can add new drivers simply by dropping them in a directory and using the Driver's `create` method to instantiate them:
The "Console API" is the CRUD API for performing the actions offered on console.statsig.com without needing to go through the web UI. If you have any feature requests, drop on in to our [slack channel](https://www.statsig.com/slack) and let us know. <br /><br /> <b>Authorization</b> <br /> All requests must include the **STATSIG-API-KEY** field in the header. The value should be a **Console API Key** which can be created in the Project Settings on [console.statsig.com/api_keys](https://console.statsig.com/api_keys) <br /><br /> <b>Rate Limiting</b> <br /> Requests to the Console API are limited to <code>~ 100reqs / 10secs and ~ 900reqs / 15 mins</code>. <br /><br /> <b>Keyboard Search</b> <br /> Use <code>Ctrl/Cmd + K</code> to search for specific endpoints.
Drop Zone is a solution to the problem of restricted sales in censored markets. The proposal is for the design of a protocol and reference client that encodes the location and a brief description of a good onto The Blockchain. Those wishing to purchase the good can search for items within a user-requested radius. Sellers list a good as available within a geographic region, subject to some degree of precision, for the purpose of obfuscating their precise location. Goods are announced next to an expiration, a hashtag, and if space permits, a description. Once a buyer finds a good in a defined relative proximity, a secure communication channel is opened between the parties on the Bitcoin test network ("testnet"). Once negotiations are complete, the buyer sends payment to the seller via the address listed on the Bitcoin mainnet. This spend action establishes reputation for the buyer, and potentially for the seller. Once paid, the seller is to furnish the exact GPS coordinates of the good to the buyer (alongside a small note such as "Check in the crevice of the tree"). When the buyer successfully picks up the item at the specified location, the buyer then issues a receipt with a note by spending flake to the address of the original post. In this way, sellers receive a reputation score. The solution is akin to that of Craigslist.org or Uber, but is distributed and as such provides nearly risk-free terms to contraband sellers, and drastically reduced risk to contraband buyers.
pikuri-memory gives a pikuri-core agent durable, long-lived memory: facts about the user and their work that persist across conversations. It wires a +recall+ tool plus an automatic per-turn prefetch onto an agent via +c.add_extension Pikuri::Memory::Extension.new(...)+ inside the +Agent.new+ block — same opt-in shape as +pikuri-tasks+ / +pikuri-vectordb+. Recall is automatic and synchronous (embed + vector search, milliseconds); capture is automatic and asynchronous (an off-the-interaction-path extraction queue), so a turn never blocks on "what should I remember?". Storage is mem0 (https://github.com/mem0ai/mem0) reached over a thin Faraday HTTP client — the append-only +add+ / read-time +search+ model. Only the *user's own words* are fed to extraction (a write-side hygiene rule that structurally drops system/assistant/tool-sourced junk), and recalled context enters the chat as a +:system+ message so it is provenance-tagged and excluded from the next extraction pass. This release ships the Ruby client + extension + tool against a *bring-your-own* mem0 endpoint; a self-managed mem0 sidecar supervisor (the +ChromaServer+-style docker pattern) is a follow-on.
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.