On Sat, Jan 17, 2009 at 10:12 PM, Trans <transfire / gmail.com> wrote:

>  module Prawn
>    module PDF
>      class Document
>
> The extra namespace ensures it can still be used without conflict
> should another lib use the PDF namespace too. And one can do:
>
>  include Prawn
>
> to still use just
>
>  PDF::Document
>
> A 'shortcut' require can also be provided to automatically do the
> including.

Nah, it'd be mighty annoying to nest all my classes that way. I'm fine
with claiming the PDF namespace since I'm the current maintainer of
the Ruby PDF project (PDF::Writer), and one of the principle
developers on Prawn maintains PDF::Reader.

It will be up to other developers to avoid namespace collisions with
us, or alternatively, join forces and become part of the 'pdf' project
for Ruby.

-greg

-- 
Technical Blaag at: http://blog.majesticseacreature.com
 Non-tech stuff at: http://metametta.blogspot.com
"Ruby Best Practices"  Book now in O'Reilly Roughcuts:
http://rubybestpractices.com