Re: [webkit-dev] CSS3 Paged Media module
2012/3/8, David Hyatt : > That page should be updated. We don't have that architectural flaw any > longer since I re-wrote pagination last year. Please do so! -- Seo Sanghyeon ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] CSS3 Paged Media module
That page should be updated. We don't have that architectural flaw any longer since I re-wrote pagination last year. dave (hy...@apple.com) On Mar 7, 2012, at 8:27 AM, Seo Sanghyeon wrote: > 2012/3/7, Milian Wolff : >> Ping? Could someone be so kind as to answer my questions below? > > As the following page admits, WebKit's printing architecture has > "the big flaw" and in general inferior to Gecko and other engines. > I fear you may have to rework most of WebKit's printing code to do > what you want. > > http://www.webkit.org/projects/printing/ > > -- > Seo Sanghyeon > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] CSS3 Paged Media module
2012/3/7, Milian Wolff : > Ping? Could someone be so kind as to answer my questions below? As the following page admits, WebKit's printing architecture has "the big flaw" and in general inferior to Gecko and other engines. I fear you may have to rework most of WebKit's printing code to do what you want. http://www.webkit.org/projects/printing/ -- Seo Sanghyeon ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] CSS3 Paged Media module
On Wed, Feb 8, 2012 at 4:50 AM, Milian Wolff wrote: > I wonder, has anyone begun working on this? If not, I am willing to give it a > shot. I realize that this is a big task, and it will probably be hard for a > newcomer like me to do properly. Hence take this email also as a cry for help. > Any hints like what to tackle first, would be very welcome. Since nobody answers, it is likely nobody is familiar with this spec. There is no documentation available for WebKit's internals. I suggest you to get started on existing (and easier) printing bugs just to get to know some reviewers interested in the subject. Once you know WebKit's printing better, you'll be able to ask more targeted questions on the mailing list. Cheers, Benjamin ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] CSS3 Paged Media module
On Wednesday 08 February 2012 13:50:54 Milian Wolff wrote: > Hello! Ping? Could someone be so kind as to answer my questions below? Thanks > I am interested in improving WebKits printing capabilities. Especially a way > to define headers and footers would be most welcome. The CSS3 Paged Media > module [1] should allow just that. > > I wonder, has anyone begun working on this? If not, I am willing to give it > a shot. I realize that this is a big task, and it will probably be hard for > a newcomer like me to do properly. Hence take this email also as a cry for > help. Any hints like what to tackle first, would be very welcome. > > Looking at the sources, my current understanding of what needs to be done is > the following: > > 1) implement CSSParser::createMarginAtRule > > this should probably return a CSSMaringAtRule which inherits CSSStyleRule. > Is there any documentation on what else to do? Which existing CSSRule > implementation could I use as a reference? > > 2) handle the MarginAtRules in layouting > > I bet that this will be the hard work ;-) Again, is there any documentation > I should read? Any hints? Are there maybe existing css rules that I can use > as a reference? > > I furthermore wonder whether this can be implemented without too heavy > changes. So far, the PrintContext is rather detached from the actual > layouting mechanism. Especially considering that CSS3 allows different page > sizes based on @page rules, I have a hard time of figuring out how this > could work with the existing API. I fear there are (big?) changes required > here. > > As such, any hints or guidance would be much appreciated. > > 3) unit testing > > I see that there are existing printing unit tests in LayoutTests/printing/ > and reckon that the above needs extensive testing and I'll try to get this > done as well. > > 4) Probably related to 1 & 2, I guess one must also improve support for > @page rules in general. > > Cheers, I appreciate your help. > > [1]: http://www.w3.org/TR/css3-page/ -- Milian Wolff | milian.wo...@kdab.com | Software Engineer KDAB (Deutschland) GmbH&Co KG, a KDAB Group company Tel. Germany +49-30-521325470, Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-independent software solutions signature.asc Description: This is a digitally signed message part. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] CSS3 Paged Media module
Hello! I am interested in improving WebKits printing capabilities. Especially a way to define headers and footers would be most welcome. The CSS3 Paged Media module [1] should allow just that. I wonder, has anyone begun working on this? If not, I am willing to give it a shot. I realize that this is a big task, and it will probably be hard for a newcomer like me to do properly. Hence take this email also as a cry for help. Any hints like what to tackle first, would be very welcome. Looking at the sources, my current understanding of what needs to be done is the following: 1) implement CSSParser::createMarginAtRule this should probably return a CSSMaringAtRule which inherits CSSStyleRule. Is there any documentation on what else to do? Which existing CSSRule implementation could I use as a reference? 2) handle the MarginAtRules in layouting I bet that this will be the hard work ;-) Again, is there any documentation I should read? Any hints? Are there maybe existing css rules that I can use as a reference? I furthermore wonder whether this can be implemented without too heavy changes. So far, the PrintContext is rather detached from the actual layouting mechanism. Especially considering that CSS3 allows different page sizes based on @page rules, I have a hard time of figuring out how this could work with the existing API. I fear there are (big?) changes required here. As such, any hints or guidance would be much appreciated. 3) unit testing I see that there are existing printing unit tests in LayoutTests/printing/ and reckon that the above needs extensive testing and I'll try to get this done as well. 4) Probably related to 1 & 2, I guess one must also improve support for @page rules in general. Cheers, I appreciate your help. [1]: http://www.w3.org/TR/css3-page/ -- Milian Wolff | milian.wo...@kdab.com | Software Engineer KDAB (Deutschland) GmbH&Co KG, a KDAB Group company Tel. Germany +49-30-521325470, Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-independent software solutions signature.asc Description: This is a digitally signed message part. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
