The abstract class for creating web components
ECMAScript spec abstract operations.
Abstract element implementation for Eclipse Theia based editors.
A collection of implementation for ECMAScript abstract operations
Write Pino transports easily
Abstract element class extending functionality of Selenium WebDriver. Used as part of theia-extension-tester.
An Abstract Class for describing an Ethereum Provider for ethers.
A Light–weight CSS Preprocessor
An Abstract Class for desribing an Ethereum Signer for ethers.
Abstract class for a lexicographically sorted key-value database
[](https://npm.im/@dnd-kit/abstract)
encode/decode number as bitcoin variable length integer
Create a manifest describing the abilities of an abstract-level database
Utils for writing Salesforce CLI plugins
BitGo SDK coin library for COSMOS base implementation
TypeScript definitions for abstract-leveldown
[](https://github.com/bitcoinjs/bip174/actions/workflows/main_ci.yml) [](https://www.npmjs.org/package/bip174)
BitGo SDK coin library for ETH base implementation
Docusaurus util package to abstract the current bundler.
A noop logger that conforms to the Log4j interface for modules to stub out internal logging
BitGo SDK coin library for Substrate base implementation
Abstract interface definition of Tron Wallet Adapters.
BitGo SDK coin library for base Lightning Network coin implementation
abstract base class for crypto-streams
an engine to abstract common html/css elements across Heroku properties
Abstract mechanism for setting up Institutions with arbitrary data elements.
REST chain is a library that abstracts the path elements of making a REST API call to appear as method calls in Ruby.
Form Factor is a miniature abstraction layer for view generation. Form Factor breaks the coupling between a view element and the structural markup generated, in order to make the generation more flexible. Instead of directly specifying the literal view to generate, Form Factor defers that to a template, which decides: (1) Structural markup to generate (2) stylesheets to include and (3) javascripts to include. Plugging in a different Form Factor template can be done with a single line of controller code, giving your site a different look and feel.
Portable Move Notation (PMN) v1.0.0 is a rule-agnostic, JSON-based format using arrays to represent deterministic state-changing actions in abstract strategy board games. This gem provides a consistent Ruby interface for serializing, deserializing, and validating moves across Chess, Shogi, Xiangqi, and other traditional or non-traditional variants. The v1.0.0 format uses simple 4-element arrays: [source_square, destination_square, piece_name, captured_piece], making it compact and language-agnostic while focusing on deterministic state transformations independent of game-specific rules.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
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.