TODO

TODO

Daemon Kit aims to simplify creating Ruby daemons by providing a sound application skeleton (through a generator), task specific generators (jabber bot, etc) and robust environment management code. Using simple built-in generators it is easy to created evented and non-evented daemons that perform a multitude of different tasks. Supported generators: * XMPP bot (non-evented) * AMQP consumer (evented) * Nanite agent * Cron-style daemon * ruote remote participants

Adhearsion is an open-source telephony development framework. This is a fork to add CallWeaver compatibility.

Lepidoptera is a simple and easy to extend code generator for common every day projects.

Choose the license and generate required documents

gem oficial para suporte a deploy de aplicações

A framework to assist in the migration of data from legacy databases.

Adhearsion is an open-source telephony development framework (with minor mods)

Our default app template

Generate Swiss DTA payment files to extract payments from your existing application

Picolena is a lightweight ferret-powered documents search engine written in Ruby on rails

Generates a basic skeleton for a Mirah Android application

QA Robusta is an automation framework easing pain points away from automation test case writers. How is pain relieved? * Elements, such as links, buttons, and other html objects are defined in one location. This ensures over time the user won't have definitions spread out throughout different layers of code requiring time consuming updates if the application under test is modified. * Well defined flows allows the user to have a common means for navigating and controlling interactions with the application under test. This takes all logic out of test classes and yields in higher more modular code re-use. * When an application requiring testing has the elements and flows implemented less code savy resources can easily add new test cases once trained on how to access the flows and elements. * When ever a link or button is clicked a screen shot is taken * Results are available under site/results directory in html format. Report includes the rdoc on a per test class method along with any screen shots taken. Example report: https://cyberconnect.biz/opensource/demo_results.html * Transparent remote Unix command execution leading to well defined interfaces for common task. For example, one may have a class defined specifically for RemoteUnixNetwork. This class would have methods such as, assign_ip, ifup, ifdown, etc. This class then would be able to perform these task on any remote Unix machine. * Executes the same on Windows or Linux/Unix environments. Developers have the freedom to develop on the platform of choice. * Mechanize extension: Allows the user to define a web application's page elements in a YAML format and provide navigation paths accessing the YAML structure to interact with the web application. Users can also perform direct http.post or any other mechanize functionality when defining state-full interfaces to hit a web application without going through a browser.

Daemon Kit aims to simplify creating Ruby daemons by providing a sound application skeleton (through a generator), task specific generators (jabber bot, etc) and robust environment management code. Using simple built-in generators it is easy to created evented and non-evented daemons that perform a multitude of different tasks. Supported generators: * XMPP bot (non-evented) * AMQP consumer (evented) * Nanite agent * Cron-style daemon * ruote remote participants

Reactive is a desktop application framework that gives everything needed to create database-backed applications according to the Model-View-Control pattern of separation. Reactive is highly inspired and also uses code of Rails, the famous Web-Framework for ruby. In Reactive, the model is handled by what's called an object-relational mapping layer. Reactive doesn't impose any ORM, you may choose the one you like but Reactive defaults to Active Record. This means it has baked in support for it, without forcing you to use it. The view part is independant of Reactive, this means that the application has to choose a view provider and feed it into Reactive. This leads to complete freedom for the GUI part. View providers are packaged as gems, so that it is easy for the developer to choose and install them. Look for reactive_view_* to discover some view providers (at this early alpha stage, only reactive_view_wx is available) The controller is part of Reactive and is loosely coupled to the view. Simple convention set up the link.

Development tools for reactive applications

Adhearsion is an open-source telephony development framework

RestfulX: The RESTful Way to develop Adobe Flex and AIR applications

A Multi-User Console Interactive Development Environment Based On GNUScreen