Results for make-quote

A funny toy project that can help you generate a image from someone's quote

Make quotes in error messages consistent.

Duration is a library for manipulating timespans. It can give you readable output for a timespan as well as manipulate the timespan itself. With this it is possible to make "countdowns" or "time passed since" type objects.

This package makes it simple to add callbacks a.k.a. "hooks" to ruby classes

Nicolus is a simple program to make all possible combination out of 2 or more lists of words. == FEATURES/PROBLEMS: * Command line parser * "inverse" generate "aaa 111" and "111 aaa" == SYNOPSIS:

FirePHRuby is a Ruby module for the "FirePHP" Firefox/Firebug extension to make AJAX development easier.

This gem prints out random quotes that will make you design better.

String open classed with AES-256 and RSA encryption and zipping methods for easy, secure, encryption of strings. The string_encryption gem was started with the intention of being compatible with the RSA and AES algorithms used in a javascript library on http://www.pidder.com/pidcrypt . Usage and testing against the pidcrypt library hasn't been done yet, but is scheduled for the future. The intent of this library is to make encryption and decryption of a string as straight forward as capitalizing or reversing is. To encrypt a string: encrypted_secret = "Super Secret Text".encrypt("Super Secret Password") To decrypt a string: decrypted_secret = encrypted_secret.encrypt("Super Secret Password") Branden Giacoletto

== DESCRIPTION: Welcome to the PDF-Labels project. Our aim is to make creating labels programmatically easy in Ruby. This Library builds on top of "PDF::Writer":http://ruby-pdf.rubyforge.org/ and uses the templates from "gLabels":http://glabels.sourceforge.org. What this means is easy, clean Ruby code to create many common label types without measuring the labels yourself! All of this in pure Ruby (we use the XML templates from gLabels, we do NOT have a dependancy on gLabels, nor on Gnome) == FEATURES/PROBLEMS: * Works with all gLabels supported templates for rectangular labels * Does not yet work for CD labels (circles) == SYNOPSIS: p = PDFLabelPage.new("Avery 8160") # label is 2 x 10 #Some examples of adding labels p.add_label() # should add to col 1, row 1 p.add_label(:position => 1) # should add col 1, row 2 p.add_label(:text => "Positoin 15", :position => 15) # should add col 2, row 1 p.add_label(:text => 'No Margin', :position => 5, :use_margin => false) #this doesn't use a margin p.add_label(:position => 9, :text => "X Offset = 4, Y Offset = -6", :offset_x => 4, :offset_y => -6) p.add_label(:text => "Centered", :position => 26, :justification => :center) # should add col 2, row 15 p.add_label(:text => "[Right justified]", :justification => :right, :position => 28)# col 2, row 14, right justified. p.add_label(:position => 29) # should add col 2, row 15 p.add_label(:position => 8, :text => "This was added last and has a BIG font", :font_size => 18)

Wish you could write your Ruby in XML? Has the fact that Ruby is not "enterprise" got you down? Do you feel like your Ruby code could be made to be more "scalable"? Well look no further my friend. You've found the enterprise gem. Once you install this gem, you too can make Rails scale, Ruby faster, your code more attractive, *and* have more XML in your life. I'm sure you're asking yourself, "how can the enterprise gem promise so much?". Well the answer is easy, through the magic of XML! The enterprise gem allows you to write your Ruby code in XML, therefore making your Ruby and Rails code scale. Benefits of writing your code in XML include: * It's easy to read! * It scales! * Cross platform * TRANSFORM! your code using XSLT! * Search your AST with XPath *or* CSS! The enterprise gem even comes with a handy "enterprise" binary to help you start converting your existing *legacy* Ruby code in to scaleable, easy to read XML files. Let's start getting rid of that nasty Ruby code and replacing it with XML today!

== DESCRIPTION: Need makes ruby relative requires just work. Simply need a file with a relative path and the file will always be required correctly, regardless of what file your application is being launched through. Typically, ruby projects would unshift lib onto $PATH or use the File.dirname(__FILE__) trick. Using need means you don't have to worry about either of these. Assume you have two files, one directly in lib and the other in lib/extensions. Let's assume that file_a in lib requires file_b, in lib/extensions. Previously, you would doing some crazy load path unshifting or use the __FILE__ trick to make these requires flexible enough to work when your app is being accessed by rake, through a test suite, or required as a gem. Now, just use need. In file_a: need{"extensions/file_b"} need "extensions/file_b"

This is just a REALLY simple RubyGem that will return a random Mitch Hedberg quote. I decided to do this after taking a course on Ruby - I thought I could force it into being a little more complicated to test some of what I learned.... but this is about as simple as it gets. From a pure OO standpoint, there probably are some issues with this implementation, regardless of how simple it is. The Quote object probably shouldn't handle printing to the screen. But that's how I did it... maybe I'll enhance it that. Maybe make a Printable mix-in that handle outputting in different format?

uh ok so roast beef is some kind of package manager that is for bleeding-edge programs. so basically it does not have its own repositories. instead it just will download source from the upstream repository and will do all the necessary steps to install . you get things that are as fresh as possible. i am talking about really fresh like your eggs and milk. roast beef saves you from having to look up the repository locations for all the stuff you want to build from source. it also abstracts away the differences in build processes. say you want the latest version of such a package as gnu emacs. so you grab the source but you know emacs is a little different from other packages and requires "make bootstrap" in between the configure and make step. with roastbeef all the complexity of such things is hidden from you. and if you have a lot of stuff built from source you can keep them all up to date with a single command. the motivations behind this are made more clear in a blog post: http://technomancy.us/106 == man why you even got to do a thing

No description provided.

No description provided.

No description provided.

No description provided.