Ah... OK - if there are people that can get by with only the core and w/o PdfDocument - then fine.
-----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Monday, October 18, 2010 5:13 PM To: Leonard Rosenthol Cc: [email protected] Subject: Re: [Podofo-users] PoDoFo Architecture Changes Hi, At first I was thinking the same, but PdfDocument has to many responsibilities right now. For example, it creates fonts, forms and pages. Pages create annotations and actions. Moving PdfDocument to the base part would require serious refactoring to remove these references. Regards, Dom Am Monday 18 October 2010 schrieb Leonard Rosenthol: > I would think that PdfDocument (for managing pages and such) should be > part of the core as well. Clearly painter and annots can be split out... > > Leonard > > -----Original Message----- > From: Dominik Seichter [mailto:[email protected]] > Sent: Monday, October 18, 2010 1:20 PM > To: [email protected] > Subject: [Podofo-users] PoDoFo Architecture Changes > > Hi Guys, > > I would like to discuss some changes I made today in a separate branch [0]. > My change today splits PoDoFo into two libraries: > * podofo-base - which contains all the basic datatypes and low level > parsing infrastructure * podofo-doc - high level features such as > PdfDocument, PdfPainter or PdfAnnotation > > This change has in my opinion several advantages: > - If you only need basic features (e.g. Scribus for Adobe Illustrator > files import), you can just link to podofo-base - Smaller dependencies > sets, please see the attached PNG for an overview of dependencies. > PoDoFo-base does only depend on zlib and libjpeg for compression > filters. - Easier maintanence, as we have a cleaner structure inside > of the project and two libraries which can be tested independently. I > will split up the unit tests project later. - No changes for external > projects, just include <podofo.h> and everything will be the same for > you. You only link to libpodofo-doc instead of libpodofo. > > I would suggest the following release plan: > - Do one more release of PoDoFo 0.8.x from current trunk > - After the release, merge the changes from the branch into trunk and > continue development of PoDoFo 0.9.x with the new structure. > > What do you think of the new structure? Do these changes cause > problems for anyone of you, who is using PoDoFo? Do you have > suggestions on how the structure can be further improved? > > Best regards, > Dom > > [0] > https://[email protected]/svnroot/podofo/podofo/b > ranch > es/_dev/architecture_cleanup -- > Dominik Seichter - [email protected] - > http://domseichter.blogspot.com KRename - http://www.krename.net - > Powerful batch renamer for KDE KBarcode - http://www.kbarcode.net - > Barcode and label printing PoDoFo - http://podofo.sf.net - PDF > generation and parsing library -- Dominik Seichter - [email protected] - http://domseichter.blogspot.com KRename - http://www.krename.net - Powerful batch renamer for KDE KBarcode - http://www.kbarcode.net - Barcode and label printing PoDoFo - http://podofo.sf.net - PDF generation and parsing library ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ Podofo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/podofo-users
