Forum: Ruby iphoto parsing

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
62cbb5ca28ce35c820d154f0fa5a0afe?d=identicon&s=25 Patrick May (Guest)
on 2006-01-08 09:20
(Received via mailing list)
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
A57dbd9d858a6995b9ca4110d871a256?d=identicon&s=25 Henry Maddocks (Guest)
on 2006-01-09 11:10
(Received via mailing list)
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 ...?
Fa0d14a176f060c96eef797fa48e6bcc?d=identicon&s=25 unknown (Guest)
on 2006-01-09 12:29
(Received via mailing list)
Patrick May <patrick@hexane.org> 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 ?
86e33dee4a89a8879a26487051c216a8?d=identicon&s=25 Michael Fellinger (Guest)
on 2006-01-10 08:53
(Received via mailing list)
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:
This topic is locked and can not be replied to.