A simple, editable and draggable tree component
Core logic for the editable widget implemented as a state machine
A small React hook to turn elements into fully renderable & editable content surfaces, like code editors, using contenteditable (and magic)
React component used to build inline-editable components
TypeScript definitions for leaflet-editable
React Editable Json Tree
A suite of 3D-enabled data editing overlays, suitable for deck.gl
Provides React components and integration layer with Adobe Experience Manager Page Editor.
TypeScript definitions for x-editable
Inquirer input text prompt
In-place editing with Twitter Bootstrap, jQuery UI or pure jQuery
A UI component library made by Instructure Inc.
Escape HTML utils.
SPS Woodland Design System Editable Table component
Friendly contenteditable API
A JSON tree view component that is easy to use and also supports data selection.
TypeScript definitions for react-input-mask
A collection of unstyled, accessible UI components for React, utilizing state machines for seamless interaction.
Headless core for visual-json — the visual JSON editor. Schema-aware, embeddable, extensible.
<img style="width:100%" src="https://user-images.githubusercontent.com/4838076/143581035-ebee5ba2-9cb1-4fe8-a05b-2f44bd69bb4b.gif" alt="Component toolkit for live running code editing experiences" />
Essential JS 2 DropDown Components
Lexical is an extensible text editor framework that provides excellent reliability, accessible and performance.
A content-editable component for ember-cli that just works.
The modern CSS-in-JS library
A screen + vim IDE setup for editing a Rails tree
Editions for ActiveRecord models
Create, edit, and traverse dialogue trees
This gem provides ui components for Rails Applicaitons based on Cells, that can be used to edit the criteria_operator expression trees.
Minimal CMS Rails Engine or more likelly a "static" pages manager. Pages can be created, deleted, edited and arranged into sections using a file tree like interface courtesy of jQuery tree (http://jstree.com). It attempts to be as minimal, flexible and unobtrusive as posible leaving a lot of functionality like templating languages and authentication/authorization for page creation, deletion and editing for the Rails app developer to implement. (It now works after premature release)
scorm2004-manifest is a Ruby gem that provides a manifest file parser for SCORM 2004 4th edition. It parses and validates the manifest file according to SCORM 2004 4th Edition Content Aggregation Model (CAM) Version 1.1. After parsing and validating, it builds an object tree that captures XML's hierarchical structure.
pikuri-workspace adds "operate on a directory tree" to pikuri-core agents: the +Pikuri::Workspace::Filesystem+ class that scopes filesystem access to an anchor + explicit readable / writable prefix lists (with optional ephemeral temp playground), the +Pikuri::Workspace::Confirmer+ seam (+AUTO_APPROVE+ + +TERMINAL+) for user-state mutations, and five tools wired to those seams: +Pikuri::Workspace::Read+, +Pikuri::Workspace::Write+, +Pikuri::Workspace::Edit+, +Pikuri::Workspace::Grep+, and +Pikuri::Workspace::Glob+. Self-contained — no shell execution; +Pikuri::Code::Bash+ ships in pikuri-code on top of these.
CommandSet is a user interface framework. Its focus is a DSL for defining commands, much like Rake or RSpec. A default readline based terminal interpreter (complete with context sensitive tab completion, and the amenities of readline: history editing, etc) is included. It could very well be adapted to interact with CGI or a GUI - both are planned. CommandSet has a lot of very nice features. First is the domain-specific language for defining commands and sets of commands. Those sets can further be neatly composed into larger interfaces, so that useful or standard commands can be resued. Optional application modes, much like Cisco's IOS, with a little bit more flexibility. Arguments have their own sub-language, that allows them to provide interface hints (like tab completion) as well as input validation. On the output side of things, CommandSet has a very flexible output capturing mechanism, which generates a tree of data as it's generated, even capturing writes to multiple places at once (even from multiple threads) and keeping everything straight. Methods that normally write to stdout are interposed and fed into the tree, so you can hack in existing scripts with minimal adjustment. The final output can be presented to the user in a number of formats, including contextual coloring and indentation, or even progress hashes. XML is also provided, although it needs some work. Templates are on the way. While you're developing your application, you might find the record and playback utilities useful. cmdset-record will start up with your defaults for your command set, and spit out an interaction script. Then you can replay the script against the live set with cmdset-playback. Great for ad hoc testing, usability surveys and general demos.