Following up on my earlier plist posting, I've just put together a gem to read the iPhoto database: http://www.narf-lib.org/2006/01/iphoto2.html Cheers, Patrick
on 2006-01-08 09:20
on 2006-01-09 11:10
I have some code that I'm thinking of releasing into the wild. It is a single 'module' consisting of 4 classes. I was wondering what the preferred method of grouping classes is. Should I wrap them in a module or a class or ...?
on 2006-01-09 12:29
Patrick May <email@example.com> wrote: > http://www.narf-lib.org/2006/01/iphoto2.html fine thanks ! i've done a script reading an entire AdressBook and converting it into xml (following more or less draft-dawson-vcard-xml-dtd-01.dtd) this makes use of RubyAEOSA, iconv and xml/smart. how is difficult to make that a gem ?
on 2006-01-10 08:53
It very much depends on your code, but generally wrapping everything into a module is the prefered way, it keeps namespaces clean and allows for easy mixins... the pickaxe has a nice chapter about why to use modules, you should check it out :) ~~~~manveru Am Montag, 9. Januar 2006 19:08 schrieb Henry Maddocks: