different sized paper
tknospdr - September 26, 2007 - 13:50
| Project: | Table Export |
| Version: | 5.x-1.3-2 |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Description
This mod does almost exactly what I need. Is there a way to modify it so the pages it creates are on tabloid sized paper instead of letter? Tabloid is 11x17 in case you don't know.
Thanks,
David
#1
Sorry, should have specified that this is with the PDF output.
#2
Thats definatly something i can look into the PDF format uses the HTML2PDF library im sure it has some functionality for that ill look into it asap, or if anyone else wants to develop some formats for this module its very easy
#3
I will probably add some more PDF features like orientation aswell as margins and simple things like that soon and add a new feature release :D
#4
great, can't wait!
Thanks,
David
#5
#6
#7
Well that sucks, I was still waiting.
#8
Sorry about that, im welcoming patches &/or maintainers, unfortunately I rarely use this module myself anymore so its hard to keep up with the large feature list I had
#9
Is there still some interest for this feature?
I think I will implement styling options for orientation and format. Anything else?
#10
Find attached a modified export_pdf.module which should replace the 5.x-1.3-2 version if you wish to test it. I can make a patch as well if you want but I prefer to do that at the end.
What has been implemented:
Can anybody test it? (remove the .txt extension)
#11
This module will be undergoing a large overhaul soon ( hopefully ), I will be sure to review/add these additions if applicable.
#12
Ok, thx for your comment.
Apparently, there are issues with the orientation: in Landscape, the full width fill (100%) doesn't work out.
Also the border color is not customizable.
Since you are planning a large overhaul, I'd like to tell you how I use your module: I use it as an engine for just creating pdf and csv files from tables. So, I don't make use of the visibility api (I commented out all the references in the table_export module).
In order to hook into the table_export module, I simply use the following code:
<?php$function = 'export_'.$format.'_export_format';
if (function_exists($function)) {
$args = array();
$args[] = function_which_returns_a_table();
$args[] = function_which_returns_the_filename();
call_user_func_array($function, $args);
}
?>
You may take into account that your module would be more valuable to drupal developers if you don't make it dependent from the visibility API. Thx!
#13
As for using table export as simply an exporter I am not sure how valuable that would be, I think I understand your goal, however I am not sure where the http://drupal.org/project/importexportapi project is at, I will most likely be integrating that module
#14
Ok, perhaps I exaggerated a bit with stating it would be more valuable. Still, it a minor adjustment to not make this module dependent from visibility api.
Anyhow, I interested to see how you plan to integrate with the import/export API. I thought that module is all about node import/export, whereas this module is about table export. So, my immediate thought would be not to integrate these. Of course, you have been developing this module, so you probably know best whether you may share code between all these modules.
Good luck with it.
#15
To be honest I have no clue what the plans are for import/export :) if it is as you mention then it will defiantly not apply to this use