Chris Dumez | 19 Nov 21:20 2014
Picon

size_t vs unsigned in WTF::Vector API ?

Hi all,

I recently started updating the WTF::Vector API to use unsigned types instead of size_t [1][2], because:
- WTF::Vector is already using unsigned type for size/capacity internally to save memory on 64-bit, causing a mismatch between the API and the internal representation [3]
- Some reviewers have asked me to use unsigned for loop counters iterating over vectors (which looks unsafe as the Vector API, e.g. size(), returns a size_t).
- I heard from Joseph that this type mismatch is forcing us (and other projects using WTF) to disable some build time warnings
- The few people I talked to before making that change said we should do it

However, Alexey recently raised concerns about this change. it doesn't "strike him as the right direction. 4Gb is not much, and we should have more of WebKit work with the right data types, not less.”.
I did not initially realize that this change was controversial, but now that it seems it is, I thought I would raise the question on webkit-dev to see what people think about this.

Kr,

_______________________________________________
webkit-dev mailing list
webkit-dev <at> lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
Osztrogonác Csaba | 17 Nov 17:16 2014
Picon

Status of WinCairo buildbot?

Hi,

it seems the WinCairo buildbot is offline since a months:
https://build.webkit.org/builders/WinCairo%20Release?numbuilds=200

And it had been continuosly red before it went offline,
at least since 1st October.

Is there anybody maintains / interested in maintaining this bot?
If no, I propose removing it from https://build.webkit.org/ .

br,
Ossy
Zoltan Herczeg | 13 Nov 08:12 2014

Announcing the TyGL-WebKit port to accelerate 2D web rendering with GPU

Hi All,

We are proud to announce the TyGL port (link:
http://github.com/szeged/TyGL) on the top of EFL-WebKit. TyGL (pronounced
as tigel) is part of WebKit and provides 2D-accelerated GPU rendering on
embedded systems. The engine is purely GPU based. It has been developed on
and tested against ARM-Mali GPU, but it is designed to work on any GPU
conforming to OpenGL ES 2.0 or higher.

The GPU involvement on future graphics is inevitable considering the pixel
growth rate of displays, but harnessing the GPU power requires a different
approach than CPU-based optimizations. 2D graphics is traditionally
software-based however, and 2D APIs are interfaces to these CPU-based
algorithms. WebKit GraphicsContext API is no different, so the key
challenge of our project was and is producing the expected output in a GPU
friendly way.

Key features:

Batching pipeline:

GPU provides the highest performance when a large number of triangles are
drawn with a single draw command without any OpenGL state changes. The
GraphicsContext API in WebKit provides draw operations for single shapes
however, which can result frequent state changes if implemented naively.
TyGL was designed to group these commands to reduce the number of draw
calls.

Automatic shader generator:

TyGL can generate complex shaders from multiple shader fragments, which
allows efficient batching but it also takes care to make them fit into the
shader cache of the GPU.

Trapezoid based path rendering:

TyGL uses trapezoid-based tesselation of shapes and the GPU renders them
with high anti-aliasing quality. We are continuously improving this part
of the engine and look forward to make use of new GPU capabilities (like
Pixel Local Storage) to squeeze more performance out of it.

No software fallback:

The whole engine is optimized for GPU without legacy software fallback.
Hence we don't need to sacrifice optimizations for compatibility. There
are enough software based 2D libraries which can be used when GPU is not
available.

TyGL is already capable of rendering many web-sites correctly, but some
features have not been implemented yet. We continue this work and we are
open to contributions from the community. Contact to us if you want more
information about the project.

Regards,
U-Szeged's web browser team.
youenn fablet | 10 Nov 11:28 2014
Picon

Networking process scope

Hi,

I looked at the Networking process recently and am wondering what is
in scope/out of scope of this process.

Currently, the networking process is used to load resources from:
- URLs resolved using platform specific libraries (CF, libsoup...),
including data URLs
- Blob URLs
The networking process is not used for (at least):
- appcache resources URLs
- archive resources URLs

Two options come to mind:
1. Use networking process for all URLs that require actual networking.
That would mean moving data & blob URL handling within WebProcess,
probably unifying this loading with appcache/archive resource loading.
2. Use networking process for all URLs. That would mean moving
appcache/archive resource loading into Networking process at some
point.

Any thoughts?

Regards,
   Youenn
Darin Adler | 9 Nov 01:27 2014
Picon

GTK EWS bot failing to build (gtkdoc-mkdb can’t find WebKitDOMCustomUnstable.h)

Hi folks.

The GTK EWS bot is failing to build, with this error:

> Can't open
/home/rego/checkout/WebKit/WebKitBuild/Release/DerivedSources/webkitdom/WebKitDOMCustomUnstable.h:
No such file or directory at
/home/rego/checkout/WebKit/WebKitBuild/DependenciesGTK/Root/bin/gtkdoc-mkdb line 3889.
> 
> Generating webkitdomgtk documentation...
> Traceback (most recent call last):
>   File "/home/rego/checkout/WebKit/Tools/gtk/generate-gtkdoc", line 201, in <module>
>     generate_documentation_for_config(common.build_path('gtkdoc-webkitdom.cfg'))
>   File "/home/rego/checkout/WebKit/Tools/gtk/generate-gtkdoc", line 152, in generate_documentation_for_config
>     return generate_doc(generator, arguments.skip_html)
>   File "/home/rego/checkout/WebKit/Tools/gtk/generate-gtkdoc", line 133, in generate_doc
>     generator.generate(not skip_html)
>   File "/home/rego/checkout/WebKit/Tools/gtk/gtkdoc.py", line 145, in generate
>     self._run_gtkdoc_mkdb()
>   File "/home/rego/checkout/WebKit/Tools/gtk/gtkdoc.py", line 361, in _run_gtkdoc_mkdb
>     self._run_command(args, cwd=self.output_dir)
>   File "/home/rego/checkout/WebKit/Tools/gtk/gtkdoc.py", line 210, in _run_command
>     % (args[0], process.returncode))

Is there someone who knows how to fix this?

— Darin
_______________________________________________
webkit-dev mailing list
webkit-dev <at> lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
Said Abou-Hallawa | 6 Nov 20:19 2014
Picon

Tagged assertions...

Recently I ran into an issue where I wanted to find if there is a bug filed against a certain assertion. The only way I was able to use is to search for the name of the function which has the assertion.  The function can be overloaded or the function can have more than one assertion.  So I found it difficult to track the assertion I am interested in.  In future if the function gets renamed, it will be even more difficult.

I have a suggestion for this.

A pre-build tool will tag every new assertion after the change is committed.  For example in the code I will add the following assertion:

ASSERT(condition);

The pre-build tool will change it to be:

ASSERT_TAG(condition, “abcde”);

where “abcde” is a unique tag in all the source code.  A database should be maintained by the build process to keep track what tags are available to be assigned.

When the assertion fires, the dump may look like the following:

ASSERTION FAILED (tag: abcde) condition
… rest of the call-stack

In Bugzilla, there should be a field for the assertion tag.  If I want to file an assertion bug, I should be filling this field like the following:

Product: WebKit
Summary: ASSERTION failed in someFunction
Assertion tag: abcde
Description:
Attachment:

Later if the assertion fires, from the dump I can know exactly what assertion fired.  And more importantly I can search for it easily.  In the Bugzilla search page, I should see a field for the assertion tag in the simple search page:

Status: All
Product: WebKit
Words:
Assertion tag: abcde

This search will bring me all the opened bugs in WebKit which has the assertion tag = “abcde” if there is any.

ID Product Comp Assignee Status Resolution  Assertion tag  Summary
12345 WebKit abcde ASSERTION failed in someFunction

Thanks,
Said

_______________________________________________
webkit-dev mailing list
webkit-dev <at> lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
Bem Jones-Bey | 4 Nov 18:28 2014
Picon

ASAN and WebKit on OS X

Hey folks,

I'd like to get an ASAN build up and running. However, following the 
instructions on the Wiki (https://trac.webkit.org/wiki/ASanWebKit) isn't 
working for me. (And I had to modify them slightly since it looks like 
things are in slightly different places with Xcode 6.1?) Does anyone have 
more recent instructions? I'm still running OS X 10.9, if it matters.

Thanks,
Bem
Antti Koivisto | 31 Oct 18:02 2014
Picon
Picon

Disk cache

Hello,

I'm planning to add an experimental HTTP cache implementation to WebKit (https://bugs.webkit.org/show_bug.cgi?id=30322). The main motivations are:

- Improving performance by bringing the cache closer. For example we can serialize WebKit response objects directly instead of converting to/from platform types.
- Making future innovation around caching easier. Closer coordination between cache and WebKit opens new optimization possibilities.

The cache lives in the network process. Most of the code is cross-platform. The storage backend uses libdispatch IO though it wouldn't be hard to add a generic posix one too.

The code will be behind NETWORK_CACHE feature flag.


  antti
_______________________________________________
webkit-dev mailing list
webkit-dev <at> lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
Said Abou-Hallawa | 31 Oct 17:55 2014
Picon

gtk failure

I submitted a patch for the bug https://bugs.webkit.org/show_bug.cgi?id=137132The build failed for gtk-wk2 but passed for mac and mac-wk2. Here is the failure.
Last 500 characters of output:e/CMakeFiles/WebCore.dir/rendering/style/RenderStyle.cpp.o -c ../../Source/WebCore/rendering/style/RenderStyle.cpp ../../Source/WebCore/rendering/style/RenderStyle.cpp: In member function 'WebCore::Color WebCore::RenderStyle::colorIncludingFallback(int, bool) const': ../../Source/WebCore/rendering/style/RenderStyle.cpp:1525:10: error: 'CSSPropertyWebkitColumnRuleColor' was not declared in this scope case CSSPropertyWebkitColumnRuleColor:

In the patch I have the following change 

Source/WebCore/rendering/style/RenderStyle.cpp

<at> <at> Color RenderStyle::colorIncludingFallbac
15221522 case CSSPropertyOutlineColor:
15231523 result = visitedLink ? visitedLinkOutlineColor() : outlineColor();
15241524 break;
1525  case CSSPropertyWebkitColumnRuleColor:
 1525 case CSSPropertyColumnRuleColor:
15261526 result = visitedLink ? visitedLinkColumnRuleColor() : columnRuleColor();
15271527 break;
15281528 case CSSPropertyWebkitTextDecorationColor:


I am un-prefixing the column rule color property.  So I replaced CSSPropertyWebkitColumnRuleColor with CSSPropertyColumnRuleColor.  But the failure is saying the prefixed property is not defined.  

How can for gtk-wk2 only, the patch is not applied in RenderStyle.cpp but is applied with other files and is applied also for all files for the mac platform?

Thanks,
Said
_______________________________________________
webkit-dev mailing list
webkit-dev <at> lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
youenn fablet | 31 Oct 00:02 2014
Picon

Streams API

Hi all,

I would like to add support for the streams API ([1], [2]), starting
with readable streams and their integration with XHR and loaders.
This work is expected to happen behind a flag.

Regards,
   Youenn

[1] https://github.com/whatwg/streams
[2] http://www.w3.org/TR/streams-api/
Koen Bok | 29 Oct 11:00 2014

Re: webkit-dev Digest, Vol 113, Issue 19

Unsubscribe

On Tuesday, October 28, 2014, <webkit-dev-request <at> lists.webkit.org> wrote:

Send webkit-dev mailing list submissions to
        webkit-dev <at> lists.webkit.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.webkit.org/mailman/listinfo/webkit-dev
or, via email, send a message with subject or body 'help' to
        webkit-dev-request <at> lists.webkit.org

You can reach the person managing the list at
        webkit-dev-owner <at> lists.webkit.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of webkit-dev digest..."


Today's Topics:

   1. FOSDEM 2015 Desktops DevRoom Call for Talks (Pau Garcia i Quiles)
   2. Re: [blink-dev] FOSDEM 2015 Desktops DevRoom Call for     Talks
      (Levi Weintraub)
   3. OS X Mavericks build failing (Bem Jones-Bey)


----------------------------------------------------------------------

Message: 1
Date: Mon, 27 Oct 2014 21:00:35 +0100
From: Pau Garcia i Quiles <pgquiles <at> elpauer.org>
To: blink-dev <at> chromium.org,   "webkit-dev <at> lists.webkit.org"
        <webkit-dev <at> lists.webkit.org>
Subject: [webkit-dev] FOSDEM 2015 Desktops DevRoom Call for Talks
Message-ID:
        <CAKcBokvRCmge+7y1YpHxvUBYOv=-qJH57GVmQM=00=tRo-Zp1g <at> mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

 Hello,

--8<---

FOSDEM <http://www.fosdem.org> is one of the largest gatherings of Free
Software contributors in the world and happens each February in Brussels
(Belgium). One of the tracks will be the Desktops DevRoom (formerly known
as ?CrossDesktop DevRoom?), which will host Desktop-related talks.

We are now inviting proposals for talks about Free/Libre/Open-source
Software on the topics of Desktop development, Desktop applications and
interoperability amongst Desktop Environments. This is a unique opportunity
to show novel ideas and developments to a wide technical audience.

Topics accepted include, but are not limited to: Enlightenment, Gnome, KDE,
Unity, XFCE, LXQt, Windows, Mac OS X, software development for the desktop,
general desktop matters, applications that enhance desktops and web (when
related to desktop).

Talks can be very specific, such as the advantages/disadvantages of
development with Qt on Wayland over X11/Mir; or as general as predictions
for the fusion of Desktop and web in 5 years time. Topics that are of
interest to the users and developers of all desktop environments are
especially welcome. The FOSDEM 2014 schedule
<https://archive.fosdem.org/2014/schedule/track/desktops/> might give you
some inspiration.

Please include the following information when submitting a proposal:

   - Your name
   - The title of your talk (please be descriptive, as titles will be
   listed with around 250 from other projects)
   - Short abstract of one or two paragraphs
   - Short bio (with photo)
   - Requested time: from 15 to 45 minutes. Normal duration is 30 minutes.
   Longer duration requests must be properly justified. You may be assigned
   LESS time than you request.

The deadline for submissions is December 7th 2014. FOSDEM will be held on
the weekend of January 31st-February 1st 2015 and the Desktops DevRoom will
take place on Sunday, February 1st 2015. Please use the following website
to submit your proposals: https://penta.fosdem.org/submission/FOSDEM15 (you
do not need to create a new Pentabarf account if you already have one from
past years).

You can also join the devroom?s mailing list, which is the official
communication channel for the DevRoom: desktops-devroom <at> lists.fosdem.org
<https://lists.fosdem.org/private/desktops-devroom/> (subscription page
<https://lists.fosdem.org/listinfo/desktops-devroom> for the mailing list)

? The Desktops DevRoom 2015 Organization Team

--8<---


--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-dev/attachments/20141027/10f004bc/attachment-0001.html>

------------------------------

Message: 2
Date: Mon, 27 Oct 2014 13:04:21 -0700
From: Levi Weintraub <leviw <at> chromium.org>
To: Pau Garcia i Quiles <pgquiles <at> elpauer.org>
Cc: blink-dev <blink-dev <at> chromium.org>,       "webkit-dev <at> lists.webkit.org"
        <webkit-dev <at> lists.webkit.org>
Subject: Re: [webkit-dev] [blink-dev] FOSDEM 2015 Desktops DevRoom
        Call for        Talks
Message-ID:
        <CAMLeo+GCHOYhZXtFZcoVx=W-5PSHheq7B6nP3m_BmDfSqT16Lw <at> mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Please don't send advertisements or cross-post to these lists.

Thanks,
/L/

On Mon, Oct 27, 2014 at 1:00 PM, Pau Garcia i Quiles <pgquiles <at> elpauer.org>
wrote:

> Hello,
>
> --8<---
>
> FOSDEM <http://www.fosdem.org> is one of the largest gatherings of Free
> Software contributors in the world and happens each February in Brussels
> (Belgium). One of the tracks will be the Desktops DevRoom (formerly known
> as ?CrossDesktop DevRoom?), which will host Desktop-related talks.
>
> We are now inviting proposals for talks about Free/Libre/Open-source
> Software on the topics of Desktop development, Desktop applications and
> interoperability amongst Desktop Environments. This is a unique opportunity
> to show novel ideas and developments to a wide technical audience.
>
> Topics accepted include, but are not limited to: Enlightenment, Gnome,
> KDE, Unity, XFCE, LXQt, Windows, Mac OS X, software development for the
> desktop, general desktop matters, applications that enhance desktops and
> web (when related to desktop).
>
> Talks can be very specific, such as the advantages/disadvantages of
> development with Qt on Wayland over X11/Mir; or as general as predictions
> for the fusion of Desktop and web in 5 years time. Topics that are of
> interest to the users and developers of all desktop environments are
> especially welcome. The FOSDEM 2014 schedule
> <https://archive.fosdem.org/2014/schedule/track/desktops/> might give you
> some inspiration.
>
> Please include the following information when submitting a proposal:
>
>    - Your name
>    - The title of your talk (please be descriptive, as titles will be
>    listed with around 250 from other projects)
>    - Short abstract of one or two paragraphs
>    - Short bio (with photo)
>    - Requested time: from 15 to 45 minutes. Normal duration is 30
>    minutes. Longer duration requests must be properly justified. You may be
>    assigned LESS time than you request.
>
> The deadline for submissions is December 7th 2014. FOSDEM will be held on
> the weekend of January 31st-February 1st 2015 and the Desktops DevRoom will
> take place on Sunday, February 1st 2015. Please use the following website
> to submit your proposals: https://penta.fosdem.org/submission/FOSDEM15
> (you do not need to create a new Pentabarf account if you already have one
> from past years).
>
> You can also join the devroom?s mailing list, which is the official
> communication channel for the DevRoom: desktops-devroom <at> lists.fosdem.org
> <https://lists.fosdem.org/private/desktops-devroom/> (subscription page
> <https://lists.fosdem.org/listinfo/desktops-devroom> for the mailing list)
>
> ? The Desktops DevRoom 2015 Organization Team
>
> --8<---
>
>
> --
> Pau Garcia i Quiles
> http://www.elpauer.org
> (Due to my workload, I may need 10 days to answer)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-dev/attachments/20141027/c65cf119/attachment-0001.html>

------------------------------

Message: 3
Date: Mon, 27 Oct 2014 22:42:36 +0000
From: Bem Jones-Bey <bjonesbe <at> adobe.com>
To: webkit-dev <webkit-dev <at> lists.webkit.org>
Subject: [webkit-dev] OS X Mavericks build failing
Message-ID: <29823522-89CA-4DCA-A88C-89FA73A68900 <at> adobe.com>
Content-Type: text/plain; charset="us-ascii"

Howdy,

My build on Mavericks has stopped working, and I haven't changed anything except syncing to head and installing the Xcode patch that came out a couple of days ago. Since the bots are green, I can only assume it has something to do with the public SDK. I've filed a bug for this: https://bugs.webkit.org/show_bug.cgi?id=138108

Anyone know what the proper fix is?

Thanks,
Bem

------------------------------

_______________________________________________
webkit-dev mailing list
webkit-dev <at> lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev


End of webkit-dev Digest, Vol 113, Issue 19
*******************************************
_______________________________________________
webkit-dev mailing list
webkit-dev <at> lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Gmane