Re: [webkit-dev] Lots of “BREW” patches up for review

2010-01-22 Thread KwangYul Seo
I changed the platform defines from BREW to BREWMP to match the official port name. As BREWMP is backward compatible with BREW, there is no much differences. As Eric mentioned, a port without the DRT and a working buildbot is too fragile We will upstream the DRT implementation to webkit.org ASAP

Re: [webkit-dev] Lots of “BREW” patches up for review

2010-01-22 Thread KwangYul Seo
I will update the patches with BREW_MP tag. Thanks, Kwang Yul Seo On Sat, Jan 23, 2010 at 3:00 AM, David Levin wrote: > Based on this, it sounds like all [BREW] patches should be r-'ed and > appropriate BREW_MP ones submitted? > > On Sun, Jan 17, 2010 at 6:23 PM, KwangYul Seo > wrote: >> >> [1

Re: [webkit-dev] Lots of “BREW” patches up for review

2010-01-19 Thread KwangYul Seo
Git over HTTP seems to be too slow. Use git protocol instead. git-clone git://www.dorothybrowser.com/WebKitBrew.git On Wed, Jan 20, 2010 at 10:09 AM, KwangYul Seo wrote: > I opened a public git repository for WebKit BREW MP port. Third party > libraries are available in ThirdPartyLibraries dire

Re: [webkit-dev] Lots of “BREW” patches up for review

2010-01-19 Thread KwangYul Seo
I opened a public git repository for WebKit BREW MP port. Third party libraries are available in ThirdPartyLibraries directory. You can get the source code from the following location with git-clone: http://www.dorothybrowser.com/git/WebKitBrew.git The port is complete, but minimal. It contains a

Re: [webkit-dev] Lots of “BREW” patches up for review

2010-01-17 Thread KwangYul Seo
[1] NDA I checked the issue with Qualcomm and drew two conclusions: 1) For BREW MP, we can open source our code without any limitation. 2) For BREW, it is not clear if we can open source our code or not due to the NDA with Qualcomm. Hosting and distributing the code can cause a potential problem

Re: [webkit-dev] Lots of “BREW” patches up for review

2010-01-14 Thread KwangYul Seo
Sure. I will open a public Git repository for potential reviewers. I need to clean up the code before opening the complete source code because some device-specific information is from a phone manufacturer under NDA. I think it will take one or two days.Third party libraries with BREW specific patch

Re: [webkit-dev] Lots of “BREW” patches up for review

2010-01-14 Thread Adam Treat
You have a complete port of BREW already? Interesting. Can you point to the complete sources so potential reviewers can have a look at what the state is? On Thursday 14 January 2010 07:02:24 am KwangYul Seo wrote: > I created a wiki for the BREW port of WebKit. > > https://trac.webkit.org/wiki/

Re: [webkit-dev] Lots of “BREW” patches up for review

2010-01-14 Thread KwangYul Seo
I created a wiki for the BREW port of WebKit. https://trac.webkit.org/wiki/BREW Currently it contains preliminary information. I will add more contents gradually. Thanks, Kwang Yul Seo On Thu, Jan 14, 2010 at 9:22 AM, Ariya Hidayat wrote: >> This is not a one-time code drop. We want to mainta

Re: [webkit-dev] Lots of “BREW” patches up for review

2010-01-14 Thread KwangYul Seo
Okay. I will add a new wiki page for the BREW port. Thanks. Regards, Kwang Yul Seo On Thu, Jan 14, 2010 at 9:22 AM, Ariya Hidayat wrote: >> This is not a one-time code drop. We want to maintain the BREW port >> ongoing and will do everything that are required to keep the BREW port >> up and runn

Re: [webkit-dev] Lots of “BREW” patches up for review

2010-01-14 Thread KwangYul Seo
I will check the issue as soon as possible and let you know the result. In case there is a legal problem with BREW with regard to NDA, BREW MP can be used instead because BREW MP is an open platform. On Thu, Jan 14, 2010 at 6:27 AM, Holger Freyther wrote: > On Wednesday 13 January 2010 18:23:21

Re: [webkit-dev] Lots of “BREW” patches up for review

2010-01-13 Thread KwangYul Seo
Hi, I am Kwang Yul Seo and I work for Company 100, Inc. (http://www.company100.net). I have started to submit patches that are required to port WebKit to Qualcomm's BREW platform. This is not a one-time code drop. We want to maintain the BREW port ongoing and will do everything that are required