Considering dropping support for prawn-format

[Gregory Brown]

Hi folks,

I'm wrestling with a tough decision here, and my guess is it'll be an
unpopular one.
I think I might drop support for prawn-format starting with Prawn 0.7.

It's very confusing to tell people, yes, use this extension officially
included with Prawn, but no, text_box won't work right, chinese
wrapped text won't work right, column_box won't work right, tables
won't work right, etc.

So I think a reasonable solution is to drop support for it until these
issues are fixed.  What prawn-format really needs is a maintainer who
will sit down, read through it, understand its issues, and then fix
them.
Right now it's a major hindrance on our 1.0 path to deal with a giant
block of complex code none of us currently understand.

If we see patches beating down the door with specs and fixes before
0.7, I'll reconsider.  Otherwise, I'm going to have to pull the plug
until someone comes along and resuscitates it.



--
BOOK: http://rubybestpractices.com
TECH: http://blog.majesticseacreature.com
NON-TECH: http://metametta.blogspot.com

[Chris Schumann]

On Sat, Nov 21, 2009 at 9:41 AM, Gregory Brown
<gregory...@gmail.com> wrote:
> I think I might drop support for prawn-format starting with Prawn 0.7.

and

> What prawn-format really needs is a maintainer who will sit down,
> read through it, understand its issues, and then fix them.

I think that's a very reasonable approach: It's better than including
broken code, better than taking your time from more important
features, and better than slapping bandaids on it to make it run.

A project manager makes the tough calls for the good of the project,
and the team. Thank you for doing this job along with your work on the
code itself.

Chris