Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


Just Joined
  • Content count

  • Joined

  • Last visited

About bdash

  • Rank
    InsanelyMac Protégé
  1. Just to clear things up a little... The initial port of WebKit to Windows was done by developers that were already active in the WebKit community. This involved refactoring the WebCore library to be less tied to Mac OS X, and implementing Windows-specific portions of the code when required. A small browser-like application named Spinneret was developed for use in testing WebCore on Windows, the first version of which made its way into the WebKit source code repository in January this year. For the majority of the time since Janurary, WebCore has continued to function on Windows. Various improvements have been contributed, both from people within Apple and members of the open source community. The most common changes in recent times have been minor fixes to ensure that the code compiles on Windows (most of the developers on WebKit work on Mac OS X and some of their changes cause the Windows port to fail to compile). The most obvious reason for porting WebKit to Windows (and other platforms: both GDK and QT ports exist in the WebKit source code repository) is to improve the portability of the code. Improving portability usually involves improving the architecture of the code, removing legacy cruft, and improving abstractions. This has improved the quality of the code in WebKit quite remarkably, with a large amount of functionality being shifted from the Mac OS X-specific WebKit layer down into the portable WebCore layer. I don't see Apple porting Safari itself to Windows, as it heavily relies on many Mac OS X specific technologies. I personally would love to see a WebKit-based browser on Windows, both as a tool for web developers on Windows to get an idea of their compatibility with Safari and as a way to further improve the portability of the WebKit codebase. As always, the WebKit project is keen to hear from anyone that wants to help improve WebKit, whether it be the Mac, Windows, or Linux variants. More information can be found on the website at http://webkit.org/, or by joining us on IRC at irc://irc.freenode.net/#webkit . -- Mark Rowe, WebKit contributor
  2. Where is the source code for this application, and your modifications to the WebCore framework that is required to support the Windows version? Where is the license information for the WebKit code that you have used? Why are you not collaborating with the WebKit project on this? Portability is a goal for WebKit as it provides incentive to refactor and improve the rendering engine. Lots of work has already been put into a Windows port. Why does your website refer to the application as "WebKit"? That's very obviously misleading as it is a browser based on the WebKit libraries, and has the potential to mislead people seeking out the real WebKit. I'd also suggest you think twice before using Apple's Safari logo so prominently on your page -- it's quite clearly a trademark and is a copyrighted image. As a member of the WebKit open source community I would love to see a WebKit-based browser running on Windows, but I'd also prefer to see this accomplished by collaboration amongst the WebKit community rather than in a misleading fashion.