Re: [webkit-dev] failed when install webkit in Linux Ubuntu 7.10

2007-11-13 Thread Holger Freyther


Am 13.11.2007 um 10:45 schrieb SUN:

I install webkit in my linux Ubuntu 7.10 following the instruct  
http://mondaybynoon.com/2007/04/23/installing-and-running-webkit-in- 
linux-using-qt/
I get an error when I run the instruct : WebKit/WebKitTools/Scripts/ 
build-webkit
The error is : Unsupported platform, can't determine built library  
locations.


Who can help me?


Hi,

better trust the sources that have webkit.org in their name. E.g. try  
http://trac.webkit.org/projects/webkit/wiki/BuildingQtOnLinux.


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


[webkit-dev] About webkit building for Windows, why need to download additional libraries

2007-11-13 Thread 周毅书
Hi, all
   I downloaded webkit building for windows, and i can build it. When build
it on windows platform, why we need additional libraires(downloaded by
WebKitSupportLibrary.zip), why not use win32 standard libraries directly?
And more, where can i get those libraries source code.
   Any help will be appreciated! Ths!

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


[webkit-dev] Page load failure event

2007-11-13 Thread Naiem Shaik
Hi ,
I am working with the Gtk+port, there is an event load_done which is
emitted along with value false when the page loading has failed. Are
there any flags to indicate the reason of failure.

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


Re: [webkit-dev] Moving away from qmake

2007-11-13 Thread Maciej Stachowiak


On Nov 12, 2007, at 1:26 PM, Timothy Hatcher wrote:

We could add a script that would add/remove/rename files in all the  
project files for the various build systems.


Yeah, that's what I had in mind, more than a meta-build-system. If we  
had that, it would remove 90% of the pain of multiple build systems.  
Adding new generated source files could still be an issue, though.


Cheers,
Maciej



On Nov 12, 2007, at 1:19 PM, David D. Kilzer wrote:


Kevin Ollivier [EMAIL PROTECTED] wrote:


[...]  The tricky part AFAICT would be XCode, though, because
even if there is a scripted solution for this, it would probably  
need

to be run on a Mac where we have access to AppleScript or some other
scripting tool that can read and make changes to XCode projects...
[...]


Xcode project files are plain text as well.  It's possible to  
update them via
script (see WebKitTools/Scripts/sort-Xcode-project-file), but it  
requires a

little more insight than just staring at the source.


— Timothy Hatcher


___
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


[webkit-dev] Leopard WebKit bundle version

2007-11-13 Thread Dan Waylonis

Hi,

On Leopard, /System/Library/Frameworks/WebKit.framework/Versions/A/ 
Resources/Info.plist (excerpt):


   keyCFBundleShortVersionString/key
string5523.10.3/string
keyCFBundleVersion/key
string5523.10.3/string

However, http://developer.apple.com/internet/safari/uamatrix.html  
says that it should be 523.10.3


Who's right?  I've voting for a sticky 5 key on someone's  
keyboard... :-)


Dan
-
Dan Waylonis[EMAIL PROTECTED]
nekotech SOFTWARE
http://www.nekotech.com
650.964.2490 Voice / Fax



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


Re: [webkit-dev] Leopard WebKit bundle version

2007-11-13 Thread Mark Rowe


On 14/11/2007, at 13:13, Dan Waylonis wrote:


Hi,

On Leopard, /System/Library/Frameworks/WebKit.framework/Versions/A/ 
Resources/Info.plist (excerpt):


   keyCFBundleShortVersionString/key
string5523.10.3/string
keyCFBundleVersion/key
string5523.10.3/string

However, http://developer.apple.com/internet/safari/uamatrix.html  
says that it should be 523.10.3


Who's right?  I've voting for a sticky 5 key on someone's  
keyboard... :-)


They're both correct.  The Safari and WebKit Version Information  
page provides information about the build numbers that appear in the  
user agent string.  The build number in the user agent string is  
derived from, but not identical to, the value of CFBundleVersion on  
the WebKit framework.  It currently consists of the CFBundleVersion  
with the leading digit removed.


Kind regards,

Mark Rowe

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


Re: [webkit-dev] Origyn BAL abstraction for WebKit: branch request

2007-11-13 Thread Maciej Stachowiak


On Nov 12, 2007, at 3:03 AM, Jean-Charles VERDIE (Pleyo) wrote:


Dear webkit stakeholders

Back in july, Pleyo announced a new port of Webkit, not onto a  
specific platform but over an Abstraction Layer that we called OwBAL  
and which lets us address specific needs which do not perfectly fit  
with the platform approach. Actually, our goals are to be able to  
adapt WebKit not to a platform, but a set of libraries which can be  
all-but-one identical, or completely different, or whatever.  
Platform approach makes sense when porting to a comprehensive  
environment, but it does not address our needs. So that platform  
made big parts of the code redundant for us.


Today, our abstraction code is almost mature and we'd like to move  
it back to webkit.org. I believe that since our changes are quite  
intrusive in many parts of webcore, jscore and platform, a branch  
could be a good start where we could put the code so that we can  
start advocating some (if not all) of our changes to eventually end  
up being part of webkit trunk.


Can anyone tell me how to process?


I am ok with this in principle. However, in general, being on a branch  
doesn't align you with the project as closely as staying in sync with  
the trunk. In particular, there is still the risk of ending up  
diverging from the core. In particular the S60 port may take a long  
time to merge up to a more modern baseline. Still, it is probably  
better to be on a branch in webkit.org than in a completely separate  
repository, in terms of code sharing and communication.


Are there any other opinions? Besides being a meta-port, what specific  
platforms and libraries does your version of WebKit target?


Does anyone working on OWB already have SVN access?

Regards,
Maciej

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