S.js - simple, clean, fast reactive programming in Javascript
Encode & decode XML and HTML entities with ease & speed
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Escape RegExp special characters
Flow types for the Javascript AST
a CSS selector compiler/engine
MermaidJS parser
Regenerate sets for Unicode properties and values.
The set of canonical Unicode property names supported in ECMAScript RegExp property escapes.
Unicode property alias mappings in JavaScript format for property names that are supported in ECMAScript RegExp property escapes.
Create PDF files on the browser and server
An Error subclass that will chain nested Errors and dump nested stacktraces
A render engine for Node and the browser
Create binary artifacts hosted by github and install them without compiling.
Match a Unicode property or property alias to its canonical property name per the algorithm used for RegExp Unicode property escapes in ECMAScript.
Check if the process is running in a Continuous Integration (CI) environment
fast and safe way to escape and unescape &<>'" chars
warns if there is a newer version of CLI released
A minimalistic JavaScript implementation of the Jinja templating engine, specifically designed for parsing and rendering ML chat templates.
Check if the process is running in an SSH session
Client for the realtime Engine
Drizzle Kit is a CLI migrator tool for Drizzle ORM. It is probably the one and only tool that lets you completely automatically generate SQL migrations and covers ~95% of the common cases like deletions and renames by prompting user input. <https://github
A well-tested CSS minifier
A responsive image cropping tool for React
Two simple macros that make it easy to add the source location to the anyhow context errors.
Wrap std APIs with anyhow error context.
Flexible concrete Error type built on std::error::Error with serde support
Utilities to allow setting ddshow loggers for timely dataflow programs
Convert number to enum
A simple SDK for mochow compatible API.
A CLI that displays an animated simplex noise field in your terminal with ASCII
Implements the "S-Stemmer" from "How Effective Is Suffixing?"
El4r enables you to write Emacs programs in Ruby(EmacsRuby) as well as in EmacsLisp. It also enables you to unit-test Emacs programs automatically both in EmacsLisp and in EmacsRuby. == How to install ruby -ropen-uri -e 'URI("http://www.rubyist.net/~rubikitch/archive/el4r-1.0.4.tar.gz").read.display' > el4r-1.0.4.tar.gz tar xzf el4r-1.0.4.tar.gz cd el4r-1.0.4 ruby setup.rb ruby -S el4r-rctool -p ruby -S el4r-rctool -i == How to use See the files below testing/ and doc/.
Request log analyzer's purpose is to find out how your web application is being used, how it performs and to focus your optimization efforts. This tool will parse all requests in the application's log file and aggregate the information. Once it is finished parsing the log file(s), it will show the requests that take op most server time using various metrics. It can also insert all parsed request information into a database so you can roll your own analysis. It supports Rails-, Merb- and Rack-based applications logs, Apache and Amazon S3 access logs and MySQL slow query logs out of the box, but file formats of other applications can easily be supported by supplying an easy to write log file format definition.
El4r enables you to write Emacs programs in Ruby(EmacsRuby) as well as in EmacsLisp. It also enables you to unit-test Emacs programs automatically both in EmacsLisp and in EmacsRuby. == How to install ruby -ropen-uri -e 'URI("http://www.rubyist.net/~rubikitch/archive/el4r-1.0.4.tar.gz").read.display' > el4r-1.0.4.tar.gz tar xzf el4r-1.0.4.tar.gz cd el4r-1.0.4 ruby setup.rb ruby -S el4r-rctool -p ruby -S el4r-rctool -i == How to use See the files below testing/ and doc/.
A very simple naive Bayesian classifier. I'm just using it as practice as I learn how to package ruby code. The algorithm used here is not original, but an adaptation from Burak Kanber's Machine Learning in Javascript series. http://readable.cc/feed/view/34236/burak-kanber-s-blog
BlackStack Deployer automates what you already know how to do manually, but in a repeatable, scalable fashion. There is no magic here! BlackStack Deployer dutifully connects to your server(s) via SSH and executes the steps necessary to deploy your project. You can define those steps yourself, or by using pre-built task libraries provided by the BlackStack Deployer community.
Deployer automates what you already know how to do manually, but in a repeatable, scalable fashion. There is no magic here! Deployer dutifully connects to your server(s) via SSH and executes the steps necessary to deploy your project. You can define those steps yourself, or by using pre-built task libraries provided by the Deployer community.
Request log analyzer's purpose is to find ot how your web application is being used and to focus your optimization efforts. This tool will parse all requests in the application's log file and aggregate the information. Once it is finished parsing the log file(s), it will show the requests that take op most server time using various metrics. It can also insert all parsed request information into a database so you can roll your own analysis. It supports Rails- and Merb-based applications and Apache access log files out of the box, but file formats of other applications can easily be supported by supplying an easy to write log file format definition.
== Glossa is a tool for generating simple naming language generators (which can in turn generate names). Note: Version 1.0.0 is an (almost) direct port of {mewo2's JavaScript naming-language generator}[https://github.com/mewo2/naming-language]. These initial ideas are his, and I have changed very little of the actual inner-workings (other than basically turn it into a class). I would _highly_ encourage everybody to go and checkout his original repo (link above), {read his documentation on how the language generator works}[http://mewo2.com/notes/naming-language/], and {follow @unchartedatlas}[https://twitter.com/unchartedatlas]
Request log analyzer's purpose is to find ot how your web application is being used and to focus your optimization efforts. This tool will parse all requests in the application's log file and aggregate the information. Once it is finished parsing the log file(s), it will show the requests that take op most server time using various metrics. It can also insert all parsed request information into a database so you can roll your own analysis. It supports Rails- and Merb-based applications and Apache access log files out of the box, but file formats of other applications can easily be supported by supplying an easy to write log file format definition.
==== 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
CORTO - your url shortner gem ----------------------------- - Yet another url shortner? corto is a ruby gem that shorten a URL for you and store the result in a SQLite3 database. Why the world needs another url shortener? Well, true to be told I don't know the answer and I'm pretty sure this code is far away from being revolutionary. However... corto is funniest! - Usage Using corto as standalone utility is straightforward. In case you want to shorten an url you just launch the program with the url as parameter. % bin/corto http://www.armoredcode.com % corto: http://www.armoredcode.com shrunk as ji5jnu Please note that you've to supply a valid URL, since internally it's parsed and rejected anything but HTTP and HTTPS verbs. % bin/corto funnystatementhere % corto: it seems funnystatementhere is not a valid url to shrink If you want to deflate a shrunk url, you have just to specify the '-d' flag this way. % bin/corto -d ji5jnu % corto: ji5jnu deflated is http://www.armoredcode.com Super easy, isn't it? Now, go ahead and shrink the web! - API A simple corto shortening session start with class initialization, optionally telling which SQLite3 database to use and then mastering the parameter. require 'corto' ... corto = Corto.new # we're now saying the gem we want to use it's internal database stored in db/corto.db s = corto.shrink('http://www.armoredcode.com') # s now stores the shrinked url that is already added to database if not present. # If you'll pass an invalid url to shrink(), nil will be returned instead Deflating a URL is super easy as well # The deflate process is quite straightforward as well d = corto.deflate(s) # d has now the deflated url or nil if that url was not found You can also count how many urls contained into db # If you want to know how many urls you have in your database, just call the count() method. puts 'Hey, I have stored ' + corto.count() + ' urls' And finally you can purge your db # Tired of your database and time for a massive clean has come? Let's purge the db. corto.purge # corto.count == 0 now - Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so I don’t break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. - Copyright Copyright © 2011 Paolo Perego. See LICENSE for details.
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.