An isomorphic client library for the Azure Document Intelligence service.
A structuredClone polyfill
A library to create readable "multipart/form-data" streams. Can be used to submit forms and file uploads to other web applications.
JavaScript utilities with respect to emerging standard
WIP V2 – Headless UI form powered by JSON Schemas
The modular and type safe schema library for validating structural data
Performant, flexible and extensible forms library for React Hooks
An env-agnostic serializer and deserializer with recursion ability and types beyond JSON, based on the HTML structured clone algorithm.
Encode FormData content into the multipart/form-data format
Underlying schema language parsed from arktype syntax.
Protocol Buffers for JavaScript & TypeScript.
Implementation of Structured Field Values for HTTP (RFC9651, RFC8941)
Provides information about the plural forms from any language that you may know
Expo module implementation of a parser based on https://httpwg.org/specs/rfc8941.html
React component for building inline, popup, or sidebar forms to edit structured data
No description provided.
A free MIT-licensed React UI component that renders dynamic, interactive JSON-based forms and surveys. You can use it to collect responses from users and send them to your own database.
JavaScript parser written in OCaml. Produces ESTree AST
Document Intelligence Rest Client
React Hook Form validation resolvers: Yup, Joi, Superstruct, Zod, Vest, Class Validator, io-ts, Nope, computed-types, TypeBox, arktype, Typanion, Effect-TS and VineJS
Utility wrapper around react-hook-form for use with react-router v7+
Work with IANA language tags.
TypeScript definitions for @ungap/structured-clone
No description provided.
Kaitai Struct is a declarative language used for describe various binary data structures, laid out in files or in memory: i.e. binary file formats, network stream packet formats, etc. The main idea is that a particular format is described in Kaitai Struct language (.ksy file) and then can be compiled with ksc into source files in one of the supported programming languages. These modules will include a generated code for a parser that can read described data structure from a file / stream and give access to it in a nice, easy-to-comprehend API. This package is a visualizer tool for .ksy files. Given a particular binary file and .ksy file(s) that describe its format, it can visualize internal data structures in a tree form and a multi-level highlight hex viewer.
Mokio is a Content Management System that allows creation of sophisticated websites. It consists maily of administration panel for your desired website. It provides the following types of content: Article (piece of text with pictures, lists, links, etc.), Picture Gallery (easily managed article with a number of photos - thumbs and edition provided), Movie Gallery (article with links to Dailymotion, Vimeo and Youtube movies - thumbs and edition provided), Contact Page with Google map and contact form. Apart from content it is possible to manage menu structure of your website for each language and defined position (part of the screen). If this is not enough for what you need, you can also include pieces of HTML code that should be shared by some (or all) subpages - called HTML Blocks. You can define on which part of the page, these blocks should be displayed. Mokio provides also administration panel for javascripts, languages and backend users. Beside Mokio itself, there are various gems dedicated for Mokio, that extends its core functionality. Visit: http://www.mokio.org Folow us on facebook: https://www.facebook.com/mokioCMS
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.
No description provided.
No description provided.
No description provided.