Description
This module will allow you to, when combined with fancy WYSIWYG functionality, produce a PDF that looks nice and also looks more or less like what you typed in your editor. You'll be able use this for press releases or official communication with letterhead or attractive looking bleeds after you configure the assets you want to use as headers and footers.
This originated as a really quick, dirty, no-budget "see if it's possible" feature for a client, but really seems like it would be a decent full module.
Why this doesn't duplicate Print:
Closest existing module I could find was Print. Print will totally transform your content into a PDF, too. Sort of. It will, at least, put your text content into a PDF and format it according to the HTML it contains. Correspondence's focus is creating an attractive PDF communiqué with pictures and tables as well as letterhead or bleeds.
Correspondence also "ships" with a feature that, after you download the dependencies, will install and configure your WYSIWYG editor and text formats with a single click, saving you a bunch of configuration hassle.
Future Work
Going the obvious route and including e-mail functionality will be one of the next steps, right after improving the document archive so that it attaches itself more directly to a node's (or other entity's) revisions.
There are also other things I plan on improving, like being able to adjust your font sizes and getting reliable correlation between editor and the PDF when you do. Due to the way WYSIWYG provides CSS to the editor, this is an annoying feature to implement (but I have an idea).
Get it
- Project page: https://drupal.org/sandbox/stickywes/2012936
- Git: git clone --branch 7.x-1.x git.drupal.org:sandbox/stickywes/2012936.git correspondence (browse at http://drupalcode.org/sandbox/stickywes/2012936.git)
Reviews
Coming soon!
Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://ventral.org/pareview/httpgitdrupalorgsandboxstickywes2012936git
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #2
wwedding commentedIssues reported by the scraper aren't my code; Features do a couple things it doesn't like and the camel caps are a library function.
Comment #3
serm commentedHi,
My manual review:
1. in correspondence.module line 776 variable $l is undefined
2. in correspondence_wysiwyg.css lines 21, 22: unit is measure px is redundant
3. I do not see any reason to use file correspondence_content_type.features.inc
Comment #4
wwedding commentedMade some new issues to address what you've pointed out, serm, thanks!
#2060527: Clean up the TCPDF build function, remove unnecessary bits that originated in example code
#2060511: Remove redundant units in CSS
As far as #3 goes: that is required because correspondence_content_type is a Feature generated by Features and those API calls are necessary to tie into that module.
Comment #5
saemie commentedHi there,
[manual review]
1) user t() in correspondence.module:48 (minus
tags), correspondence.module:306
2) Use check_plain for the filename correspondence.module:361
Comment #6
PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application (see also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #6.0
PA robot commentedI missed a space in my original git clone command.