Open Source Ruby Libraries - Page 3

A base Rails 4 application. Features user and admin system with Facebook login. It is instadeployable to Heroku. The view is implemented using Bootstrap 3.

Try any android library hosted online directly from the command line. Try any android library hosted online directly from the command line. Specify any custom branch to run. Specify any flavour to run. Specify any app module to run. Checkout tag/commit hash to clone (e.g. "v0.4.5", "6f7dd4b").

factory_bot is a fixtures replacement with a straightforward definition syntax, support for multiple build strategies (saved instances, unsaved instances, attribute hashes, and stubbed objects), and support for multiple factories for the same class (user, admin_user, and so on), including factory inheritance. factory_bot provides a framework and DSL for defining and using factories - less error-prone, more explicit, and all-around easier to work with than fixtures. Each factory has a name and a set of attributes. The name is used to guess the class of the object by default. It is recommended that you have one factory for each class that provides the simplest set of attributes necessary to create an instance of that class. If you're creating ActiveRecord objects, that means that you should only provide attributes that are required through validations and that do not have defaults. Other factories can be created through inheritance to cover common scenarios for each class.

Whether you need compute, dns, storage, or a multitude of other services, fog provides an accessible entry point and facilitates cross-service compatibility. Just getting started working with cloud resources? You are not alone, and having so many complicated options makes it hard to know where to start. fog delivers the knowledge of cloud experts to you, helping you to bootstrap your cloud usage and guiding you as your own expertise develops. By coding with fog from the start you avoid vendor lock-in and give yourself more flexibility to provide value. Whether you are writing a library, designing software as a service product or just hacking on the weekend this flexibility is a huge boon. With a rapidly expanding community and codebase the advantages of fog just keep coming. Join us and together we will realize the future of cloud computing.

GraphQL Client is a Ruby library for declaring, composing and executing GraphQL queries. Sample configuration for a GraphQL Client to query from the SWAPI GraphQL Wrapper. If you haven't already, familiarize yourself with the GraphQL query syntax. Queries are declared with the same syntax inside of a <<-'GRAPHQL' heredoc. There isn't any special query builder Ruby DSL. This client library encourages all GraphQL queries to be declared statically and assigned to a Ruby constant. If you're using Ruby on Rails ERB templates, theres a ERB extension that allows static queries to be defined in the template itself. In standard Ruby you can simply assign queries and fragments to constants and they'll be available throughout the app. However, the contents of an ERB template is compiled into a Ruby method, and methods can't assign constants. So a new ERB tag was extended to declare static sections that include a GraphQL query.

Ruby library giving block-buffered and cached read over IO objects with a String-like interface. Ideal to parse big files as Strings, limiting memory consumption.

By including the NamedParameters module into your class/module the 'named_parameters' macro is available. Optional parameters with default values can be as easily defined as mandatory parameters. Your actual method definition does not change at all.

Ruby library grouping various light-weight modules useful for many applications. Currently ships: Logging, Platform, GUI, Misc, Plugins, URLAccess, URLCache. See it as a collection of mini-libraries.

RUBYGAME HAS MOVED. http://rubygame.org

A ruby helper to improve basic class https://gitlab.com/poulet_a/rubyhelper/

try is a lightweight Ruby command-line tool for managing short-lived experiment directories. It is built for developers who constantly create quick tests, prototypes, proof-of-concepts, and late-night coding experiments that usually get lost across temporary folders. The tool gives every experiment a dated home, then makes it easy to find and reopen past work with fuzzy search. It favors simplicity, using a one-file Ruby script with no dependencies and very little setup. Smart sorting brings recently used experiments to the top, which helps users jump back into active ideas without remembering exact folder names. It is ideal for developers who want a low-friction workspace system for creative technical exploration without turning every experiment into a full project.

Elaborate Visual Studio .vcxproj / .vcproj projects to CMakeLists.txt converter, enabling Makefile or Ninja or IDE builds, i.e. full multi-platform CMake functionality (Linux, Mac, Windows...). Live Update capability: supports side-by-side tracking of evolving original proj files, within build tree!! Script hooks for static CMake defs, powerful definition-to-variable mapping. Access to project data content is via git repository _only_ (it's a developer infrastructure project, thus alternatives are less suitable). Be aware of several branches available for checkout (git branch -a): "experimental_unverified" is for the daring (to start with current most featureful code), while usability of "experimental" always gets hardened via a large build. For instructions see README.txt - for ad-hoc access see Browse Code button (experimental_unverified head) -, then attempt guided installation on a .vc[x]proj-based source tree, via install_me_fully_guided.rb . Devel cooperation welcome!!

will_paginate is a pagination library that integrates with Ruby on Rails, Sinatra, Hanami::View, Merb, DataMapper and Sequel. See installation instructions on the wiki for more info. A Sinatra app needs a couple of extra requires. For Padrino apps you need to manually register the Sinatra extension. Alternatively, you can avoid manual will_paginate install by using Padrino recipes. will_paginate 3.0+ will not work on Rails 2. In an older version of Rails, you'll have to use will_paginate 2.3. For Rails 2.0 or older, a simple require will suffice.