Re: [webkit-dev] Windows 32-bit support?

2019-06-25 Thread Arunprasad Rajkumar
Hello Michael,

Thanks for your reply.

The last version of WebKitGTK to support Windows was 2.4, from 2014.
>
Sorry for the confusion. Though JavaFX WebKit port is based on GTK stable
branches, we don't use any GTK specific bits. We rely on GTK release
branches to cherry-pick the stabilisation patches to our downstream branch.

Anyway, to answer your question: JavaScriptCore is used on Windows by
> the Apple Windows port and the WinCairo port, and there is very little
> GTK-specific code in JSC, so this should be the easiest part of
> WebKitGTK to get working on Windows. You might consider basing your
> Windows port on WinCairo rather than WebKitGTK, since that port is
> designed to run on Windows.

Right. Actually the problem is in 32-bit Windows platform. I see that the
JIT support has been dropped some time ago, and CLOOP based backend seems
to be unstable on 32-bit Windows. Any thoughts on that?

Thanks & Regards,
Arun


On Tue, 25 Jun 2019 at 19:59, Michael Catanzaro 
wrote:

> On Tue, Jun 25, 2019 at 8:31 AM, Arunprasad Rajkumar
>  wrote:
> > So my question is, do WebKit/JavaScriptCore still supports 32-bit
> > Windows?
>
> Hi Arunprasad,
>
> The last version of WebKitGTK to support Windows was 2.4, from 2014.
>
Sorry f


> If you had 2.22 working, that's news to us. To my knowledge, nobody has
> ever done that before. You might well be the only one; certainly you're
> the only one to tell us about it. Anyway, that's cool.
>
> We don't support Windows anymore because nobody seems to be interested
> in (a) making it work, and (b) maintaining the code upstream. So you're
> kinda on your own here. If you only needed a few downstream changes
> required to make it work, then we could consider accepting those
> upstream if you'd be willing to maintain the Windows-specific parts.
> We're not going to be willing to bring back real Windows support
> otherwise, since all current developers use Linux and are only
> interested in Linux.
>
> Anyway, to answer your question: JavaScriptCore is used on Windows by
> the Apple Windows port and the WinCairo port, and there is very little
> GTK-specific code in JSC, so this should be the easiest part of
> WebKitGTK to get working on Windows. You might consider basing your
> Windows port on WinCairo rather than WebKitGTK, since that port is
> designed to run on Windows.
>
> Good luck,
>
> Michael
>
>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev


[webkit-dev] Windows 32-bit support?

2019-06-25 Thread Arunprasad Rajkumar
Hello,

I'm a JavaFX WebKit port maintainer and currently working to merge GTK
WebKit 2.24.x(608.1)
 to
our downstream
branch
.
I see couple of issues related to Windows 32-bit build, mostly related to
recursion tests(js/dom/modules/import-execution-order.html,
fast/dom/Document/document-write-recursion.html).

It used to work on GTK 2.22.x(607.1)
 branch,
but it now stopped working. I investigated the issue and I found that it
needs more stack space to run. It works when I bump up the stack space to
1MB. I don't see any issues on Linux 32-bit platform.

So my question is, do WebKit/JavaScriptCore still supports 32-bit Windows?

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


Re: [webkit-dev] How to download build bot archives of AppleWin build?

2017-12-14 Thread Arunprasad Rajkumar
Thanks @Mathias.

​Thanks & Regards,
Arun

On 14 December 2017 at 14:54, Mathias Bynens <m...@google.com> wrote:

> Windows debug builds have the following URL format: https://s3-us-west-2.
> amazonaws.com/archives.webkit.org/win-i386-debug/${revision}.zip
>
> At the moment of writing, r225896 is the latest revision, so the download
> URL would be: https://s3-us-west-2.amazonaws.com/archives.webkit.
> org/win-i386-debug/225896.zip
>
> jsvu gets these downloads programmatically: https://
> github.com/GoogleChromeLabs/jsvu/tree/master/engines/javascriptcore
>
> On Thu, Dec 14, 2017 at 10:16 AM, Arunprasad Rajkumar <
> ararunpra...@gmail.com> wrote:
>
>> Hello Floks,
>>
>> Is it possible to download Apple Windows build from somewhere? Windows is
>> not listed in WebKit build archives page.
>>
>> [1] https://webkit.org/build-archives
>>
>> ​Thanks & Regards,
>> 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


[webkit-dev] How to download build bot archives of AppleWin build?

2017-12-14 Thread Arunprasad Rajkumar
Hello Floks,

Is it possible to download Apple Windows build from somewhere? Windows is
not listed in WebKit build archives page.

[1] https://webkit.org/build-archives

​Thanks & Regards,
Arun
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Changes in QtWebKit development

2013-09-30 Thread Arunprasad Rajkumar
New XML parser was removed from the tree [1].

[1] https://lists.webkit.org/pipermail/webkit-dev/2012-August/022103.html

http://trac.webkit.org/changeset/140399


On 30 September 2013 19:18, Konstantin Tokarev annu...@yandex.ru wrote:



 30.09.2013, 17:39, Dirk Schulze k...@webkit.org:
  On Sep 30, 2013, at 11:58 AM, Allan Sandfeld Jensen k...@carewolf.com
 wrote:
 
   On Thursday 26 September 2013, Andreas Kling wrote:
   On Sep 25, 2013, at 12:40 PM, Allan Sandfeld Jensen k...@carewolf.com
 
   wrote:
   On Saturday 14 September 2013, Andreas Kling wrote:
   On Sep 14, 2013, at 11:24 AM, Allan Sandfeld Jensen 
 k...@carewolf.com
   wrote:
   That said, in all likelihood the Qt port will not remain part of
 WebKit
   forever, ...
   (This being the main reason.)
 
   Since you already know you’re eventually going to leave, you could
 just
   move to a branch sooner rather than later. It’s unreasonable to
 expect
   WebKit to accommodate a port that has no forward-looking interest
 in the
   project.
   We do have a  branch tagged and being prepared for 5.2. It was taken
   before the FTL merge and the following switch to require C++11 in
 all of
   the project. It will be very hard branch again after that point
 since we
   support 2-3 year old platforms by default, and the Webkit project
 want
   to move to using the latest and greatest compilers.
   So you are saying that you'll never branch QtWebKit from WebKit trunk
   again?
   I would love to, but I do not think it is going to happen. Quite
 honestly I
   wasn't sure I would be able to pull a new branch for 5.2 off, since
 older
   Linux (gcc 4.4), all windows builds and especially old OS X (10.6)
 were not
   building WebKit2 when I started. I got it working, but it the work to
 unroll
   unnecessary compiler features and library dependencies is just going
 to get
   harder from now on (if anyone want a patch to remove the C++11
 requirement
   from WebKit2 late July, I have one).  If a new branch is made from
 WebKit
   trunk in the future would likely only be limited to specific
 platforms, and
   therefore not suited as a module shipped with Qt, but as an optional
 upgrade.
   It’s commendable that you want to land your platform-agnostic patches
   before withdrawing from the project, but assuming your last branch
 point
   is already set, I don’t see why this necessitates keeping the Qt
 platform
   code around.
   We all know what happens when a webkit port works on a branch. In
 theory it
   shouldn't be a problem, but as you know it didn't work for the N9
 browser
   branch in Nokia, it didn't even work for the iOS branch at Apple!
 
   So based on observations, I believe to be part of the project and able
 to
   commit upstream you must live upstream.
 
  I would not necessarily disagree with the problem of upstreaming work.
 But you said that most likely you wouldn't be able to branch WebKit anymore
 because of the compiler requirement.  At least for Qt. Do you have other
 interests in QtWebKit beside the integral part of Qt so that it makes sense
 for you to maintain the port further?
 
  Another question that is just partly related to WebKit but more
 curiosity.  Qt is deep integration into WebKit. We have (had?) a lot of Qt
 specific code in core WebCore to support QtXML and other things. Blink
 already stated that they would not accept such deep interventions in their
 platform. Is all that not important for you anymore? Can you operate with
 libxml2 and other libraries from now on? If that is the case, can't we
 limit the Qt specific code to just /platform/qt and remove all other Qt
 specific dependencies from WebCore?

 For embedded targets libxml2 would be an additional dependency to build,
 and it would take additional space in device firmware. New XML parser from
 [1] would be better alternative if it was finished (and had decent
 performance).

 [1] https://bugs.webkit.org/show_bug.cgi?id=64396

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




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


Re: [webkit-dev] Compilation of Webkit2 on Qt Port

2013-09-17 Thread Arunprasad Rajkumar
Your build environment might be having other WebKit library installed. If
so remove those headers and libraries and try.
On 17 Sep 2013 17:16, murali billa muralibi...@gmail.com wrote:

 Hi,
 Im trying to compile webkit2. For first time, im able to compile
 successfully for Qt port. For 2nd time, it throws below linking error
 (without any code change). Pls help me.


 .obj/release-shared/WebKit/qt/WidgetApi/qwebpage.o:qwebpage.cpp:function
 QWebPage::setVisibilityState(QWebPage::VisibilityState): error: undefined
 reference to

 'QWebPageAdapter::setVisibilityState(QWebPageAdapter::VisibilityState)'
 .obj/release-shared/WebKit/qt/WidgetApi/qwebpage.o:qwebpage.cpp:function
 QWebPag
e::visibilityState() const: error: undefined reference
 to 'QWebPageAdapter::visi
  bilityState() const'



 Regds,
 Murali

 ___
 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] Adding __FILE__ and __LINE__ to CRASH() macro

2013-04-16 Thread Arunprasad Rajkumar
Hi Darin,

Any other concerns? May I file a bug  provide the patch?

BR


On 15 April 2013 16:41, Arunprasad Rajkumar ararunpra...@gmail.com wrote:



 Forwarded conversation
 Subject: Adding __FILE__ and __LINE__ to CRASH() macro
 

 From: *Arunprasad Rajkumar* ararunpra...@gmail.com
 Date: 12 April 2013 15:29
 To: webkit-dev@lists.webkit.org webkit-dev@lists.webkit.org
 Cc: arunpras...@nds.com


 (Hope this is the proper mailing list to ask, Sorry in-case of not)

 Hello Folks,

 In embedded platforms(mostly debugger is missing) it very difficult(for
 us) to debug the issues without proper prints in CRASH macro. Though it has
 WTFReportBacktrace(); due to some constraints we are not getting proper
 call stack information(debug build with -g is costlier for us) .

 So we are thinking to extend the functionality of WTFInvokeCrashHook by
 passing __FILE__  __LINE__ and printing it. Any suggestion?

 If you all agreed then I will create bug and submit a patch.

 Thanks  BR

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

 --
 From: *Darin Adler* da...@apple.com
 Date: 12 April 2013 20:17
 To: Arunprasad Rajkumar ararunpra...@gmail.com, arunpras...@nds.com
 Cc: WebKit Development webkit-dev@lists.webkit.org


 Is this for debug builds or for production builds?

 If it is for debug builds, then adding file and line seems fine; we should
 do it in a way that shares code with assertion macros.

 If it is for production builds, then how do you debug other crashes?

 -- Darin

 --
 From: *Arunprasad Rajkumar* ararunpra...@gmail.com
 Date: 13 April 2013 11:36
 To: Darin Adler da...@apple.com
 Cc: arunpras...@nds.com, WebKit Development webkit-dev@lists.webkit.org


 Hi Darin,

 Is this for debug builds or for production builds?
  It is for production build.


 If it is for debug builds, then adding file and line seems fine; we
 should do it in a way that shares code with assertion macros.
  So in-case of calling CRASH from ASSERT then it shouldn't print __FILE__
 and __LINE__ right(because ASSERT prints all these)?

 If it is for production builds, then how do you debug other crashes?
 printf :(

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




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




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


Re: [webkit-dev] Adding __FILE__ and __LINE__ to CRASH() macro

2013-04-16 Thread Arunprasad Rajkumar
Hi Balazs,

For me this change doesn't seems to be too big or controversial, so I
would say let's go for it ;)

Thank u, I will submit a patch soon :)

BR


On 16 April 2013 14:31, Balazs Kelemen kbal...@webkit.org wrote:

  On 04/16/2013 10:27 AM, Arunprasad Rajkumar wrote:

 Hi Darin,

  Any other concerns? May I file a bug  provide the patch?

  BR


 For me this change doesn't seems to be too big or controversial, so I
 would say let's go for it ;)



 On 15 April 2013 16:41, Arunprasad Rajkumar ararunpra...@gmail.comwrote:



 Forwarded conversation
 Subject: Adding __FILE__ and __LINE__ to CRASH() macro
 

 From: *Arunprasad Rajkumar* ararunpra...@gmail.com
 Date: 12 April 2013 15:29
 To: webkit-dev@lists.webkit.org webkit-dev@lists.webkit.org
 Cc: arunpras...@nds.com


   (Hope this is the proper mailing list to ask, Sorry in-case of not)

  Hello Folks,

  In embedded platforms(mostly debugger is missing) it very difficult(for
 us) to debug the issues without proper prints in CRASH macro. Though it has
 WTFReportBacktrace(); due to some constraints we are not getting proper
 call stack information(debug build with -g is costlier for us) .

  So we are thinking to extend the functionality of WTFInvokeCrashHook by
 passing __FILE__  __LINE__ and printing it. Any suggestion?

  If you all agreed then I will create bug and submit a patch.

   Thanks  BR

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

 --
 From: *Darin Adler* da...@apple.com
 Date: 12 April 2013 20:17
 To: Arunprasad Rajkumar ararunpra...@gmail.com, arunpras...@nds.com
 Cc: WebKit Development webkit-dev@lists.webkit.org


 Is this for debug builds or for production builds?

 If it is for debug builds, then adding file and line seems fine; we
 should do it in a way that shares code with assertion macros.

 If it is for production builds, then how do you debug other crashes?

 -- Darin

  --
 From: *Arunprasad Rajkumar* ararunpra...@gmail.com
 Date: 13 April 2013 11:36
 To: Darin Adler da...@apple.com
 Cc: arunpras...@nds.com, WebKit Development webkit-dev@lists.webkit.org


  Hi Darin,

  Is this for debug builds or for production builds?
  It is for production build.


 If it is for debug builds, then adding file and line seems fine; we
 should do it in a way that shares code with assertion macros.
  So in-case of calling CRASH from ASSERT then it shouldn't print __FILE__
 and __LINE__ right(because ASSERT prints all these)?

 If it is for production builds, then how do you debug other crashes?
  printf :(

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




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




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


 ___
 webkit-dev mailing 
 listwebkit-dev@lists.webkit.orghttps://lists.webkit.org/mailman/listinfo/webkit-dev



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




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


Re: [webkit-dev] Adding __FILE__ and __LINE__ to CRASH() macro

2013-04-13 Thread Arunprasad Rajkumar
Hi Darin,

Is this for debug builds or for production builds?
It is for production build.

If it is for debug builds, then adding file and line seems fine; we
should do it in a way that shares code with assertion macros.
So in-case of calling CRASH from ASSERT then it shouldn't print __FILE__
and __LINE__ right(because ASSERT prints all these)?

If it is for production builds, then how do you debug other crashes?
printf :(



On 12 April 2013 20:17, Darin Adler da...@apple.com wrote:

 Is this for debug builds or for production builds?

 If it is for debug builds, then adding file and line seems fine; we should
 do it in a way that shares code with assertion macros.

 If it is for production builds, then how do you debug other crashes?

 -- Darin




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


Re: [webkit-dev] Thank You

2013-04-03 Thread Arunprasad Rajkumar
Whether Bugs fixing, Feature development will be up-streamed to WebKit
trunk? or it will live with Blink itself?


On 4 April 2013 02:32, Eric Seidel e...@webkit.org wrote:

 I’m writing to say thank you, personally, and on behalf of the Chromium
 project.

 Chromium could not have happened without WebKit and the help of its
 contributors.

 As you likely have seen, Adam just posted
 http://blog.chromium.org/2013/04/blink-rendering-engine-for-chromium.html
 announcing Blink, which is a departure from our previous WebKit
 workflow.

 I hope that others will see Blink as I do: as a chance to take the
 WebKit codebase to exciting new places.  I hope someday that many of
 the ideas we pursue in Blink will find their way into many platforms,
 including WebKit.

 For those interested in the technical details, we’ll be posting more
 of our thoughts and plans to blink-...@chromium.org.

 WebKit and Chromium have a long, shared history, and we hope to
 continue our relationship.  We will be available on #webkit and
 webkit-dev and hope to continue our connections with this great
 community for years to come.

 Thank you again.

 Eric

 p.s. Adam and I are happy to work with other reviewers to remove
 PLATFORM(CHROMIUM) code and other messes we may have caused over the
 years from webkit.org.  Adam and I are still running queues.webkit.org
 and associated EWS/CQ/sherriff-bot and plan to do so for the next few
 weeks as we work to transition them to new owners.
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 https://lists.webkit.org/mailman/listinfo/webkit-dev




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


Re: [webkit-dev] Best way to disable JavaScript

2013-03-18 Thread Arunprasad Rajkumar
On 18 March 2013 13:00, Jochen Eisinger joc...@chromium.org wrote:




 On Sun, Mar 17, 2013 at 8:26 PM, Geoffrey Garen gga...@apple.com wrote:

 Hi folks.

 Currently, we have two different ways to disable JavaScript execution:

 (1) Paste / Drag n Drop / editing: Remove script elements and script
 attributes from untrusted source markup at parse time.

 (2) JavaScript disabled setting / Content Security Policy: Check settings
 and/or CSP at runtime.

 There are problems with mode (2):

 * It breaks features that are implemented in JavaScript.

 The Web Inspector, bookmarklets, extensions, Safari Reader, and Safari
 autofill all run JavaScript. This means that they break when users disable
 JavaScript.


 I'm not sure I understand:

 We only invoke canExecuteScript for scripts in the main world, so running
 extensions (or anything else that's running in an isolated world) should
 not be affected.


Inspector injected scripts will be in main-world right? Sorry in-case I'm
wrong :)


  Also, the actual permission check is done via
 FrameLoaderClient::allowScript and ::allowScriptFromSource, so blocking
 e.g. only scripts from the web, but not from the inspector should also be
 possible.

 best
 -jochen


 As a defense against phishing attacks, mail clients and other web content
 readers disable JavaScript. This means that they can't implement pieces of
 their UI in JavaScript.

 (FWIW, WebKit violates the CSP specification in this regard: Enforcing a
 CSP policy should not interfere with the operation of user-supplied scripts
 such as third-party user-agent add-ons and JavaScript bookmarklets.)

 * It subjects users to XSS attacks.

 Runtime checking mode leaves inert JavaScript in the untrusted document.
 This is a risky proposition. Operations that clone or adopt nodes from the
 untrusted document unwittingly re-vivify that inert JavaScript, subjecting
 the user to attack. Experience shows that this is a difficult programming
 model to get right.

 * It's hard to verify.

 We have 18 different call sites to canExecuteScripts() in WebKit, not
 counting the call sites that pertain to plug-ins. Are you confident we've
 caught all the right places? Do you know if the feature you just added
 needs to call canExecuteScripts()?

 * It's two different ways to do the same thing.

 Simplicity is a goal of the WebKit project.


 Proposal:

 If -- for any reason -- JavaScript is disabled in a given document, the
 document parser will elide all JavaScript. This means that runtime checks
 can be removed.

 One potential downside to this proposal is that it changes the document's
 internal structure. Since the changes are not generally observable, since
 they only take place when we're already making much bigger changes by
 preventing whole scripts from running, and since we haven't seen any
 compatibility problems from our paste / drag n drop / editing behavior in
 this regard, I think this downside is acceptable.

 Another potential downside is that CSP errors will be reported at parse
 time instead of runtime. FWIW, some authors might see this as an upside.

 Any objections?

 Thanks,
 Geoff
 ___
 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




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


Re: [webkit-dev] LLInt without JIT

2013-03-13 Thread Arunprasad Rajkumar
.

  But if you have reason to believe that the LLInt assembly backends will
 be better for your purposes then I think all it will take is hacking
 Platform.h appropriately. If this turns out to be hard, then you should
 file a bug, or even better, I would love to see a patch from you to improve
 the logic in Platform.h to make this use case easier.

  Hope this helps!

  -Filip



   On Mar 8, 2013, at 4:59 PM, Fritz Koenig frkoe...@google.com wrote:

LowLevelInterpreter.asm is processed to create LLIntAssembly.h for
 the built platform.  It appears that if there is no jitting configured[1],
 this will always create the C Loop.

  Is there any way of using the assembly backends to create
 LLIntAssembly.h when not jitting?

  [1]: Source/WTF/wtf/Platform.h:815 /* If the jit is not available,
 enable the LLInt C Loop: */
   ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 https://lists.webkit.org/mailman/listinfo/webkit-dev





 ___
 webkit-dev mailing 
 listwebkit-dev@lists.webkit.orghttps://lists.webkit.org/mailman/listinfo/webkit-dev



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




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


Re: [webkit-dev] [webkit-help] [squirrelfish-dev] How to debug the JIT when it crash

2013-03-05 Thread Arunprasad Rajkumar
I think SH4 JIT(in MSVC) for JSC is not supported for r65000. Are you
developing yourself or using any other patches yet to land? Current truck
supports SH4 JIT only if it is compiled using GCC I guess.

On 5 March 2013 11:35, talking1...@gmail.com wrote:

 Hi Arunprasad,

 ** **

 Thanks for your tips.

 ** **

 ** **

 My environment as following:

 CPU: SH4;

 SVN revision: 65000

 OS:  WINCE

 Tool Chain: MSVS+PB

 JS test case: I cann’t get the single js test case. But I can reproduce it
 as this steps[First access the http://image.baidu.com/, then access
 http://maps.google.de, wait 2-5 minitues, it will crash. The crash type
 is “access violation”].

 ** **

 I have try to debug it, find that the crash was caused by the jit, if we
 disable the JIT feature,  the browser will not crash.

 ** **

 As the test case is very complex and it is hard to be simplify,  so I
 don’t know how to debug it.

 ** **

 I try to print all the emitted instructions, but it is too many for me to
 analyze, after the instructions were emitted, the instruction will be
 repatch or relink, so anybody can give me some suggestion for how to debug
 it.

 ** **

 ** **

 Thanks.

 ** **

 ** **

 *From:* talking1239+caf_=talking1239=126@gmail.com [mailto:
 talking1239+caf_=talking1239=126@gmail.com] *On Behalf Of *Arunprasad
 Rajkumar
 *Sent:* 2013年3月4日 20:28
 *To:* talking1...@gmail.com
 *Cc:* webkit-h...@lists.webkit.org; squirrelfish-...@lists.webkit.org;
 webkit-dev@lists.webkit.org
 *Subject:* Re: [webkit-dev] [webkit-help] [squirrelfish-dev] How to debug
 the JIT when it crash

 ** **

 It will be good to mention CPU, WebKit SVN revision, OS, Tool Chain, JS
 test case name(Sun Spider,..?)..etc so that people can give more
 suggestions.

 On 4 March 2013 16:11, talking1...@gmail.com wrote:

 Hi All, apologies for the spam.

 right now I am trying to fix the jit crash bug, but I don't know how to
 start it, can anyone give me some suggestion? 

 when javascript engine run some special test case, it will run crash.

 I have print all the emited instructions, but the instructions will be
 repatch or relink after it run, so is exist an way or steps for debugging
 it?

 Thanks in advance!

 --

 BGs/Felix Shi




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



 

 ** **

 -- 

 *Arunprasad Rajkumar*

 http://in.linkedin.com/in/ararunprasad




-- 
*Arunprasad Rajkumar*
http://in.linkedin.com/in/ararunprasad
___
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-03-01 Thread Arunprasad Rajkumar
Hi,

Please ignore if it is really out of context.

It would be nice to define a Class by Class
roles/responsibilities/expectations from Platform layer before starting
implementation. May be it is a kind of Class/Function standardization
process :). I agree that currently we have standardized platform specific
interface classes like GraphicsContext, ResourceHandle, ImageFrame,.. but
the issue is each port has its own extensions to those classes to make the
process easier, PSB
class GraphicsContext {
...
#if PLATFORM(QT)
ShadowBlur* shadowBlur();
#endif
...
#if USE(CAIRO)
GraphicsContext(cairo_t*);
#endif
..
#if USE(CG)
void applyStrokePattern();
void applyFillPattern();
void drawPath(const Path);

void drawNativeImage(NativeImagePtr, const FloatSize selfSize,
ColorSpace styleColorSpace, const FloatRect destRect, const FloatRect
srcRect, CompositeOperator = CompositeSourceOver, BlendMode =
BlendModeNormal, ImageOrientation = DefaultImageOrientation);

// Allow font smoothing (LCD antialiasing). Not part of the
graphics state.
void setAllowsFontSmoothing(bool);

void setIsCALayerContext(bool);
bool isCALayerContext() const;

void setIsAcceleratedContext(bool);
#endif

};

How we are going to address these?. After this work whether we have all
these defines?

Kind Regards,
Arun

On 1 March 2013 21:50, Žan Doberšek zandober...@gmail.com wrote:

 On Fri, Mar 1, 2013 at 12:43 PM, Jesus Sanchez-Palencia 
 je...@webkit.orgwrote:

 Hi,

 2013/2/28 Darin Adler da...@apple.com:
  To do this, we need to eliminate dependencies from the platform
 directory to the rest of WebCore.
 
  At this time, we are far from that. Many dependencies on the DOM and
 other such things have crept into the platform directory.

 I would be happy to help fixing this, Darin. Are the bugs blocking
 https://bugs.webkit.org/show_bug.cgi?id=21354 a good-enough to start
 list or is there something more urgent?


 Violations reported by those bugs are most likely still valid. There are
 of course probably other existing violations that haven't been reported yet.

 -Z



 Cheers,
 jesus



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




-- 
*Arunprasad Rajkumar*
http://in.linkedin.com/in/ararunprasad
___
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-03-01 Thread Arunprasad Rajkumar
Hi Balazs,

Then the role of the new platform layer sounds similar like existing one :)
Only it will be moved from Source/WebCore/platform from Source/Platform.
Instead of having extra capabilities under a preprocessor define, why can't
we define a class which has a superset of all platform capabilities, but it
is upto the Platform layer to implement it or leave it umimplemented.

Kind Regards,
Arun

On 1 March 2013 22:45, Balazs Kelemen kbal...@webkit.org wrote:

  On 03/01/2013 06:03 PM, Arunprasad Rajkumar wrote:

 Hi,

  Please ignore if it is really out of context.

  It would be nice to define a Class by Class
 roles/responsibilities/expectations from Platform layer before starting
 implementation. May be it is a kind of Class/Function standardization
 process :). I agree that currently we have standardized platform specific
 interface classes like GraphicsContext, ResourceHandle, ImageFrame,.. but
 the issue is each port has its own extensions to those classes to make the
 process easier, PSB


 If I got it correctly than exactly these are the classes that should leave
 in Platform (among others). The fact that their feature set is not
 equivalent is orthogonal to this. It's a fact that each platform has it's
 own extra capabilities and we should be able to utilize them. Guarding them
 with preprocessor directives and relying on the convention that only
 platform code will actually use them is one way to do this, probably not
 the best.


  class GraphicsContext {
 ...
  #if PLATFORM(QT)
 ShadowBlur* shadowBlur();
 #endif
 ...
 #if USE(CAIRO)
 GraphicsContext(cairo_t*);
 #endif
  ..
  #if USE(CG)
 void applyStrokePattern();
 void applyFillPattern();
 void drawPath(const Path);

  void drawNativeImage(NativeImagePtr, const FloatSize selfSize,
 ColorSpace styleColorSpace, const FloatRect destRect, const FloatRect
 srcRect, CompositeOperator = CompositeSourceOver, BlendMode =
 BlendModeNormal, ImageOrientation = DefaultImageOrientation);

  // Allow font smoothing (LCD antialiasing). Not part of the
 graphics state.
 void setAllowsFontSmoothing(bool);

 void setIsCALayerContext(bool);
 bool isCALayerContext() const;

  void setIsAcceleratedContext(bool);
 #endif

  };

  How we are going to address these?. After this work whether we have all
 these defines?

  Kind Regards,
 Arun

 On 1 March 2013 21:50, Žan Doberšek zandober...@gmail.com wrote:

  On Fri, Mar 1, 2013 at 12:43 PM, Jesus Sanchez-Palencia 
 je...@webkit.org wrote:

 Hi,

 2013/2/28 Darin Adler da...@apple.com:
  To do this, we need to eliminate dependencies from the platform
 directory to the rest of WebCore.
 
  At this time, we are far from that. Many dependencies on the DOM and
 other such things have crept into the platform directory.

  I would be happy to help fixing this, Darin. Are the bugs blocking
 https://bugs.webkit.org/show_bug.cgi?id=21354 a good-enough to start
 list or is there something more urgent?


  Violations reported by those bugs are most likely still valid. There
 are of course probably other existing violations that haven't been reported
 yet.

  -Z



 Cheers,
 jesus



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




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


 ___
 webkit-dev mailing 
 listwebkit-dev@lists.webkit.orghttps://lists.webkit.org/mailman/listinfo/webkit-dev



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




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


Re: [webkit-dev] Possibilities to use border css property on image map...

2013-02-26 Thread Arunprasad Rajkumar
Hi Darin,

Thanks for your response. I will file a bug. Just wanted to ensure whether
it is a real bug or not. From next time can I post it to webkit-help to
ensure the bug?

I filed in webkit bugzilla. https://bugs.webkit.org/show_bug.cgi?id=110940

Kind Regards,
Arun

On 26 February 2013 22:30, Darin Adler da...@apple.com wrote:

 On Feb 25, 2013, at 11:26 PM, Arunprasad Rajkumar ararunpra...@gmail.com
 wrote:

  So I tried using :focus { border:5px solid red; }. But it is not working
 in WebKit based browsers. But border property works well for all other
 elements(a,div,span,p,..) but not with area.

 Thanks fore the bug report. However, mail to this mailing list is not the
 correct way to report a bug.

 The right way to do that is to use http://bugs.webkit.org to file a bug
 report. Please do that.

 Other information about how to correctly keep in touch with the people
 working on WebKit is on the contact page at
 http://www.webkit.org/contact.html with information about the mailing
 lists and more.

 -- Darin




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


Re: [webkit-dev] Script Execution in webkit

2013-02-23 Thread Arunprasad Rajkumar
Some basics I understood about JS execution in WebKit.

JavaScript execution inside a browser is event driven. Event may be fired
from multiple source like Mouse,
Keyboard,Timer(window.setInterval,window.setTimeout), XHR, DOM... Also
WebKit executes javascript in a mainthread(in case of worker context it
will be executed from respective worker thread) and script is
not yieldable at any point. Control will reach to mainloop only after
executing the complete flow(Suppose script execution starts from
a()-b()-c()-d(), you can't yield the execution at any intermediate
point).

Please find my reply below,

On 23 February 2013 18:26, Vicky Tux sssein...@gmail.com wrote:


 1. Is there any possibility to identify whether any script executing
 currently or not?


[ARUN] Not possible. If script is being executing then mainthread will be
blocked. You can add your own traps to
ScriptController::evaluateInWorld(Refer
InspectorInstrumentation::willEvaluateScript
 InspectorInstrumentation::didEvaluateScript). But you should check the
status from another thread to know the browser mainthread is executing
script or not. But what will you do with that status?, beware you can't
yield/disable it from another thread.

2. Is webkit supporting to pause and resume script execution?

[ARUN] WebKit supports only disabling the script execution via Settings.
You may wonder like how WebInspector's pause script execution works!!!.
It is completely different story :(.

3. Will disabling execution through simply setting
 setJavaScriptEnabled(false) and enabling by reverting it causes any
 misbehavior in script execution?

[ARUN] That is depends on the page being executing. Incase page has timing
dependent execution flow(timers) then it may misbehave.


 Thanks,
 Ameen.

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


(If it has any faults, please correct me:) )

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


Re: [webkit-dev] Access WebKit Rendering pixel data

2013-02-18 Thread Arunprasad Rajkumar
yes :). WebKit is not a library, so it don't have defined form of API
exposed. The one who _uses_ WebCore(WebCore+WTF+JSC/V8) called as Embedders
have some form of API, but again it is up-to them to expose the level of
control to outside. Embedders call their work by different names like
QtWebKit, GTK WebKit, EFL WebKit,...  they may provide as libraries. All
have some level of documented Public API for its users.

Refer,

GTK WebKit - http://webkitgtk.org/?page=documentation
QtWebKit - http://qt-project.org/doc/qt-4.8/qtwebkit.html
EFL WebKit Start-up Guide -
http://www.politreco.com/2010/10/easily-embedding-webkit-into-your-efl-application/

If you already choose some library, then make your question specific and
post it to appropriate mailing listhttps://lists.webkit.org/mailman/listinfo.
webkit-dev is not the right place to ask this question :)

On 18 February 2013 22:04, Michael Chen michael8...@yahoo.com wrote:

 Thanks for the reply. What you saying is that there is no clean way to do
 it in WebKit itself, I will have to go to the platform specific code to do
 it.

 Best,
 Michael

   --
 *From:* Arunprasad Rajkumar ararunpra...@gmail.com
 *To:* Michael Chen michael8...@yahoo.com
 *Cc:* webkit-dev@lists.webkit.org webkit-dev@lists.webkit.org
 *Sent:* Saturday, February 16, 2013 5:51 AM
 *Subject:* Re: [webkit-dev] Access WebKit Rendering pixel data

 Are you talking about Rendered buffer? It is graphics library specific.
 From which layer you wanted to access? Each WebKit
 port(qt,gtk,chromium,efl,wx,mac) has their own API exposed to the app
 developers. Incase of Qt QWebView is a QWidget and you can use
 http://doc.qt.digia.com/qt/qwidget.html#render
 to get the rendered buffer as QPixmap object. In GTK port you can get the
 Cairo context and copy it to the Cairo_image_t(pixman backed Cairo surface).
 On Feb 16, 2013 8:23 AM, Michael Chen michael8...@yahoo.com wrote:
 
  Hi All,
 
  I am new to WebKit. Is it possible to get a raw pointer to the WebKit
 rendering buffer?
 
  I appreciate any comments.
 
  Best regards,
  Michael
 
  ___
  webkit-dev mailing list
  webkit-dev@lists.webkit.org
  https://lists.webkit.org/mailman/listinfo/webkit-dev
 





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


Re: [webkit-dev] Access WebKit Rendering pixel data

2013-02-18 Thread Arunprasad Rajkumar
Yes :) Thanks for your better explanation  correction.

On 19 February 2013 00:04, Martin Robinson mrobin...@webkit.org wrote:

 On Mon, Feb 18, 2013 at 9:57 AM, Arunprasad Rajkumar
 ararunpra...@gmail.com wrote:
  yes :). WebKit is not a library, so it don't have defined form of API
  exposed. The one who _uses_ WebCore(WebCore+WTF+JSC/V8) called as
 Embedders
  have some form of API, but again it is up-to them to expose the level of
  control to outside. Embedders call their work by different names like
  QtWebKit, GTK WebKit, EFL WebKit,...  they may provide as libraries. All
  have some level of documented Public API for its users.

 A small clarification: The ports are not embedders.

 It's true that WebKit, the project, is not a library. It is a code
 base and a community. Certain ports of WebKit are libraries or
 embedding APIs, such as Mac Webkit, QtWebKit, EFLWebKit and
 WebKitGTK+. Because of the history of the WebKit project, the Mac port
 is sometimes just called WebKit. You can think of the ports as
 WebKit implemented for a particular platform. These port libraries
 expose WebKit in slightly different ways depending on the culture and
 needs of the communities in which they exist. Applications that use a
 WebKit library to show a WebView or otherwise access web content are
 called embedders.

 Since this discussion is not about development of WebKit internals,
 it's probably better to move it to webkit-help.

 --Martin




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


Re: [webkit-dev] Access WebKit Rendering pixel data

2013-02-16 Thread Arunprasad Rajkumar
Are you talking about Rendered buffer? It is graphics library specific.
From which layer you wanted to access? Each WebKit
port(qt,gtk,chromium,efl,wx,mac) has their own API exposed to the app
developers. Incase of Qt QWebView is a QWidget and you can use
http://doc.qt.digia.com/qt/qwidget.html#render
to get the rendered buffer as QPixmap object. In GTK port you can get the
Cairo context and copy it to the Cairo_image_t(pixman backed Cairo surface).

On Feb 16, 2013 8:23 AM, Michael Chen michael8...@yahoo.com wrote:

 Hi All,

 I am new to WebKit. Is it possible to get a raw pointer to the WebKit
rendering buffer?

 I appreciate any comments.

 Best regards,
 Michael

 ___
 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] Media Server Development

2013-01-31 Thread Arunprasad RajKumar
Basically WebKit runs in the event thread(main thread) of the porting(qt,gtk). 
WebKit node data structures will be created and destroyed only from the 
mainthread. Also WebKit's timer scheduled from the main thread. Are u running 
multiple instance of webview from multiple  threads? If so it shouldn't be done 
like tat. You can check the thread id of duration and destrutor's caller if u r 
not sure.

Sent from my Xperia™ smartphone 

Kiran K kiran.pe...@gmail.com 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] 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 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


Re: [webkit-dev] Reg.use of WTF_CHANGES in FastMalloc.cpp...

2012-04-13 Thread Arunprasad Rajkumar
Hi Eric, Morrita   All,

Thanks for answering.

I understand like FastMalloc is derived from google's perf-tool TCMalloc to
avoid one more dependency. Unused codes were kept inside  WTF_CHANGES to
ease the merging of new versions of TCMalloc.

But why don't we enable the statistics(allocated objects,committed virtual
memory from OS) here? Similar to *about:tcmalloc in google chrome.* Hope
this will help to identify the leaks  memory growth of webkit.


On 12 April 2012 14:59, Eric Seidel e...@webkit.org wrote:

 FastMalloc is a fork of tcmalloc:
 http://trac.webkit.org/browser/trunk/Source/WTF/wtf/FastMalloc.cpp#L37
 http://goog-perftools.sourceforge.net/doc/tcmalloc.html
 from several years ago.

 On Thu, Apr 12, 2012 at 2:11 AM, Hajime Morrita morr...@chromium.org
 wrote:
  Hi,
 
  The code was brought from a third party library and WebKit (WTF) needs
  some changes to the original code. It looks such changes are marked by
  WTF_CHANGES. For example, WTF shouldn't depend on gflags, which is
  disabled by the WTF_CHANGES guard.
 
  --
  morrita
 
  On Thu, Apr 12, 2012 at 6:01 PM, Arunprasad Rajkumar
  ararunpra...@gmail.com wrote:
  I don't understand the use of define  WTF_CHANGES in FastMalloc.cpp 
  TCSystemAlloc.cpp.
 
  Any body help me to understand that?
 
  Thanks in advance.
 
  --
  Arunprasad Rajkumar
  ___
  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




-- 
*Arunprasad Rajkumar*
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


[webkit-dev] Reg.use of WTF_CHANGES in FastMalloc.cpp...

2012-04-12 Thread Arunprasad Rajkumar
I don't understand the use of define  WTF_CHANGES in FastMalloc.cpp 
TCSystemAlloc.cpp.

Any body help me to understand that?

Thanks in advance.

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


Re: [webkit-dev] Reg. New File Inclusion Style for Webkit

2011-12-04 Thread Arunprasad Rajkumar
yes, this will yield a good results for build time. I would like to get
more comments from other developers regarding this.

On 21 November 2011 06:24, Peter Kasting pkast...@google.com wrote:

 On Sun, Nov 20, 2011 at 1:57 AM, Arunprasad Rajkumar 
 ararunpra...@gmail.com wrote:

 Why don't we follow chrome style of file inclusions rather than the usual.

 For example,
 *#include WebCore/Page/Chrome.h*

 This will be more convient way of representing the inclusion. Hope it
 will avoid long compiler inclusion paths and file namespace issues.


 Here are some pros and cons I can think of:

 Pros:
 * If used pervasively, would allow us to greatly trim the compiler include
 search paths, possibly providing a noticeable build speedup (I have no
 estimated numbers).
 * Makes it slightly more obvious to a reader what, precisely, is being
 depended upon; might make it easier to notice layering violations.

 Cons:
 * Would require us to convert the existing codebase (possibly easy with
 the help of a script, but would at least result in touching all the files)
 * Generates more change noise when a header is moved around
 * Could pose problems for ports that need to supply particular headers
 from some override directory instead of the typical spot.  (I'm being
 vague here because I think this is probably a real issue but I don't
 actually know the details of enough ports' build setups to be clear.)

 I would prefer the full-path style myself, especially if there is really a
 build-time win, but I strongly suspect that a lot of folks would see the
 benefit here as not worth the cost.

 PK

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


[webkit-dev] Reg. New File Inclusion Style for Webkit

2011-11-20 Thread Arunprasad Rajkumar
Hi All,

Why don't we follow chrome style of file inclusions rather than the usual.

For example,
*#include WebCore/Page/Chrome.h*

This will be more convient way of representing the inclusion. Hope it will
avoid long compiler inclusion paths and file namespace issues.

Please comment.

Regards,
Arun.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Reg. Multi-tap keyboard entry implementation in Webkit

2011-11-17 Thread Arunprasad Rajkumar
Hi Anurag,

Thanks for your reply. I'm using Webkit 1  cairo as a GraphicsContext.

Regards,
Arun.

On 16 November 2011 15:38, Anurag Dak anurag...@gmail.com wrote:

 Hi Arun,

 If that is the case you need to register a flag / Mode for  Mutlitap in
 webkit which can be on/off
 through a API.{ which engine you want to use Webkit 1/ Webkit 2 because
 you need to register that API }
 After that you need to bypass the events where you got keyboard event
 [revert me with the version{1/2} , i will tell what are
 the locations for keyboard events] and a timer is required which propagate
 events after desired delay.





 Regards,
 Anurag


 On Wed, Nov 16, 2011 at 2:05 PM, Arunprasad Rajkumar 
 ararunpra...@gmail.com wrote:

 Hi Anurag  webkit team,

 I actually don't want to create any UI for multi-tap entry. Just need to
 implement the functionality as like SMS multi-tap keyboard entry. To
 achieve this I should feed the char to text box equvalent controls, but
 keyevents should be generated only after particular timeout. Please help me
 to feed the character to text box without generating key events.

 regards,
 Arun

 On 14 November 2011 18:43, webkit-help-requ...@lists.webkit.org wrote:

 Message: 3
 Date: Mon, 14 Nov 2011 17:01:12 +0530
 From: Anurag Dak anurag...@gmail.com
 To: webkit-h...@lists.webkit.org
 Subject: [webkit-help] Reg. Multi-tap keyboard entry implementation in
webkit.
 Message-ID:

 calxalghtrowtb1q_uwsmn9mapdxqgssc+6znyuazogblksh...@mail.gmail.com
 Content-Type: text/plain; charset=iso-8859-1

 Hi,
 For  Multi-tap keyboard entry implementation in  webkit.
 Can you elaborate you question.

 As i think want to create a Multi-tap  UI [ in any graphics library ] and
 sent the respective events.
 to webkit to process.

 Regards,
 Anurag Dak

 On Sun, Nov 13, 2011 at 8:30 PM, webkit-help-requ...@lists.webkit.org
 wrote:

  Message: 2
  Date: Sun, 13 Nov 2011 12:56:06 +0530
  From: Arunprasad Rajkumar ararunpra...@gmail.com
  To: webkit-dev@lists.webkit.org, webkit-h...@lists.webkit.org
  Subject: [webkit-help] Reg. Multi-tap keyboard entry implementation in
 webkit...
  Message-ID:
 CACDxuFwD_JSgSQw-1N17qH_hM6N0KKtN_DgY=
 sqdokjxaaw...@mail.gmail.com
  
  Content-Type: text/plain; charset=iso-8859-1
 
  Hi Folks,
 
  How complex is to implement Multi-Tap keyboard entry support in
 Webkit...?
 
  Could any one help me how to start this implementation..?
 
  Expecting kind support.
 
  Regards,
  Arun.




 --
 Regards,
 Anurag Dak
 9582176821
 *Hope is a good thing, May be the best of the thing; and no good thing
 ever dies - Shaw shank Redemption*


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


Re: [webkit-dev] Reg. Multi-tap keyboard entry implementation in Webkit

2011-11-16 Thread Arunprasad Rajkumar
Hi Anurag  webkit team,

I actually don't want to create any UI for multi-tap entry. Just need to
implement the functionality as like SMS multi-tap keyboard entry. To
achieve this I should feed the char to text box equvalent controls, but
keyevents should be generated only after particular timeout. Please help me
to feed the character to text box without generating key events.

regards,
Arun

On 14 November 2011 18:43, webkit-help-requ...@lists.webkit.org wrote:

 Message: 3
 Date: Mon, 14 Nov 2011 17:01:12 +0530
 From: Anurag Dak anurag...@gmail.com
 To: webkit-h...@lists.webkit.org
 Subject: [webkit-help] Reg. Multi-tap keyboard entry implementation in
webkit.
 Message-ID:
calxalghtrowtb1q_uwsmn9mapdxqgssc+6znyuazogblksh...@mail.gmail.com
 
 Content-Type: text/plain; charset=iso-8859-1

 Hi,
 For  Multi-tap keyboard entry implementation in  webkit.
 Can you elaborate you question.

 As i think want to create a Multi-tap  UI [ in any graphics library ] and
 sent the respective events.
 to webkit to process.

 Regards,
 Anurag Dak

 On Sun, Nov 13, 2011 at 8:30 PM, webkit-help-requ...@lists.webkit.org
 wrote:

  Message: 2
  Date: Sun, 13 Nov 2011 12:56:06 +0530
  From: Arunprasad Rajkumar ararunpra...@gmail.com
  To: webkit-dev@lists.webkit.org, webkit-h...@lists.webkit.org
  Subject: [webkit-help] Reg. Multi-tap keyboard entry implementation in
 webkit...
  Message-ID:
 CACDxuFwD_JSgSQw-1N17qH_hM6N0KKtN_DgY=
 sqdokjxaaw...@mail.gmail.com
  
  Content-Type: text/plain; charset=iso-8859-1
 
  Hi Folks,
 
  How complex is to implement Multi-Tap keyboard entry support in
 Webkit...?
 
  Could any one help me how to start this implementation..?
 
  Expecting kind support.
 
  Regards,
  Arun.

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


[webkit-dev] Reg. Multi-tap keyboard entry implementation in webkit...

2011-11-12 Thread Arunprasad Rajkumar
Hi Folks,

How complex is to implement Multi-Tap keyboard entry support in Webkit...?

Could any one help me how to start this implementation..?

Expecting kind support.

Regards,
Arun.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


[webkit-dev] Reg. Multi-tap keyboard entry implementation in webkit...

2011-11-05 Thread Arunprasad Rajkumar
Hi Folks,

How complex is to implement Multi-Tap keyboard entry support in Webkit...?

Could any one help me how to start this implementation..?

Expecting kind support.

Regards,
Arun.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev