[ANN] Ribs 0.0.1

Ruby JRuby
1

I am extremely pleased to announce the first release of Ribs.

Ribs is a library for JRuby, that allows you to persist Ruby objects
using Hibernate. Some time ago I wrote about ActiveHibernate. I have now
decided to implement this myself, and the result is the Ribs project.

The first release is quite minimal in scope. You can define and work
with models that have primitive values only - there is no support for
associations. You can find, create, update and delete model objects. All
of this uses Hibernate and JDBC.

To get started, you just define that an object is to be a Ribs model:

class Artist
Ribs!
end

Once that’s done, you can start working with it.

Of course, this is just the beginning. I have a quite long list of
things I’d like to have in the project, but I felt the need to release
quickly and often to be more important than to implement everything
first.

This release is not really for production usage, but I would appreciate
if people tried it out and came with suggestions. The current planned
features can be found in the PLAN file, in the git repository.

More documentation can be found here:
http://olabini.com/projects/ribs/doc.
You can download the gem at:
http://olabini.com/projects/ribs/downloads/ribs-0.0.1.gem.
The git repository is at: git://github.com/olabini/ribs.git.

Ribs will soon be available in the regular gem repositories - as soon as
my Rubyforge project has been approved.

The project is released under the MIT license.

Cheers

–
Ola B. (http://olabini.com)
JRuby Core Developer
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)

“Yields falsehood when quined” yields falsehood when quined.

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
2

So is this project intended to work with a rails project seamlessly or
as an alternative to activerecord? Btw your activehibernate, is that
still an active project I remember the last time I looked at it not a
whole lot of chatter was going on about it

~Matt

On Sat, Aug 30, 2008 at 1:57 PM, Ola B. [email protected] wrote:

often to be more important than to implement everything first.
Ribs will soon be available in the regular gem repositories - as soon as my

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
3

Matthew C. wrote:

So is this project intended to work with a rails project seamlessly or
as an alternative to activerecord? Btw your activehibernate, is that
still an active project I remember the last time I looked at it not a
whole lot of chatter was going on about it

~Matt

Hi,

Yeah, the idea is that you should be able to use it in or outside Rails.
I haven’t tried it yet, though.

ActiveHibernate seems to have petered off a bit, and I decided to start
work from a new code base, but yeah, the goals are similar. I hope to
get Ribs in a more finished state quicker.

Cheers

–
Ola B. (http://olabini.com)
JRuby Core Developer
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)

“Yields falsehood when quined” yields falsehood when quined.

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
4

On Sat, Aug 30, 2008 at 7:52 PM, Ola B. [email protected] wrote:

To get started, you just define that an object is to be a Ribs model:

class Artist
Ribs!
end

Once that’s done, you can start working with it.

Personally, I’d favor a more DataMapper-like approach, like this:

class Artist
include Ribs:Resource
property :name, :string, :primary_key
end

IMHO, it’s not really interesting to use block syntax to define your
properties.

Of course, this is just the beginning. I have a quite long list of things
I’d like to have in the project, but I felt the need to release quickly and
often to be more important than to implement everything first.

This release is not really for production usage, but I would appreciate if
people tried it out and came with suggestions. The current planned features
can be found in the PLAN file, in the git repository.

I assume you also intend to handle lazy loading. Some kind of
automigration
feature would be nice too… At any rate, this looks like a very
promising
project for the JRuby crowd.

Cheers,

Emm