[webkit-dev] Do any ports still disable SVG?

2013-01-25 Thread Eric Seidel
This question came up in:
https://bugs.webkit.org/show_bug.cgi?id=92393

Do any ports still disable SVG?  Should we be removing the ENABLE_SVG
defines (and potentially unifying SVG and HTML style resolve more
closely)?
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Do any ports still disable SVG?

2013-01-25 Thread Jochen Eisinger
Many chromium developers disable svg for faster building.

Jochen
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Do any ports still disable SVG?

2013-01-25 Thread Antonio Gomes
QtWebKit has a --minimal option where SVG is disabled IIRC.

On Fri, Jan 25, 2013 at 2:27 PM, Jochen Eisinger joc...@chromium.org wrote:
 Many chromium developers disable svg for faster building.

 Jochen


 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Do any ports still disable SVG?

2013-01-25 Thread Arunprasad Rajkumar
Eric, Most of the resource constraint environments(embedded systems) still
disables the SVG. If the define is removed code size of WebKit will be
increased by atleast 3 to 4M.

On 26 January 2013 01:01, webkit-dev-requ...@lists.webkit.org wrote:

 This question came up in:https://bugs.webkit.org/show_bug.cgi?id=92393

 Do any ports still disable SVG?  Should we be removing the ENABLE_SVG
 defines (and potentially unifying SVG and HTML style resolve more
 closely)?

 --
*Arunprasad Rajkumar*
http://in.linkedin.com/in/ararunprasad
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Do any ports still disable SVG?

2013-01-25 Thread Elliott Sprehn
Perhaps the time to remove ENABLE_SVG is in several years once many pages
depend on it and disabling it results in a busted browser...


On Fri, Jan 25, 2013 at 2:55 PM, Arunprasad Rajkumar ararunpra...@gmail.com
 wrote:

 Eric, Most of the resource constraint environments(embedded systems) still
 disables the SVG. If the define is removed code size of WebKit will be
 increased by atleast 3 to 4M.


 On 26 January 2013 01:01, webkit-dev-requ...@lists.webkit.org wrote:

 This question came up in:https://bugs.webkit.org/show_bug.cgi?id=92393

 Do any ports still disable SVG?  Should we be removing the ENABLE_SVG
 defines (and potentially unifying SVG and HTML style resolve more
 closely)?

 --
 *Arunprasad Rajkumar*
 http://in.linkedin.com/in/ararunprasad

 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo/webkit-dev


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Do any ports still disable SVG?

2013-01-25 Thread Philip Rogers
We could reduce a bit of maintenance cost by removing all the defines. I
ran some numbers and I'm not sure we are there yet in terms of lost
productivity, even on the Chromium side. SVG adds around 20% to debug
compile times:

Linux, Z620, no goma, clean build, ninja, Debug DumpRenderTree, without
SVG: 4m05s
Linux, Z620, no goma, clean build, ninja, Debug DumpRenderTree, with SVG:
4m52s

Linux, Z620, no goma, clean build, ninja, Release DumpRenderTree, without
SVG: 3m58s
Linux, Z620, no goma, clean build, ninja, Release DumpRenderTree, with SVG:
4m36s

For Chromium developers not working on WebKit it is probably best to
continue building without SVG, even though I must warn you that you'll miss
out on the some sweet graphics.

Philip


On Fri, Jan 25, 2013 at 12:19 PM, Elliott Sprehn espr...@chromium.orgwrote:

 Perhaps the time to remove ENABLE_SVG is in several years once many pages
 depend on it and disabling it results in a busted browser...


 On Fri, Jan 25, 2013 at 2:55 PM, Arunprasad Rajkumar 
 ararunpra...@gmail.com wrote:

 Eric, Most of the resource constraint environments(embedded systems)
 still disables the SVG. If the define is removed code size of WebKit will
 be increased by atleast 3 to 4M.


 On 26 January 2013 01:01, webkit-dev-requ...@lists.webkit.org wrote:

 This question came up in:https://bugs.webkit.org/show_bug.cgi?id=92393

 Do any ports still disable SVG?  Should we be removing the ENABLE_SVG
 defines (and potentially unifying SVG and HTML style resolve more
 closely)?

 --
 *Arunprasad Rajkumar*
 http://in.linkedin.com/in/ararunprasad

 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo/webkit-dev



 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo/webkit-dev


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Do any ports still disable SVG?

2013-01-25 Thread Arunprasad Rajkumar
I agree with you guys. Most of the sites now uses SVG. But I'm worrying
about the resource constraint platforms where browser is not intended for
open Internet browsing, rather it is used for building user interfaces(like
navigation systems, tv, set-top-box). Though using SVG in the constraints
environments increases the productivity, but most of the platforms still
lacks OpenGL ES2 or OpenVG  survives only with 2D accelerators!!. As far I
know most of the pages still uses SVG to show only very basic graphics
elements like buttons,... and it may be lack of proper tools to author svg
documents.

On 26 January 2013 03:47, Philip Rogers p...@google.com wrote:

 We could reduce a bit of maintenance cost by removing all the defines. I
 ran some numbers and I'm not sure we are there yet in terms of lost
 productivity, even on the Chromium side. SVG adds around 20% to debug
 compile times:

 Linux, Z620, no goma, clean build, ninja, Debug DumpRenderTree, without
 SVG: 4m05s
 Linux, Z620, no goma, clean build, ninja, Debug DumpRenderTree, with SVG:
 4m52s

  Linux, Z620, no goma, clean build, ninja, Release DumpRenderTree,
 without SVG: 3m58s
 Linux, Z620, no goma, clean build, ninja, Release DumpRenderTree, with
 SVG: 4m36s

  For Chromium developers not working on WebKit it is probably best to
 continue building without SVG, even though I must warn you that you'll miss
 out on the some sweet graphics.

 PhilipI agree with you guys



 On Fri, Jan 25, 2013 at 12:19 PM, Elliott Sprehn espr...@chromium.orgwrote:

 Perhaps the time to remove ENABLE_SVG is in several years once many pages
 depend on it and disabling it results in a busted browser...


 On Fri, Jan 25, 2013 at 2:55 PM, Arunprasad Rajkumar 
 ararunpra...@gmail.com wrote:

 Eric, Most of the resource constraint environments(embedded systems)
 still disables the SVG. If the define is removed code size of WebKit will
 be increased by atleast 3 to 4M.


 On 26 January 2013 01:01, webkit-dev-requ...@lists.webkit.org wrote:

 This question came up in:https://bugs.webkit.org/show_bug.cgi?id=92393

 Do any ports still disable SVG?  Should we be removing the ENABLE_SVG
 defines (and potentially unifying SVG and HTML style resolve more
 closely)?

 --
 *Arunprasad Rajkumar*
 http://in.linkedin.com/in/ararunprasad

 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo/webkit-dev



 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo/webkit-dev





-- 
*Arunprasad Rajkumar*
http://in.linkedin.com/in/ararunprasad
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev