Re: [webkit-dev] Feature Announcement: IndieUI: Events

2013-03-05 Thread UdayKiran Reddy 
https://bugs.webkit.org/show_bug.cgi?id=111446


On Tue, Mar 5, 2013 at 6:07 PM, James Robinson  wrote:

>
>
> On Tue, Mar 5, 2013 at 9:11 AM, Chris Fleizach wrote:
>
>> Hello,
>>
>> I'm planning on implementing the IndieUI Events 1.0 W3C spec
>> https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-events.html
>>
>
>>
>> This feature's primary goal is to allow assistive technologies (like a
>> Screen reader) a way to control certain events that normally rely on a
>> standard device, but it's abstract enough that it will be useful in other
>> contexts.
>>
>> Example: The escape key on a keyboard might be used to dismiss a dialog,
>> but an assistive technology might not be able to press the escape key.
>>
>> The spec's introduction states:
>>
>> IndieUI: Events 1.0 is an abstraction between physical, device-specific
>> user interaction events and inferred user intent such as scrolling or
>> changing values. This provides an intermediate layer between device- and
>> modality-specific user interaction events, and the basic user interface
>> functionality used by web applications. IndieUI: Events focuses on granular
>> user interface interactions such as scrolling the view, canceling an
>> action, changing the value of a user input widget, selecting a range,
>> placing focus on an object, etc. Implementing platforms will combine
>> modality-specific user input, user idiosyncratic heuristics to determine
>> the specific corresponding Indie UI event, and send that to the web
>> application in addition to the modality-specific input such as mouse or
>> keyboard events, should applications wish to process it.
>>
>>
>> The WebKit bug can be found here
>> https://bugs.webkit.org/show_bug.cgi?id=111446
>>
>
> This bug appears to be a closed issue about speech synthesis, not IndieUI.
>  Do you have a link to the IndieUI tracking bug?  Thanks!
>
> - James
>
>
>>
>>
>> The feature flag I plan on using is
>> INDIEUI_EVENTS
>>
>> Let me know if you have any questions.
>>
>> Thanks
>>
>> ___
>> 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] Feature Announcement: IndieUI: Events

2013-03-05 Thread James Robinson 
On Tue, Mar 5, 2013 at 9:11 AM, Chris Fleizach  wrote:

> Hello,
>
> I'm planning on implementing the IndieUI Events 1.0 W3C spec
> https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-events.html
>

>
> This feature's primary goal is to allow assistive technologies (like a
> Screen reader) a way to control certain events that normally rely on a
> standard device, but it's abstract enough that it will be useful in other
> contexts.
>
> Example: The escape key on a keyboard might be used to dismiss a dialog,
> but an assistive technology might not be able to press the escape key.
>
> The spec's introduction states:
>
> IndieUI: Events 1.0 is an abstraction between physical, device-specific
> user interaction events and inferred user intent such as scrolling or
> changing values. This provides an intermediate layer between device- and
> modality-specific user interaction events, and the basic user interface
> functionality used by web applications. IndieUI: Events focuses on granular
> user interface interactions such as scrolling the view, canceling an
> action, changing the value of a user input widget, selecting a range,
> placing focus on an object, etc. Implementing platforms will combine
> modality-specific user input, user idiosyncratic heuristics to determine
> the specific corresponding Indie UI event, and send that to the web
> application in addition to the modality-specific input such as mouse or
> keyboard events, should applications wish to process it.
>
>
> The WebKit bug can be found here
> https://bugs.webkit.org/show_bug.cgi?id=111446
>

This bug appears to be a closed issue about speech synthesis, not IndieUI.
 Do you have a link to the IndieUI tracking bug?  Thanks!

- James


>
>
> The feature flag I plan on using is
> INDIEUI_EVENTS
>
> Let me know if you have any questions.
>
> Thanks
>
> ___
> 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] Heads-up: C++11 and WebKit2

2013-03-05 Thread Benjamin Poulain 
On Tue, Mar 5, 2013 at 3:48 PM, Kenneth Rohde Christiansen <
kenneth.christian...@gmail.com> wrote:

> I am personally happy that we can make use of C++11 and I don't
> suppose it is a problem for the Tizen/EFL port. On the other hand, I
> fear that Qt might be targeting some platforms where this could be an
> issue. According to http://qt-project.org/wiki/Qt_5.0 they are still
> aiming at supporting Windows XP as a Tier 1 platform.
>

WebKit2 already requires XP SP2 or above. Can't MSVC 2010 target that?

I welcome the adoption of more C++ 11 in WebKit2. The TODO list of
things-we-can-do-better-when-we-will-have-C++-11 is depressingly growing.

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

Re: [webkit-dev] Heads-up: C++11 and WebKit2

2013-03-05 Thread Kenneth Rohde Christiansen 
Hi there,

I am personally happy that we can make use of C++11 and I don't
suppose it is a problem for the Tizen/EFL port. On the other hand, I
fear that Qt might be targeting some platforms where this could be an
issue. According to http://qt-project.org/wiki/Qt_5.0 they are still
aiming at supporting Windows XP as a Tier 1 platform.

Cheers
Kenneth

On Tue, Mar 5, 2013 at 11:21 PM, Anders Carlsson  wrote:
> Hello everyone,
>
> Some time ago we started using C++11 in the Mac port of WebKit2. In the near 
> future we’re going to expand our use of C++11 in the WebKit2 codebase. 
> Specifically, we’d like to make use of rvalue references and move semantics 
> in our IPC code to avoid needlessly copying data and to give some 
> serializable objects (such as Mach ports) better semantics.
>
> If you’re a port that is building WebKit2, you're probably already building 
> with a compiler that supports rvalue references; according to 
> http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport, support for move 
> semantics exists in Visual Studio 2010 and later, as well as GCC 4.3 and 
> later (and any reasonable modern version of clang).
>
> - Anders
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev



-- 
Kenneth Rohde Christiansen
Senior Engineer, WebKit, Qt, EFL
Phone  +45 4294 9458 / E-mail kenneth at webkit.org

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

[webkit-dev] WebKit Contributors Meeting - Save the Date

2013-03-05 Thread Sam Weinig 
Hi all,

Apple will once again be hosting a WebKit Contributors Meeting. It will be held 
at the DoubleTree by Hilton Hotel in San Jose on Thursday, May 2nd and Friday, 
May 3rd. As with the meeting in previous years, this event will have an 
"unconference"-like format, allowing plenty of time for impromptu 
sessions/discussions and hacking.

We will open registration in the coming weeks. The meeting will be free of 
charge. All WebKit contributors are encouraged to attend.

We hope to see you there!

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

[webkit-dev] Heads-up: C++11 and WebKit2

2013-03-05 Thread Anders Carlsson 
Hello everyone,

Some time ago we started using C++11 in the Mac port of WebKit2. In the near 
future we’re going to expand our use of C++11 in the WebKit2 codebase. 
Specifically, we’d like to make use of rvalue references and move semantics in 
our IPC code to avoid needlessly copying data and to give some serializable 
objects (such as Mach ports) better semantics. 

If you’re a port that is building WebKit2, you're probably already building 
with a compiler that supports rvalue references; according to 
http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport, support for move 
semantics exists in Visual Studio 2010 and later, as well as GCC 4.3 and later 
(and any reasonable modern version of clang).

- Anders

___
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 Darin Adler 
On Mar 4, 2013, at 2:41 AM, talking1...@gmail.com wrote:

> Hi All, apologies for the spam.

Please, it’s not acceptable to cross-post to all three of lists to ask for help 
debugging a problem. If we all did that we’d have tons of traffic on these 
mailing lists.

Stop!

Please at least narrow this down to just the webkit-help list, or better please 
use a bug report for this discussion instead.

-- Darin
___
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,  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,  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

[webkit-dev] Feature Announcement: IndieUI: Events

2013-03-05 Thread Chris Fleizach 
Hello,

I'm planning on implementing the IndieUI Events 1.0 W3C spec
https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-events.html

This feature's primary goal is to allow assistive technologies (like a Screen 
reader) a way to control certain events that normally rely on a standard 
device, but it's abstract enough that it will be useful in other contexts.

Example: The escape key on a keyboard might be used to dismiss a dialog, but an 
assistive technology might not be able to press the escape key.

The spec's introduction states:

IndieUI: Events 1.0 is an abstraction between physical, device-specific user 
interaction events and inferred user intent such as scrolling or changing 
values. This provides an intermediate layer between device- and 
modality-specific user interaction events, and the basic user interface 
functionality used by web applications. IndieUI: Events focuses on granular 
user interface interactions such as scrolling the view, canceling an action, 
changing the value of a user input widget, selecting a range, placing focus on 
an object, etc. Implementing platforms will combine modality-specific user 
input, user idiosyncratic heuristics to determine the specific corresponding 
Indie UI event, and send that to the web application in addition to the 
modality-specific input such as mouse or keyboard events, should applications 
wish to process it.


The WebKit bug can be found here
https://bugs.webkit.org/show_bug.cgi?id=111446

The feature flag I plan on using is
INDIEUI_EVENTS

Let me know if you have any questions.

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

Re: [webkit-dev] Proposal: Add a region-selectable timeline in Web Inspector CPU profile panel.

2013-03-05 Thread Patrick Mueller 
On 3/5/13 6:41 AM, Deng, Pan wrote:
> ...
> For JS CPU-profile panel, I think a selectable region that allow
> exploring any part of aggregated data is a helpful, that is a different
> view from breakdown details. And it is also common used among profilers,
> ...

It seems like profiling is an area that would benefit from additional
experimentation from users.  For instance, see my experiments with
rsprofiler: http://pmuellr.github.com/rsprofiler/

Interesting that I was able to build this just from console.profile(),
console.profileEnd(), and then accessing console.profiles for the profiling
data.  This only works for Safari though.  I never seem to get more than
the "head" node from Chrome.

I suspect the data in console.profiles would also be a different format
between Safari and Chrome, as Safari seems to be making use of dtrace for
their data collection, and presumably Chrome wouldn't (at least, say, on
Windows).

So it would be nice to have that data standardized.  Or at least the head
node from the profile data could indicate the style/format of the remainder
of the profile data (eg, "counts" vs "samples" - or maybe "safari-2.3" vs
"chrome-1.7").

The last bit is making it easier for developers to be able to visualize
their profiling data however they want to.  For Chrome, I think the easy
story there is to make the data available via the Chrome Dev Tools
extensions points.  I don't think Safari has extensions for Web Inspector
(like Chrome does for Dev Tools).  So, everyone but Chrome users would be
stuck doing the nasty bits I did for rsprofiler.  But someone could write a
Chrome extension to create a new panel to start/stop profiling, and then
render the visualization of the data how they want.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev