On Jan 17, 9:13 ¨Âí¬ ÇòåçïòÂòï÷¼çòåçïòù®ô®âò®®®Àçíáéì®ãïí÷òïôåº
> On Sat, Jan 17, 2009 at 9:00 PM, Stefan Lang
>
> <perfectly.normal.hac... / gmail.com> wrote:
> > 2009/1/18 Gregory Brown <gregory.t.br... / gmail.com>:
> >> I'm getting very few requests for features to add to Prawn that exist
> >> in PDF::Writer but not in Prawn.
> >> Because it directly effects each and every user, I need to know what
> >> this means.  ¨Âìåáóòåíåíâåò ôèáô éîôåîä ôï ªÅÎÄ ÁÌÓÕÐÐÏÒÆÏ> >> PDF::WRITER* after Prawn becomes PDF::Document, so long as there is a
> >> sufficient mandate from the community.
>
> > Why rename it? Prawn is a nice name, while PDF::Document seems to
> > imply that there are other closely related PDF::* modules.
>
> There are :)
>
> We've got PDF::Inspector and PDF::Reader.  ¨Âïô÷èéãáòôåîôáôéöåì> planned to become part of the 'pdf' project.
>
> http://rubyforge.org/projects/pdf
>
> gem install pdf would get you all of them.
> Note that I'll likely turn Prawn into PDF::Document by something
> simple like this in the pdf gem:
>
> module PDF; end
> Prawn = PDF;
> require "prawn"
>
> Or something silly like that, at first. (Just off the top of my head,
> I'm not sure the above actually works)
>
> It may be possible to just keep Prawn as Prawn, but we'll see how it goes.

  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.

T.