README in rbcdio-0.01 vs README in rbcdio-0.02

- old
+ new

@@ -11,15 +11,15 @@ control. Ruby programs wishing to be oblivious of the OS- and device-dependent properties of a CD-ROM can use this library. == Requirements -I've only tested rcdio on Ruby 1.8.4. +I've only tested rcdio on Ruby 1.8.4 - 1.8.6 You'll need a C compiler so the extension can be compiled when it is -installed. You'll also need libcdio (http://libcdio.sf.net) and it's -header files installed. +installed. You'll also need libcdio +(http://www.gnu.org/software/libcdio) and it's header files installed. One weirdness I've seen in running "gem install" is that on some OS's like Solaris, gem assume the GNU "install" program goes by the name "ginstall". (I've read a report that on cygwin this was the case too: http://www.cygwin.com/ml/cygwin/2005-10/msg00259.html ) @@ -28,21 +28,21 @@ libcdio is rather large and yet may still grow a bit. (UDF support in libcdio may be on the horizon.) What is in rubycdio is incomplete; over time it may grow to completion -depending on various factors: e.g. interest, whether others help out, -whether I get a longer-term job at some such place that uses Ruby. +depending on various factors: e.g. interest, whether others help out. Sections of libcdio that are currently missing are the (SCSI) MMC commands, the cdparanoia library, CD-Text handling. Of the audio controls, I put in those things that didn't require any thought. The ISO 9660 library is pretty complete, except file "stat" information which is at present is pretty minimal. -That said, what's in there is very usable (It contains probably more -access capabilities than what most media players that don't use +That said, what's in there is very usable. It contains probably more +access capabilities than what most media players that don't issue MMC +directly need. The encapsulation by SWIG is done in two parts. The lower-level Ruby interface is called rubycdio and is generated by SWIG. The more object-oriented module is cdio; it is a Ruby class that uses @@ -64,12 +64,13 @@ having to redo the underlying translation. (But the reverse is generally not true: usually changes to the C-to-python translation, rubycdio, do result in small, but obvious and straightforward changes to the abstraction layer cdio.) -There is much to be done - you want to help out, please do so! +There is much to be done - if you see something missing and want to +help out, please do so! Standalone documentation is missing although many of the methods, classes and functions have some document strings. See also the programs in the example directory. -$Id: README,v 1.5 2006/12/21 11:55:23 rocky Exp $ +$Id: README,v 1.8 2007/10/13 17:11:45 rocky Exp $