Clio is a great way to build commandline tools. It provides an advanced
options parser with a variety of notations suited to almost any perfered
style, and provides a very rich and and easy to use library for
generating console output.
ok bernd@
Trollop is YAFCLAP --- yet another fine commandline argument processing
library for Ruby. Trollop is designed to provide the maximal amount of
GNU-style argument processing in the minimum number of lines of code
(for you, the programmer).
ok bernd@
Ruby Facets is a collection of general purpose, pure-Ruby extensions
and additions for the Ruby programming language. Facets is divided into
two libraries, one for the extensions and the other for the additions.
called Facets/CORE and Facets/MORE, respectively.
Facets/CORE is a large collection of methods which extend the core
capabilities of Ruby's built-in classes and modules. This collection of
extension methods are unique by virtue of their atomicity. The methods
are stored individually so that each can be required independently.
This gives developers fine-grain control over which extra methods to bring
into his or her code. The collection currently contains over 400 methods
spanning 28 classes and modules. It is an atomic library in that the
methods are packaged individually so that each can be required
independently. This gives the programmer greater control to
include only the extra methods he or she actually needs.
Facets/MORE are a collection of classes, modules and light frameworks
whcih cons itutes an ever growing and improving source of reusable
components. Some very nice additions are provided, from an amazing SI
Units system to an elegant Annotations system. And of course there are
all the more typical goodies like Tuple, Functor and Multiton.
ok bernd@
> PyBugz is a python and command line interface to Bugzilla, allowing
> the user to quickly search, extract attachments and close bugs all
> from the comfort of the command line.
much feedback and improvement from giovanni@
There are probably other bad bugs in there, this code is a textbook example
of how NOT to write code if you want it to work.
Between the gnu style that obfuscate the stuff, the various thingies added
"just in case", the misuse of autoconf results, and the really high
abstraction level together with long functions and internal concepts, how
can anyone make sense of this code ? (short answer: it doesn't make actual
sense).
Also, no cookies for the gnu guys who, along with an important bug-fix,
manage *again* to push out 10000+ lines of useless diff thanks to a change
in automake/autoconf itself.
We don't need to make fun of Windows and its security, the GNU project
manages to produce as many problems on its own...
When will they learn secure practices ? I would bet "not this century",
but then I probably won't be around to collect the bet...
While Moose attributes provide you with a way to name your accessors,
readers, writers, clearers and predicates, this library provides
commonly used attribute helper methods for more specific types of data.
ok sthen@
A logging role building a very lightweight wrapper to Log::Log4perl for
use with your Moose classes. For compatibility the logger attribute can
be accessed to use a common interface for application logging.
ok jasper@ and kevlo@
- fix HOMEPAGE
- change license to MIT (since 1.11.0)
- add regression tests (by sthen@)
- take maintainership
- minor cleanups
ok sthen@ and ok jasper@ (for a previous diff)
