Intelligent Forms to detect invalid inputs
Default Renderer Set for JSON Forms
Material Renderer Set for JSON Forms
Core module of JSON Forms
Vue 3 Vanilla renderers for JSON Forms
The modular and type-safe form library for SolidJS
Build forms in React, without the tears
No description provided.
React module of JSON Forms
Forms utilities for PrimeUI Libraries
React Hook Form validation resolvers: Yup, Joi, Superstruct, Zod, Vest, Class Validator, io-ts, Nope, computed-types, TypeBox, arktype, Typanion, Effect-TS and VineJS
The modular and type-safe form library for Qwik
A plugin that provides a basic reset for form styles that makes form elements easy to override with utilities.
Compiles a function to compute the plural forms index for a given value
Formly is a dynamic (JSON powered) form library for Angular that bring unmatched maintainability to your application's forms.
The modular and type-safe form library for Preact
A rapid form development library for Angular
A best-practices CSS foundation
Set of forms components and blocks for GrapesJS editor
Provides information about the plural forms from any language that you may know
Vue 3 module of JSON Forms
VGS Collect.js script loading module
Formly is a dynamic (JSON powered) form library for Angular that bring unmatched maintainability to your application's forms.
The input component is designed for capturing user input within a text field.
A bevy plugin for creating forms.
A bevy plugin for creating forms.
Acquire stock infomations form yahoofinance, I am so sorry to Yahoo!.
It will acquire a stock infomations form yahoofinance, although I am very sorry to Yahoo!.
A Rails 3+ Engine providing a basic contact form. I used Formtastic to keep things simple, and to hook into your apps custom Formtastic stylesheets.
Formative is an extraction of the custom form builder I used in my last couple of Rails projects. It is the simplest thing that could possibly work for me. YMMV.
A handy dandy way to avoid using #accepts_nested_attributes_for
Aurita::GUI provides an intuitive and flexible API for object-oriented creation of primitive and complex HTML elements, such as tables and forms. It is a core module of the Aurita application framework, but it can be used as stand-alone library in any context (such as rails). As there seems to be a lack of ruby form generators, i decided to release this part of Aurita in a single gem with no dependencies on aurita itself.
Trivial convenience app for generating bin/executable unix utilites in scriping language of your choice, defaulting to ruby, because. I often forget the exact form and go to copy an existing one, this just saves me the effort, and anyone else who has the same issue.
Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.
Words, with both pure ruby & tokyo-cabinate backends, implements a fast interface to Wordnet over the same easy-to-use API. The FFI backend makes use of Tokyo Cabinet and the FFI interface, rufus-tokyo, to provide cross ruby distribution compatability and blistering speed. The pure ruby interface operates on a special ruby optimised index along with the basic dictionary files provided by WordNet. I have attempted to provide ease of use in the form of a simple yet powerful api and installation is a sintch!
it does not allow the execution of arbitrary code templates may contain functions calls of the form \\-function_name(coma,seperated,list,of,minival,values) "minival" is a variable parser (see gem "minival_refi") (last time I checked one argument was mandatory (suggestion: "\\-fun_without_args(nil)" )) usage: include Refi template = Template.new(template_string) chunks = template.get_chunks() "chunks" is an array containing the text of the template as strings and the function calls as hashes {fun_name => [list,of,arguments]}
Words, with both pure ruby & tokyo-cabinate backends, implements a fast interface to Wordnet over the same easy-to-use API. The FFI backend makes use of Tokyo Cabinet and the FFI interface, rufus-tokyo, to provide cross ruby distribution compatability and blistering speed. The pure ruby interface operates on a special ruby optimised index along with the basic dictionary files provided by WordNet. I have attempted to provide ease of use in the form of a simple yet powerful api and installation is a sintch!
RedParse is a ruby parser (and parser-compiler) written in pure ruby. Instead of YACC or ANTLR, it's parse tool is a home-brewed language. (The tool is (at least) LALR(1)-equivalent and the 'parse language' is pretty nice, even in it's current form.) My intent is to have a completely correct parser for ruby, in 100% ruby. And I think I've more or less succeeded. Aside from some fairly minor quibbles (see below), RedParse can parse all known ruby 1.8 and 1.9 constructions correctly. Input text may be encoded in ascii, binary, utf-8, iso-8859-1, and the euc-* family of encodings. Sjis is not yet supported.
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.