From: George Moschovitis <george.moschovitis@...>
Date: 2005-02-15T20:39:59+09:00
Subject: Re: [ANN] Nitro + Og 0.10.0

Hello Michael,

> Wow. That's very good news. That makes database examples much easier, as 
> everyone will be able to try them without installing and configuring 
 > ...
> installing the SQLite3 dependencies.

Yeap, sqlite3 is cool indeed, and Jamis's library is even better.

Please note that you need the (as-of-yet) unreleased version 1.1.0 of 
Sqlite3-Ruby. Jamis Buck was kind enough to make some small changes to 
the library to better support Og but havent released the new version yet.

I also run some tests with prepared statements in Og/Sqlite but is not
ready yet.

>> * --console option attaches an irb session to a running instace of an
>> application (works again).
>
> Could you explain how this works and how this can be useful (I'm sure it 
> *is* useful, but I don't know exactly what it is ;-).

well lets say you are running your site with this command:

$ ruby path/to/mysite/run.rb --lhttpd

(using the lighttpd/fastcgi adapter)

then you want to debug the site or interrogate some internal structures. 
You just issue:

$ ruby path/to/mysite/run.rb --console

and you end up in a irb console with the correct environment of the 
running site. This will be more usefull in the next releas when I 
re-enable the distributed sessions (drb/memcache).

This works more or less like the Rails version.

>> * Og supports optional typechecking by using property metadata.
> 
> Can you give a little example?

sure, first of all, enable typechecking:

Property.type_checking = true

then define your class:

class Article
	prop_accessor :name, String
end

the try to violate tha prop_accessor type:

a = Article.new
a.name = 123	# => You get an exception!

useful to catch some bugs.

btw, this is NOT an restricted to Og application, this is not
an Og feature.



regards,
George