Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
This also makes making certain changes to base exceedingly difficult
because of the circular dependency. For example, you include
base/values. This means that nobody can now change any part of
base/values since webrtc is pulled at a specific revision from a
different repository. In the past this has had a significant impact on
our ability to make improvements, and we've worked hard to reduce the
instances of these dependencies.
Congrats on the launch!I just noticed that the code in third_party/webrtc directly includes code from chrome (I mean all of the chrome code, not just src/chrome, i.e. also src/base, src/content)
I see the base/values usage is from libjingle which you didn't write.
But the same problem applies to your content includes. Actually, it's
worse since content changes much faster than base.
There also appears to be another copy of libvpx inside webrtc.
Hello Chromium developers,
At first I would like to thank you all for such an awesome browser!
I am new to this project, but WebRTC is extremely interesting subject
Unfortunately I could not find /src/third_party/webrtc directory in my
today's git clone. Is there probably another repo with WebRTC
I would like to see the changes in WebKit and in the browser as well..
Is it planned to integrate WebRTC into original WebKit our Chromium
will use its own WebKit tree?
> All details about WebRTC in general can be found athttp://www.webrtc.org/.
On 18 июн, 00:00, Henrik Andreasson <henr...@chromium.org> wrote:
> We would like to announce that a new open source project is about to land in
> Our goal is to enable Chrome with Real-Time Communications (RTC)
> RTC support in Chrome all the way from WebKit down to the native audio and
> video parts. When we are done, any web developer shall be able to create RTC
> applications, like the Google Talk client in Gmail, without using any
> plugins but only WebRTC components that runs in the sandbox.