基于nativeShare进行了二次扩展, 添了除调起UC，QQ浏览器内置分享组件之外的其他浏览器适配。添加到npm。
Share text, images (and other files), or a link via the native sharing widget of your device. Android is fully supported, as well as iOS 6 and up. WP8 has somewhat limited support.
Native sharing using the Web Share API if supported, a beautiful fallback if not.
A Tauri v2 plugin that enables sharing content with native sharing interfaces on Android, iOS, macOS and Windows.
A Vue component to use native sharing mechanism of the device as part of the Web Share API.
A small JS utility library for sharing text content via WhatsApp or via the native sharing widget of your device.
Cordova plugin for Native Sharing
A customizable React share button component that leverages the Web Share API. Easily integrate native sharing functionality into your React applications with support for custom icons, colors, and share content.
Provides a way to share files directly with other compatible applications.
Share text, images (and other files), or a link via the native sharing widget of your device. Android is fully supported, as well as iOS 6 and up. WP8 has somewhat limited support.
Share text, images (and other files), or a link via the native sharing widget of your device. Android is fully supported, as well as iOS 6 and up. WP8 has somewhat limited support.
React Native Sharing Capabilities
CLI for md.pockla.com - save and edit markdown notes from your shell or CI. Pairs with the md pockla MCP server for agent-native sharing.
Native sharing using the Web Share API if supported, a beautiful fallback if not.
Core logic for Polaris Viz that is not platform specific
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
This plugin allows you to use the native sharing window of your mobile device.
Yeoman generator: Create project and components for both Web and Native sharing all logic
Native sharing using the Web Share API if supported, a beautiful fallback if not.
Cordova plugin for Native Sharing
Web API compatible fetch implementation
Social share, sending simple data to other apps.
Ionic Native - Native plugins for ionic apps
Cordova plugin for Native Sharing
Ruby FFI for Built a Shared Library by GraalVM Native Image
Ruby bindings for smbCloud Auth, powered by the shared Rust SDK and a native Magnus extension.
The AFsplitter is used by LUKS to store encrypted keys in its header. There is a native Ruby implementation and a FFI implementation that binds the "libafsplit.so" shared library. AFsplitter is documented at http://clemens.endorphin.org/AFsplitter.
Per-gem control over copying native extension shared libraries (.so/.bundle) into the gem's lib/ directory after installation. Useful for old/unmaintained gems that expect extensions in lib/.
Prebake speeds up bundle install by skipping native gem compilation. It fetches precompiled binaries for gems like puma, nokogiri, pg, grpc, and bootsnap from a shared cache instead of compiling C extensions from source. Drop-in Bundler plugin - one line in your Gemfile, no other changes needed. Works out of the box with the hosted cache at gems.prebake.in, or self-host with S3-compatible storage (AWS S3, Cloudflare R2, Backblaze B2, MinIO) or Gemstash. Works with Ruby 3.2+ and Ruby 4.0 on any platform.
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.
winipc is a native extension that exposes Windows local inter-process communication through an ergonomic, safe-by-default Ruby API: duplex named pipes (byte and message mode, with a server and a connect-with-retry client), pagefile-backed shared memory via named file mappings, and named synchronization objects (mutex, event, semaphore). Pipe handles are opened for overlapped I/O so they cooperate with a fiber scheduler, and objects are created with a restrictive security descriptor by default. Windows MSVC (mswin) Ruby only.
Scrapetor is a Ruby HTML parsing + scraping toolkit. The parser is a native C arena DOM with structural indexes built at parse time and NEON SIMD scanners in the SAX hot loop. A streaming extraction engine compiles the schema DSL into a single forward pass — no DOM materialised, one Ruby boundary crossing per document. On builds where libcurl is available, Scrapetor::Fetcher adds an HTTP/2-capable fetch layer with per-thread connection cache, shared DNS + TLS session pool, in-process gzip / deflate / brotli / zstd decoding, iconv charset transcoding, retry + exponential backoff, ETag / Last-Modified disk cache with bulk revalidation, per-host throttle, cookie jar, basic + bearer auth, proxy, and three bulk concurrency models (parallel_fetch / multi_fetch / streaming multi_each). Scrapetor::Session ties the cookie / auth / throttle / retry policies together. Also ships robots.txt + sitemap.xml parsers, a bounded-memory streaming HTML parser, and structured-data extractors (JSON-LD, OpenGraph, Schema.org, Microdata, RDFa, Twitter Cards). The Net::HTTP-based Scrapetor.fetch is preserved as the no-libcurl fallback.
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.