A JavaScript library for escaping CSS strings and identifiers while generating the shortest possible ASCII-only output.
For ruby and ruby on rails
Parse, validate, traverse, transform, and optimize Oniguruma regular expressions
Ruby SemVer in TypeScript.
Convention over configuration for using Vite in Ruby apps
Like ruby's abbrev module, but in js
Ruby grammar for tree-sitter
prettier plugin for the Ruby programming language
Easy formatted numbers, currency and percentage with input/directive mask for Vue.js
WebSocket framework for Ruby on Rails.
Epson ESC POS Printer SDK for open source react-native library
Collecton of TextMate grammars in JSON
bootstrap-sass is a Sass-powered version of Bootstrap 3, ready to drop right into your Sass powered applications.
JavaScript client for graphql-ruby
realistic password strength estimation
Convention over configuration for using Vite in Rails apps
webpack5 common tools
A Stimulus Wrapper for Flatpickr library
Provide I18n to your React Native application
Prism Ruby parser
A pure JavaScript implementation of Sass.
## Installation
Ruby on Rails unobtrusive scripting adapter
A lightweight Sass tool set.
A turing machine interpreter packaged as a command line tool.
Tencent Cloud Ruby SDK is the official software development kit, which allows Ruby developers to write software that makes use of Tencent Cloud service TMS.
A reference implementation, written in Ruby, to interact with GovDelivery's TMS API. The client is compatible with Ruby >=2.5.8, and <= 2.7.1
A reference implementation, written in Ruby, to interact with GovDelivery's TMS API. The client is compatible with Ruby 1.9 and 2.0.
Simple Tile Server for Ruby
Ruby Interface to Dream Cheeky(TM) USB Devices
Ronin Dorks is a Ruby library for Ronin that provides support for various Google (tm) Dorks functionality. Ronin is a Ruby platform for exploit development and security research. Ronin allows for the rapid development and distribution of code, exploits or payloads over many common Source-Code-Management (SCM) systems.
A Ruby gem for the TMS API
An ActiveRecord-style API wrapper for TheMovieDB.org
An ActiveRecord-style API wrapper for TheMovieDB.org
jirarest2 is yet another implementation of the JIRA(tm) REST-API[https://developer.atlassian.com/display/JIRADEV/JIRA+Remote+API+Reference] . This one for Ruby1.9.1 It is intended to be called within the shell to create and verify JIRA(tm) issues fast without a browser. There was no particular need for perfomance at the time of writing. This implementation is still a for cry from others like http://rubygems.org/gems/jira-ruby which requires oauth authentication. There are scripts to create new issues with watchers and link those to existing issues and to manipulate watchers on existing issues. *Use it at your own risk. Most of the API features are not implemented.* *Ruby1.9.1 is needed. Ruby1.8 doesn't work!*
==== Topic Maps for Rails (rtm-rails) RTM-Rails is the Rails-Adapter for Ruby Topic Maps. It allows simple configuration of topicmaps in config/topicmaps.yml. ==== Overview From a developer's perspective, RTM is a schema-less database management system. The Topic Maps standard (described below) on which RTM is based provides a way of creating a self-describing schema just by using it. You can use RTM as a complement data storage to ActiveRecord in your Rails apps. ==== Quickstart - existing Rails project jruby script/generate topicmaps Run the command above after installing rtm-rails. This will create * a minimal default configuration: config/topicmaps.yml and * a file with more examples and explanations config/topicmaps.example.yml * a file README.topicmaps.txt which contains more information how to use it and where to find more information * an initializer to load the topicmaps at startup * a rake task to migrate the topic maps backends in your rails application. ==== Quickstart - new Rails project For a new Rails application these are the complete initial steps: jruby -S rails my_topicmaps_app cd my_topicmaps_app jruby -S script/generate jdbc jruby -S script/generate topicmaps # The following lines are necessary because Rails does not have a template # for the H2 database and Ontopia does not support the Rails default SQLite3. sed -e "s/sqlite3/h2/" config/database.yml > config/database.yml.h2 mv config/database.yml.h2 config/database.yml # Prepare the database and then check if all is OK jruby -S rake topicmaps:migrate_backends jruby -S rake topicmaps:check ==== Usage inside the application When everything is fine, let's create our first topic: jruby -S script/console TM[:example].get!("http://example.org/my/first/topic") # and save the topic map TM[:example].commit Access the configured topic maps anywhere in your application like this: TM[:example] To retrieve all topics, you can do TM[:example].topics To retrieve a specific topic by its subject identifier: TM[:example].get("http://example.org/my/topic") Commit the changes to the database permanently: TM[:example].commit ... or abort the transaction: TM[:example].abort More information can be found on http://rtm.topicmapslab.de/ ==== Minimal configuration default: topicmaps: example: http://rtm.topicmapslab.de/example1/ The minimal configuration creates a single topic map, named :example with the locator given. This topic map will be persisted in the same database as your ActiveRecord connection if not specified otherwise. The default backend is OntopiaRDBMS (from the rtm-ontopia gem). A more complete configuration can be found in config/topicmaps.example.yml after running "jruby script/generate topicmaps". It also includes how to specifiy multiple connections to different data stores and so on. ==== Topic Maps Topic Maps is an international industry standard (ISO13250) for interchangeably representing information about the structure of information resources used to define topics, and the relationships between topics. A set of one or more interrelated documents that employs the notation defined by this International Standard is called a topic map. A topic map defines a multidimensional topic space - a space in which the locations are topics, and in which the distances between topics are measurable in terms of the number of intervening topics which must be visited in order to get from one topic to another, and the kinds of relationships that define the path from one topic to another, if any, through the intervening topics, if any. In addition, information objects can have properties, as well as values for those properties, assigned to them. The Topic Maps Data Model which is used in this implementation can be found on http://www.isotopicmaps.org/sam/sam-model/. ==== License Copyright 2009 Topic Maps Lab, University of Leipzig. Apache License, Version 2.0