• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

contrib/H25-Apr-2009-598300

examples/H25-Apr-2009-3,3671,138

inc/Module/H25-Apr-2009-1,6601,218

lib/PDF/H25-Apr-2009-309,623266,537

t/H25-Apr-2009-646

util/H25-Apr-2009-2522

.shipitH A D25-Apr-2009643 1511

ChangesH A D22-Apr-200953 42

INSTALLH A D16-Nov-20051.6 KiB5133

LICENSEH A D22-Apr-20093.6 KiB8470

MANIFESTH A D25-Apr-200910.6 KiB235234

META.ymlH A D25-Apr-2009513 2726

Makefile.PLH A D22-Apr-2009212 1410

READMEH A D22-Apr-20092.5 KiB5942

TODOH A D16-Nov-20051.8 KiB5848

README

1After much time, effort, and with well received results,
2Alfred Reibenschuh is abandoning PDF::API2.
3see http://tech.groups.yahoo.com/group/perl-text-pdf-modules/message/3615
4
5However we have seen great progress in moving towards paperless methods.
6
7Furthermore the PDF specification is now an ISO standard.
8
9Now is the time to really push forward with the development of an even
10better perl pdf solution.
11
12This is a beginning toward that goal.
13
14This version starts with PDF::API2 0.73, creating a new one of PDF::API3.
15
16There are a growing number of PDF "quick solutions". It is hoped that
17PDF::API3 can coalesce many under one library. There is commonality
18that all "quick solutions" will need: find, open, read, write, parse files.
19
20The intent is to provide a universal library for which other "solutions"
21may utilize for lower level functionality. As such, all PDF::API2 modules
22have been re-named as PDF::API3::Compat::API2.
23
24The intent is that the interface at the API2 level will stay the same.
25
26As the library is refactored, a new API3 interface will be formulated.
27Low level functionality will be factored into PDF::API3::Lib. The
28typical programmer interface will be factored under PDF::API3. The
29typical programmer interface would utilized the lower level routines
30of PDF::API3::Lib.
31
32Other PDF libraries may be incorporated as PDF::API3::Compat::distA,
33PDF::API3::Compat::distB, PDF::API3::Compat::distC, etc. As these are
34refactored to utilize or generalize PDF::API3::Lib, their typical
35programmer interface will move under PDF::API3 if general, or may be
36spun off as PDF::API3x extensions
37
38The intent is to use git and encourage distributed development.
39A git and wiki will be put up soon.
40
41Development philosophy includes development of lots of tests,
42tidy'ing and critic utilities, and utlization of Moose and other
43libraries that will speed development and provide a clean, solid,
44easily maintained, production ready system. And to develop appropriate
45programmer and maintenance documentation. Yes - maintenance of how it
46works and why choices were made so as to ease maintenance of it by others.
47
48The intent of putting this release out is to inform the community of
49the effort, encourage others to participate, and to utilize the bug
50tracking system of CPAN for tracking bugs and new development.
51
52Consider this pre-alpha software.
53
54Thanks Martin Hosken for Text::PDF from which PDF::API2 was developed.
55Thanks Alfred Reibenschuh for PDF::API2 for taking it to the next level.
56
57Otto Hirr
58Apr 2009
59