[webkit-dev] [gtk] OpenGL headers are not listed as a dependency

2011-12-01 Thread John Yani
I followed this instruction http://trac.webkit.org/wiki/BuildingGtk and
I've got a configure error: GL/gl.h  not found.

When I installed mesa-common-dev, linker said it cannot find -lGL

Is something wrong with my distribution? I'm running Ubuntu  11.10.

Or I should install opengl package or something?
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] [gtk] OpenGL headers are not listed as a dependency

2011-12-01 Thread John Yani
Got it working by installing these packages:

libgl1-mesa-glx
libgl1-mesa-dev

Probably, It should've been written in the instruction.


On 2 December 2011 01:30, John Yani  wrote:

> I followed this instruction http://trac.webkit.org/wiki/BuildingGtk and
> I've got a configure error: GL/gl.h  not found.
>
> When I installed mesa-common-dev, linker said it cannot find -lGL
>
> Is something wrong with my distribution? I'm running Ubuntu  11.10.
>
> Or I should install opengl package or something?
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Tools/Scripts/build-webkit --gtk --debug --makeargs="-j1" taking up to 80% of memory

2012-01-04 Thread John Yani
On Mon, 2011-12-26 at 21:45 -0800, sachin nikam wrote:
> I synced up the latest webkit code base and am trying to build webkit
> gtk on ubuntu 11.10 with 4gb of RAM and 4 CPUs
>
> I tried with --makeargs="-j2" but still got "ld process terminated
> signal[9]" error ?which indicates that it ran out of memory.
> I suspect i will still the get the same error with --makeargs="-j1".
> Is there any other flag where we can restrict the memory usage?
> Regards
> Sachin

I had the same problem after I've upgraded my PC to 12 GB of RAM.
Before upgrade I was able to build 32 bit webkit on my 4 GB computer
with Ubuntu 11.10 32-bit with PAE and 8 GB of swap.
So what I recommend is to remove 1 GB of memory (or load something
heavy to take that 1GB of RAM) and add more swap.

Physical address extension doesn't allow any process to take more than
[specific amount] of physical RAM, so swap  must be used. In your case
it seems like swap is never used, so the system fails to address
additional physical memory you have.

But I highly recommend upgrading your computer to minimum of 8 GB of
RAM and install 64 bit Ubuntu. If you really need 32-bit build,
cross-compiling might be an option.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Using GitHub to Contribute to WebKit (Experimental)

2012-03-16 Thread John Yani
On 16 March 2012 18:34, Ryosuke Niwa  wrote:
> If some reviewer and committer decide to use this process, where can I see
> review comments and other discussions?

See point 3  of "Landing your code". Reviewer adds a link to pull
request  in changelog.

>
> Would they still be on Bugzilla?

I suppose, they'll be only on github.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted

2012-03-23 Thread John Yani
I think you have to have at least 8 GiB of RAM (16 GiB is recommended)
and 64-bit OS to compile webkit in debug mode.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted

2012-03-23 Thread John Yani
Or you can add 8 GiB of swap, like I did before I upgraded my machine:
https://lists.webkit.org/pipermail/webkit-help/2011-November/002678.html
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted

2012-03-23 Thread John Yani
WebKit's codebase increases every day, so It's not strange that it
requires more and more memory to link.

On 23 March 2012 12:03, Sanjeet Pratap Singh
 wrote:
> Hi John, Thanks for your instant response.
> But, I had been compiling webkit in debug mode earlier, with the same
> configurations with no such any error.
> And thats why I doubt whether increasing the RAM, is an proper and generic
> solution.
>
> Thanks,
> Sanjeet
>
> On Fri, Mar 23, 2012 at 3:18 PM, John Yani  wrote:
>>
>> I think you have to have at least 8 GiB of RAM (16 GiB is recommended)
>> and 64-bit OS to compile webkit in debug mode.
>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted

2012-03-23 Thread John Yani
> This even affects 64bit systems with 12GB of ram. :-|

So you're saying that you've tried to build webkit on 64bit system
with 12GiB of RAM and failed? How much memory is used when build is
not running?
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Eliminate potential null pointer dereference?

2012-04-21 Thread John Yani
On 20 April 2012 08:18, Alexey Proskuryakov  wrote:
>
> I noticed a number of patches going in recently that add null checks, or 
> refactor the code under the premise of "eliminating potential null 
> dereference". What does that mean, and why are we allowing such patches to be 
> landed?
>
> For example, this change doesn't look nice: 
> .

It means that there might be a situation when selector is null after
first loop finishes:

2310 while (selector) {
2311// Allow certain common attributes (used in the default
style) in the selectors that match the current element.
2312if (selector->isAttributeSelector() &&
!isCommonAttributeSelectorAttribute(selector->attribute()))
2313return true;
2314if (selectorListContainsUncommonAttributeSelector(selector))
2315return true;
2316if (selector->relation() != CSSSelector::SubSelector)
2317break;
2318selector = selector->tagHistory();
2319};

Now selector is null and we are trying to call tagHistory():

2320
2321for (selector = selector->tagHistory(); selector; selector =
selector->tagHistory()) {
2322if (selector->isAttributeSelector())
2323return true;
2324if (selectorListContainsUncommonAttributeSelector(selector))
2325return true;
2326}

Which will result in segfault.

> We should not try to confuse ourselves with unusual for loop forms, and there 
> is no explanation at all of why these changes are needed. No regression tests 
> either.

To construct an obvious test it would be needed to move static inline
function "containsUncommonAttributeSelector" to either
CSSStyleSelector.h or a new file CSSStyleSelectorHelper.h

Then the test would be trivial:

WebCore::CSSSelector selector;
bool doesContain = WebCore::containsUncommonAttributeSelector(&selector);
ASSERT_TRUE(!doesContain);

Without the mentioned patch the above lines would result in a crash.

If your concern is only about missing explanation on why changes
required to add a test are not practical, I totally agree. Otherwise
I'm missing the point.

>
> - WBR, Alexey Proskuryakov
>
> ___
> 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] How to use local icon for Web Notification API?

2012-05-15 Thread John Yani
I'm afraid this is not an appropriate list to ask. You should  try
stackoverflow first. If you think there is a bug in chrome, try the
chrome issue tracker.
Only if you're sure that all webkit browsers are affected, submit a
bug to the webkit tracker.

On 15 May 2012 10:16, Li-Chung Chang  wrote:
> Hi,
>
> All *html & *js file are located in the local.
> And follow the instructions from
> http://www.html5rocks.com/en/tutorials/notifications/quick/
>
> I take a try for showing a notification with local icon (URL:
>  file:///x/icon.png)
> like:
> window.webkitNotifications.createnotification("file:///icon.png",
> "Notification", "some detail...").show();
>
>
> I launched by "$google-chrome --allow-file-access-from-files"
> Notification can be shown but the icon is blank
>
> BTW, Icon can be shown if URL is a with http:// prefix.
>
> How to use local icon(file://) for web notification API?
>
> Please reply if you get any suggestion for that.
> Thanks.
>
> Ziv
>
>
> ___
> 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] Easing printf based debugging in WebKit with an helper.

2012-07-25 Thread John Yani
>> That possibility aside, the stronger part of my objection is language
>> purity.  WebCore uses C++ as "C with classes" and I don't think it's worth
>> it to confuse new (or existing) contributors about that going forward.
>>
>
> Can you elaborate why WebCore uses C++ as  "C with classes"?

Probably he meant that Webkit doesn't use STL, exceptions and RTTI.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Webgl support problem

2013-01-20 Thread John Yani
Try using stackoverflow for questions like that. This is not HTML5 support
forum.
21.01.2013 8:42 пользователь "Chandrakant Rinayat" <
chandrakant2...@gmail.com> написал:

> Hi, I am running simple webgl apps with webkit-clutter port, but it's
> giving an  error that "TypeError: 'null' is not an object" in line number
> 10, where gl.clearColor(0,0,0.8,1) function is present.please tell me what
> is being wrong.
> ___
> 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] Media Server Development

2013-01-31 Thread John Yani
Hi Kiran,

I'm afraid, this is not the right place to ask questions like that. Try
asking webkit-help.

On 31 January 2013 19:34, Kiran K  wrote:

> HI All,
>
> I am working on QtWebKit  on Media Server development. Basic Idea is to
> run Gstreamer in seperate process which acts like a Media server. The
> calls  from WebKit in MediaPlayerPrivateGStreamer.cpp are routed to Media
> Server via DBUS. Media Server implements the methods in
> MediaPlayerPrivateGStreamer class. I am basically doing this to have
> control over the resources like maximum playback instances, hw codec
> control etc. I am able to do achieve playback to some extent. I am facing
> some problems  (race conditions) especially when deleting playback
> instance. From the logs i concluded that when duration() function is made
> and is waiting for response from server, ~MediaPlayerPrivateGStreamer
> destructor is getting called. (some times vice versa too). I am suspecting
> that the MediaPlayer object is being shared between two threads (or across
> timers). Can anybody give me some pointers about HTMLMediaElement  and the
> timers involved? Any help is appreciated.
>
> Thanks,
> Arun
>
>
> ___
> 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] sln files with wrong line endings

2013-02-14 Thread John Yani
Checkout this link:
https://help.github.com/articles/dealing-with-line-endings

I don't know what the webkit convention is when dealing with line-endings,
but you may want to make sln files to always have crlf line-ending.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Kickstarting the migration of platform-specific WebCore source code to Source/Platform

2013-02-28 Thread John Yani
If I understood correctly, the idea is that WebCore should depend on
"platform", not vice versa.

Still, while "platform" provides platform independent API to WebCore, it
has platform-specific bits.

Did I get the idea correctly?
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev