Re: [webkit-dev] Importing W3C tests for HTML template elements

2013-12-06 Thread youenn fablet
As long as the newly imported tests use relative URLs, alias may be used as
a workaround. I will give it a try.
Bug entry is at https://bugs.webkit.org/show_bug.cgi?id=125339
Any further help appreciated,
  Youenn



2013/12/6 Darin Adler da...@apple.com

 If that's really ends up being super hard we can always put yet another
 third-party or imported directory inside the http directory as previously
 suggested. it's annoying to have three different places for imported tests
 and code, but not something I want to hold us up for a long time.

 -- Darin

 Sent from my iPhone

 On Dec 5, 2013, at 5:51 PM, Ryosuke Niwa rn...@webkit.org wrote:

 On Wed, Dec 4, 2013 at 11:19 AM, Darin Adler da...@apple.com wrote:

 On Dec 4, 2013, at 6:48 AM, youenn fablet youe...@gmail.com wrote:

 I am planning to add some XHR tests from
 https://github.com/w3c/web-platform-tests.
 My initial plan was to add them in a subdirectory of
 LayoutTests/http/tests/w3c.
 If adding them into LayoutTests/imported/w3c, that would probably
 require updating the test scripts to start/stop the HTTP test server for
 that particular sub-folder.

 Any preference?


 I’d prefer LayoutTests/imported/w3c. Although I’m not so happy about the
 different terminology we are using for “imported” vs. “ThirdParty”, which
 seems like the same concept at the top level of the directory structure.


 One trickiness to it is that we don't currently run any HTTP test in
 parallel and the document root of the HTTP server is set to
 LayoutTests/http/tests so we might need to modify that or restart the HTTP
 server whenever we're running HTTP tests outside of LayoutTests/http.

 - R. Niwa


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


Re: [webkit-dev] Hi

2013-12-06 Thread PERIER Romain
Hi,

Perhaps that webkit-...@lists.webkit.org is more suitable for this question
(as this is related to the gtk port)

Romain


2013/12/6 larry x.wang larry.x.w...@oracle.com

  How can I install a specific version of webkitgtk? ie 1.9.X
 in the download tar,When I extract the tar package,the install and readme
 is empty.I don't how build it from source and how to install it.
 I also download the full package of webkit-svn about 1G,where I follow the
 instruction,the command error occur.
 the error is like below:
 Trying other mirror.
 Error: Cannot retrieve repository metadata (repomd.xml) for repository:
 adobe-linux-i386. Please verify its path and try again

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

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


Re: [webkit-dev] [JSCore] No call to finalize() via Garbage Collector ?

2013-12-06 Thread Manuel BACHMANN
HI Geoffrey,

Thanks a lot for your answer.
After studying the code a bit, it appears that my app is sharing a
JSGlobalContext with others. This context is, by design, never destroyed.

I read the WebKit JavaScript core documentation (
https://developer.apple.com/library/mac/documentation/Carbon/Reference/WebKit_JavaScriptCore_Ref/WebKit_JavaScriptCore_Ref.pdf),
and it says a JSGlobalContext is a standard JSContext.

So I suppose that's why the garbage collector never runs finalize() ?
Anyways, thanks for the hints.


Regards,
Manuel
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Importing W3C tests for HTML template elements

2013-12-06 Thread Dirk Pranke
The way I got around this when I was first working on it was to simply map
imported/w3c onto a subdirectory of the document root in apache; it's a two
line change.

For some time I've toyed with the idea of changing the DocumentRoot to just
be LayoutTests/, so that any test could be run over http directly. A lot of
tests and test results would need to be updated for this, but I think it
could simplify the test organization a fair amount and open up some
interesting possibilities.

-- Dirk

On Thu, Dec 5, 2013 at 6:25 PM, Darin Adler da...@apple.com wrote:

 If that's really ends up being super hard we can always put yet another
 third-party or imported directory inside the http directory as previously
 suggested. it's annoying to have three different places for imported tests
 and code, but not something I want to hold us up for a long time.

 -- Darin

 Sent from my iPhone

 On Dec 5, 2013, at 5:51 PM, Ryosuke Niwa rn...@webkit.org wrote:

 On Wed, Dec 4, 2013 at 11:19 AM, Darin Adler da...@apple.com wrote:

 On Dec 4, 2013, at 6:48 AM, youenn fablet youe...@gmail.com wrote:

 I am planning to add some XHR tests from
 https://github.com/w3c/web-platform-tests.
 My initial plan was to add them in a subdirectory of
 LayoutTests/http/tests/w3c.
 If adding them into LayoutTests/imported/w3c, that would probably
 require updating the test scripts to start/stop the HTTP test server for
 that particular sub-folder.

 Any preference?


 I’d prefer LayoutTests/imported/w3c. Although I’m not so happy about the
 different terminology we are using for “imported” vs. “ThirdParty”, which
 seems like the same concept at the top level of the directory structure.


 One trickiness to it is that we don't currently run any HTTP test in
 parallel and the document root of the HTTP server is set to
 LayoutTests/http/tests so we might need to modify that or restart the HTTP
 server whenever we're running HTTP tests outside of LayoutTests/http.

 - R. Niwa


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


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


[webkit-dev] WebKit, C++11, and Visual Studio 2013

2013-12-06 Thread Brent Fulgham
Hi Everyone,

We are working hard to move WebKit toward stronger adoption of C++11 features, 
such as variadic templates, ranged for-loops, and initializer lists. 
Unfortunately, this effort has been hampered by the small subset of C++11 
features available in Visual Studio 2010.

You can get a feel for the level of C++11 support in the last few versions of 
Visual Studio here:
http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx

With Visual Studio 2013, we finally have access to a compiler that supports the 
major C++11 features we need. Consequently, we intend to switch to VS2013 and 
begin taking advantage of these new language constructs.

Over the next week we will be landed a series of source changes that allow 
WebKit to be built with VS2013, but will continue to build with VS2010 on our 
build machines.  Next Friday, we plan to land project file changes to switch to 
the new compiler, and will simultaneously convert our build system to use 
VS2013 as well.

Once the revised project files are landed, we will no longer be officially 
supporting Visual Studio 2010 as a compiler target.

For those playing at home, you can track progress by following 
https://bugs.webkit.org/show_bug.cgi?id=125192.

WebKit continues to build with the free “Visual Studio 2013 Express” software, 
so I do not anticipate that this change will block any external developers from 
running Windows builds.

Thanks,

-Brent



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


Re: [webkit-dev] WebKit, C++11, and Visual Studio 2013

2013-12-06 Thread Benjamin Poulain

That is awesome. Great work!

Benjamin

On 12/6/13, 2:53 PM, Brent Fulgham wrote:

Hi Everyone,

We are working hard to move WebKit toward stronger adoption of C++11
features, such as variadic templates, ranged for-loops, and initializer
lists. Unfortunately, this effort has been hampered by the small subset
of C++11 features available in Visual Studio 2010.

You can get a feel for the level of C++11 support in the last few
versions of Visual Studio here:
http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx

With Visual Studio 2013, we finally have access to a compiler that
supports the major C++11 features we need. Consequently, we intend to
switch to VS2013 and begin taking advantage of these new language
constructs.

Over the next week we will be landed a series of source changes that
allow WebKit to be built with VS2013, but will continue to build with
VS2010 on our build machines.  Next Friday, we plan to land project file
changes to switch to the new compiler, and will simultaneously convert
our build system to use VS2013 as well.

Once the revised project files are landed, we will no longer be
officially supporting Visual Studio 2010 as a compiler target.

For those playing at home, you can track progress by following
https://bugs.webkit.org/show_bug.cgi?id=125192.

WebKit continues to build with the free “Visual Studio 2013 Express”
software, so I do not anticipate that this change will block any
external developers from running Windows builds.

Thanks,

-Brent





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



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


Re: [webkit-dev] WebKit, C++11, and Visual Studio 2013

2013-12-06 Thread Romain Perier
Wonderful ! C++11 is a great norm, good news ! ;)


Le 6 déc. 2013 à 23:53, Brent Fulgham bfulg...@apple.com a écrit :

Hi Everyone,

We are working hard to move WebKit toward stronger adoption of C++11
features, such as variadic templates, ranged for-loops, and initializer
lists. Unfortunately, this effort has been hampered by the small subset of
C++11 features available in Visual Studio 2010.

You can get a feel for the level of C++11 support in the last few versions
of Visual Studio here:
http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx

With Visual Studio 2013, we finally have access to a compiler that supports
the major C++11 features we need. Consequently, we intend to switch to
VS2013 and begin taking advantage of these new language constructs.

Over the next week we will be landed a series of source changes that allow
WebKit to be built with VS2013, but will continue to build with VS2010 on
our build machines.  Next Friday, we plan to land project file changes to
switch to the new compiler, and will simultaneously convert our build
system to use VS2013 as well.

Once the revised project files are landed, we will no longer be officially
supporting Visual Studio 2010 as a compiler target.

For those playing at home, you can track progress by following
https://bugs.webkit.org/show_bug.cgi?id=125192.

WebKit continues to build with the free “Visual Studio 2013 Express”
software, so I do not anticipate that this change will block any external
developers from running Windows builds.

Thanks,

-Brent



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


Re: [webkit-dev] WebKit, C++11, and Visual Studio 2013

2013-12-06 Thread Alex Christensen
Is there any advantage of VS2013 instead of VS2012?  I've been using VS2012
for a while, and it works fine.  It also has the C++11 features we want to
use.  Staying one version behind the latest usually prevents updates from
breaking things.

Alex Christensen


On Fri, Dec 6, 2013 at 3:53 PM, Brent Fulgham bfulg...@apple.com wrote:

 Hi Everyone,

 We are working hard to move WebKit toward stronger adoption of C++11
 features, such as variadic templates, ranged for-loops, and initializer
 lists. Unfortunately, this effort has been hampered by the small subset of
 C++11 features available in Visual Studio 2010.

 You can get a feel for the level of C++11 support in the last few versions
 of Visual Studio here:
 http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx

 With Visual Studio 2013, we finally have access to a compiler that
 supports the major C++11 features we need. Consequently, we intend to
 switch to VS2013 and begin taking advantage of these new language
 constructs.

 Over the next week we will be landed a series of source changes that allow
 WebKit to be built with VS2013, but will continue to build with VS2010 on
 our build machines.  Next Friday, we plan to land project file changes to
 switch to the new compiler, and will simultaneously convert our build
 system to use VS2013 as well.

 Once the revised project files are landed, we will no longer be officially
 supporting Visual Studio 2010 as a compiler target.

 For those playing at home, you can track progress by following
 https://bugs.webkit.org/show_bug.cgi?id=125192.

 WebKit continues to build with the free “Visual Studio 2013 Express”
 software, so I do not anticipate that this change will block any external
 developers from running Windows builds.

 Thanks,

 -Brent




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




-- 



Alex Christensen

FlexSim Software Products, Inc.

*1577 North Technology Way | Building A | Suite 2300 | Orem, Utah 84097*

*Voice: 801-224-6914 | Fax: 801-224-6984*

*Email:* al...@flexsim.com k...@flexsim.com

*URL:* www.flexsim.com





This message may contain confidential information, and is intended

only for the use of the individual(s) to whom it is addressed.

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


Re: [webkit-dev] WebKit, C++11, and Visual Studio 2013

2013-12-06 Thread Brent Fulgham
Hi Alex,

There are a few items missing from VS2012 (see 
http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx) that we are 
already using in the Mac-specific source code:

1. Variadic Templates
2. Initializer Lists
3. Explicit conversion operators
4. Deleted functions

None of those items are supported in VS2012, and we would like to expand their 
use to the rest of WebKit.  Clang and GCC already support these features, so 
VS2012 (and earlier) hold the rest of the project back.

-Brent


On Dec 6, 2013, at 4:05 PM, Alex Christensen alex.christen...@flexsim.com 
wrote:

 Is there any advantage of VS2013 instead of VS2012?  I've been using VS2012 
 for a while, and it works fine.  It also has the C++11 features we want to 
 use.  Staying one version behind the latest usually prevents updates from 
 breaking things.
 
 Alex Christensen
 
 
 On Fri, Dec 6, 2013 at 3:53 PM, Brent Fulgham bfulg...@apple.com wrote:
 Hi Everyone,
 
 We are working hard to move WebKit toward stronger adoption of C++11 
 features, such as variadic templates, ranged for-loops, and initializer 
 lists. Unfortunately, this effort has been hampered by the small subset of 
 C++11 features available in Visual Studio 2010.
 
 You can get a feel for the level of C++11 support in the last few versions of 
 Visual Studio here:
   http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx
 
 With Visual Studio 2013, we finally have access to a compiler that supports 
 the major C++11 features we need. Consequently, we intend to switch to VS2013 
 and begin taking advantage of these new language constructs.
 
 Over the next week we will be landed a series of source changes that allow 
 WebKit to be built with VS2013, but will continue to build with VS2010 on our 
 build machines.  Next Friday, we plan to land project file changes to switch 
 to the new compiler, and will simultaneously convert our build system to use 
 VS2013 as well.
 
 Once the revised project files are landed, we will no longer be officially 
 supporting Visual Studio 2010 as a compiler target.
 
 For those playing at home, you can track progress by following 
 https://bugs.webkit.org/show_bug.cgi?id=125192.
 
 WebKit continues to build with the free “Visual Studio 2013 Express” 
 software, so I do not anticipate that this change will block any external 
 developers from running Windows builds.
 
 Thanks,
 
 -Brent
 
 
 
 
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 https://lists.webkit.org/mailman/listinfo/webkit-dev
 
 
 
 
 -- 
  
 Alex Christensen
 
 FlexSim Software Products, Inc.
 
 1577 North Technology Way | Building A | Suite 2300 | Orem, Utah 84097
 
 Voice: 801-224-6914 | Fax: 801-224-6984
 
 Email: al...@flexsim.com
 
 URL: www.flexsim.com
 
  
 
  
 This message may contain confidential information, and is intended
 
 only for the use of the individual(s) to whom it is addressed. 
 
 

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


Re: [webkit-dev] WebKit, C++11, and Visual Studio 2013

2013-12-06 Thread Anders Carlsson

On Dec 6, 2013, at 4:15 PM, Brent Fulgham bfulg...@apple.com wrote:

 Hi Alex,
 
 There are a few items missing from VS2012 (see 
 http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx) that we are 
 already using in the Mac-specific source code:
 
 1. Variadic Templates
 2. Initializer Lists
 3. Explicit conversion operators
 4. Deleted functions

5. range-based for loops.

- Anders


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


Re: [webkit-dev] WebKit, C++11, and Visual Studio 2013

2013-12-06 Thread Alex Christensen
You talked me into it!  I'll go get VS2013.  I hope it crashes less than
VS2010, too.

Alex


On Fri, Dec 6, 2013 at 5:26 PM, Anders Carlsson ander...@apple.com wrote:


 On Dec 6, 2013, at 4:15 PM, Brent Fulgham bfulg...@apple.com wrote:

 Hi Alex,

 There are a few items missing from VS2012 (see
 http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx) that we
 are already using in the Mac-specific source code:

 1. Variadic Templates
 2. Initializer Lists
 3. Explicit conversion operators
 4. Deleted functions


 5. range-based for loops.

 - Anders





-- 



Alex Christensen

FlexSim Software Products, Inc.

*1577 North Technology Way | Building A | Suite 2300 | Orem, Utah 84097*

*Voice: 801-224-6914 | Fax: 801-224-6984*

*Email:* al...@flexsim.com k...@flexsim.com

*URL:* www.flexsim.com





This message may contain confidential information, and is intended

only for the use of the individual(s) to whom it is addressed.

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


Re: [webkit-dev] MAC :: building gstreamer by WebKit but without CAIRO

2013-12-06 Thread Hugo Machefer
Actually, despite similarities with WIN32 situation, this patch seemed to
be useless in our case. I managed to
go one step beyond by adding (sadly but surely ;-) Glibutilies.o +
GOwnPtr.o + GrefPtr.o in WebCore.xcodeproj
manually by XCODE to force LINK with these file objects... That are
generated elsewhere by WTF.xcodeproj...
Then, symbols that were assumed unresolved by WebCore are in fact defined
in other locations == in WTF.

  -- hmachefe

PS : now = the time has come to execute binary/libraries. Lets' stay tuned.

On Thu, Nov 28, 2013 at 3:46 PM, Philippe Normand ph...@igalia.com wrote:

 I think https://bugs.webkit.org/show_bug.cgi?id=124861 is about fixing
 this issue.

 Philippe

 On Wed, 2013-11-27 at 22:47 +0100, Pascal Brianceau wrote:
  Files shared by Hugo raised the same issue on my side. Did anyone make
  a step forward ? Any tip Philippe ?
 
 
  /* Pascal */
 
 
  On Mon, Nov 25, 2013 at 9:52 AM, Hugo Machefer
  hugo.mache...@gmail.com wrote:
  Indeed: I didn't solve this yet; I can only say that the
  following line is responsible for these unresolved symbols:
 
 
  GOwnPtrGError error;
 
 
-- hmachefe
 
 
  On Sun, Nov 24, 2013 at 10:04 PM, gstreamer MACOSX
  gstreamermac...@gmail.com wrote:
  I managed to restore  ImageGStreamerCG.cpp however
  LINK fails :
 
 
__ZN3WTF13freeOwnedGPtrI7_GErrorEEvPT_, referenced
  from:
 
 
 __ZN7WebCore27MediaPlayerPrivateGStreamer13handleMessageEP11_GstMessage in
 MediaPlayerPrivateGStreamer.o
__ZN7WebCore19initializeGStreamerEv in
  GStreamerUtilities.o
 
 
-- gstreamermacosx
 
 
  PS: special thanks to hmachefe for precious
  restoration tips and to Philippe of course
 
 
 
  On Sat, Nov 23, 2013 at 9:59 AM, Philippe Normand
  ph...@igalia.com wrote:
  The ImageGStreamerCG implementation was
  removed in
  http://trac.webkit.org/changeset/118610
 
  Philippe
 
  On Sat, 2013-11-23 at 00:44 +0100, Urbain EGIS
  wrote:
   I compiled most of
  Source/WebCore/platform/graphics/gstreamer
  apart
   from ImageGstreamerCairo.cpp which has a
  strong dependency on CAIRO.
  
  
   It seems to be overkill to build WebKit by
  enabling CAIRO... Because
   (only ;-) one file ImageGstreamerCairo
  requires a specific CAIRO
   surface.
  
  
   So What would be the best strategy in case
  of MAC ?
   1° activate CAIRO by WebKit and generate it
  again (+gstreamer) ... ?
   Really ?
   2° get rid of CAIRO and find an alternative
  by CF/CG rather in terms
   of surface
  
  
   -- Egis
  
 
  
  ___
   webkit-dev mailing list
   webkit-dev@lists.webkit.org
  
 
 https://lists.webkit.org/mailman/listinfo/webkit-dev
 
 
  ___
  webkit-dev mailing list
  webkit-dev@lists.webkit.org
 
 https://lists.webkit.org/mailman/listinfo/webkit-dev
 
 
 
  ___
  webkit-dev mailing list
  webkit-dev@lists.webkit.org
  https://lists.webkit.org/mailman/listinfo/webkit-dev
 
 
 
 
  ___
  webkit-dev mailing list
  webkit-dev@lists.webkit.org
  https://lists.webkit.org/mailman/listinfo/webkit-dev
 
 
 
  ___
  webkit-dev mailing list
  webkit-dev@lists.webkit.org
  https://lists.webkit.org/mailman/listinfo/webkit-dev


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

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


Re: [webkit-dev] WebKit, C++11, and Visual Studio 2013

2013-12-06 Thread Mital Vora
This is great news !! Looking forward to see WinCairo on VS2013 :) Good
Work guys !

Regards,

Mital Vora.


On Sat, Dec 7, 2013 at 4:23 AM, Brent Fulgham bfulg...@apple.com wrote:

 Hi Everyone,

 We are working hard to move WebKit toward stronger adoption of C++11
 features, such as variadic templates, ranged for-loops, and initializer
 lists. Unfortunately, this effort has been hampered by the small subset of
 C++11 features available in Visual Studio 2010.

 You can get a feel for the level of C++11 support in the last few versions
 of Visual Studio here:
 http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx

 With Visual Studio 2013, we finally have access to a compiler that
 supports the major C++11 features we need. Consequently, we intend to
 switch to VS2013 and begin taking advantage of these new language
 constructs.

 Over the next week we will be landed a series of source changes that allow
 WebKit to be built with VS2013, but will continue to build with VS2010 on
 our build machines.  Next Friday, we plan to land project file changes to
 switch to the new compiler, and will simultaneously convert our build
 system to use VS2013 as well.

 Once the revised project files are landed, we will no longer be officially
 supporting Visual Studio 2010 as a compiler target.

 For those playing at home, you can track progress by following
 https://bugs.webkit.org/show_bug.cgi?id=125192.

 WebKit continues to build with the free “Visual Studio 2013 Express”
 software, so I do not anticipate that this change will block any external
 developers from running Windows builds.

 Thanks,

 -Brent




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


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