[Seaside] Re: WAComponent to PDF
pdebruic at gmail.com
Tue Oct 27 23:04:33 UTC 2015
The options are described here:
Paul DeBruicker wrote
> Hi Hliaire,
> wkhtmltopdf has the --footer-url and --header-url options if you don't
> want to create a complete document and instead just want to render a
> Then you can save the component to a HTML file and have wkhtmltopdf
> prepend the header and append the footer to your content before doing the
> Since the header/footer likely change infrequently vs the content it may
> be an easier way to go.
> Hope this helps,
> HilaireFernandes wrote
>> Le 22/10/2015 18:38, Otto Behrens a écrit :
>>> (WAHtmlCanvas builder fullDocument: true)
>>> rootBlock: [ :root |
>>> root context visitor: (WARenderingGuide client: root context visitor).
>>> root title: 'Form'.
>>> root meta contentType: (WAMimeType textHtml charset: 'utf-8').
>>> root stylesheet url: self stylesheetFileFullPath.
>>> self addAdditionalBookmarksForRowsToRootIfNecessary: root ];
>>> Let me know if you need more.
>> Hi Otto,
>> As the generated html file is read locally I get issue with the css path.
>> It renders the path to the style file as /files/MyFileLibrary/style.css
>> but it should look like http://myHost/pathToCss/style.css when you want
>> to read the html file locally.
>> The absolute path to style.css is purely constructed by Seaside, adding
>> the host part does not make a valid url:
>> http://myHost/files/MyFileLibrary/style.css is not valid.
>> How did you manage it? Are you serving your static files with Apache? I
>> am not there yet and would like to find a pure Seaside solution. Is
>> there a way to have a valid url, to a resource, with the http part in?
>> So far I did not find it, but Seaside is so big.
>> Dr. Geo
>> seaside mailing list
>> seaside at .squeakfoundation
View this message in context: http://forum.world.st/WAComponent-to-PDF-tp4857328p4858275.html
Sent from the Seaside General mailing list archive at Nabble.com.
More information about the seaside