El directorio enciclopédico desde la Wikipedia.
WebKit is an open source application framework that provides a foundation upon which to build a web browser. WebKit was originally derived by Apple Inc. from the Konqueror browser’s KHTML software library for use as the engine of Mac OS X’s Safari web browser, and has now been further developed by individuals from the KDE project, Apple, Nokia, Google, Torch Mobile and others.[1] It has been ported to a number of different platforms and is now used as the rendering engine within a number of different pieces of software. WebKit passes the Acid2 test, and as of September 2008, nightly builds pass the Acid3 test as well, with pixel-perfect rendering and no timing or smoothness issues on reference hardware.[2]
HistoryOriginsWebKit began in 2002 when Apple Inc. created a fork of the KDE project’s HTML layout engine KHTML and KDE's JavaScript engine (KJS). Apple developers explained in an email to KDE developers[3] that these engines allowed easier development than other technologies by nature of being small (less than 140,000 lines of code), cleanly designed and standards compliant. KHTML and KJS were ported to Mac OS X with the help of an adapter library and renamed WebCore and JavaScriptCore.[3] JavaScriptCore was announced in an email to a KDE mailing list in June 2002, alongside the first release of Apple's changes.[4] WebCore was announced at the Macworld Expo in January 2003 by Apple CEO Steve Jobs with the release of the Safari web browser. JavaScriptCore was first included with Mac OS X v10.2 as a private framework which Apple used within their Sherlock application, while WebCore debuted with the first beta of Safari. Mac OS X v10.3 was the first major release of Apple's operating system to bundle WebKit, although it had already been bundled with a minor release of 10.2. However, the exchange of code patches between the two branches of KHTML has previously been difficult and the code base diverged because both projects had different approaches in coding.[5] One of the reasons for this is that Apple worked on their version of KHTML for a year before making their fork public. Despite this, the KDE project was able to incorporate some of these changes to improve KHTML's rendering speed and add features, including compliance with the Acid2 rendering test.[citation needed] According to Apple, some changes involved Mac OS X-specific features (e.g., Objective-C, KWQ, OS X calls) that are absent in KDE's KHTML, which called for different development tactics.[6] ControversyAt one point KHTML developers said they were unlikely to accept Apple's changes and claimed the relationship between the two groups was a "bitter failure".[7] Apple submitted their changes in large patches that contained a great number of changes with inadequate documentation, often to do with future feature additions. Thus, these patches were difficult for the KDE developers to integrate back into KHTML. Furthermore, Apple had demanded developers to sign nondisclosure agreements before looking at Apple's source code and even then they were unable to access Apple's bug database.[8] During the publicized 'divorce' period, KDE developer pipitas posted an article claiming KHTML developers had managed to backport many (but not all) Safari improvements from WebCore to KHTML, and they always appreciated the improvements coming from Apple and still do so. The article also noted Apple had begun to contact KHTML developers about discussing how to improve the mutual relationship and ways of future cooperation.[9] Since the story of the fork appeared in news, Apple has released changes of the source code of its KHTML fork in a CVS repository.[10] Since the transfer of the sourcecode into a public CVS repository, Apple and KHTML developers have had increasing collaboration. Many KHTML developers have become reviewers and submitters for Apple's WebKit SVN repository. The WebKit team had also reversed many Apple-specific changes in the original WebKit code base and implemented platform-specific abstraction layers to make committing the core rendering code to other platforms significantly easier.[11] Open-sourcingOn June 7, 2005, Safari developer Dave Hyatt announced on his weblog that Apple was open sourcing WebKit (previously, only WebCore and JavaScriptCore were open source) and opening up access to WebKit’s CVS tree and Bugzilla tool.[12] This was announced at Apple’s Worldwide Developers Conference 2005 by Bertrand Serlet. In mid-December 2005 support for Scalable Vector Graphics was merged into the standard build[13] and in early January 2006 the source code was migrated from CVS to Subversion. The next month the Ars Technica website published an article announcing that the KDE team would move from KHTML to WebKit.[14] Further developmentIn November 2007, the project announced that it had accomplished support for HTML 5 media features, allowing for embedded video to be natively rendered and script-controlled in WebKit [15]. On June 2, 2008, the WebKit project announced they rewrote JavaScriptCore as "SquirrelFish", a bytecode interpreter.[16][17] The project evolved into SquirrelFish Extreme (abbreviated SFX), announced on September 18, 2008, which compiles JavaScript into native machine code, eliminating the need for a bytecode interpreter and thus speeding up Javascript execution.[18] As of September 28, 2008, the only supported architecture for SFX is the x86 architecture. UsageWebKit is used as the rendering engine within Safari on Mac OS X, Windows and the iPhone. Other applications on Mac OS X can make use of WebKit, for example Apple's email client Mail and the 2008 version of Microsoft's Entourage personal information manager both make use of WebKit to render e-mail messages with HTML content. New web browsers have been built around WebKit such as Shiira, Arora and Google's Chrome browser,[19][20] and it has also been adopted as the rendering engine in Omniweb, iCab and Epiphany replacing their original rendering engines.[21] Epiphany supported both Gecko and WebKit for some time, but the team decided that Gecko's release cycle and future development plans would make it cumbersome to continue supporting it. PortsThe week after Hyatt's announcement of WebKit's open-sourcing, Nokia announced that it had ported Webkit to the Symbian operating system and was developing a browser based on WebKit for their mobile phones, which was later named Web Browser for S60. Apple has also ported WebKit to the iPhone OS to run on the iPhone and iPod Touch, where it is used to render content within the device’s web browser and email software,[22] and the Android mobile phone platform uses WebKit as the basis of its web browser.[23] In June 2007, Apple announced that WebKit had been ported to Microsoft Windows as part of Safari. There are also ongoing ports for the open source operating systems Syllable,[24] Haiku[25] and AROS.[26] WebKit has also been ported to a number of toolkits that support multiple platforms, such as the GTK+ toolkit,[27], the Qt toolkit and the Adobe Integrated Runtime. Qt Software includes the Qt port in the Qt 4.4 release. The Qt port of WebKit will also be available to be used in Konqueror in KDE 4.1.[14] There is also a project synchronized with WebKit (sponsored by Pleyo)[28] called Origyn Web Browser, which provides a meta-port to an abstract platform with the aim of making porting to embedded or lightweight systems quicker and easier.[29] This port is used for embedded devices such as set-top boxes, PMP and also the AmigaOS official port.[30] ComponentsWebCoreWebCore is a layout, rendering, and Document Object Model (DOM) library for HTML and SVG, developed by the WebKit project. Its complete source code is licensed under the LGPL. The WebKit framework wraps WebCore and JavaScriptCore, providing an Objective-C application programming interface to the C++-based WebCore rendering engine and JavaScriptCore script engine, allowing it to easily be referenced by applications based on the Cocoa API; later versions also include a cross-platform C++ platform abstraction, and various ports provide additional APIs. JavaScriptCoreJavaScriptCore is a framework that provides a JavaScript engine for WebKit implementations, and provides this type of scripting in other contexts within Mac OS X.[31][32] JavaScriptCore is originally derived from KDE's JavaScript engine (KJS) library (which is part of the KDE project) and the PCRE regular expression library. Since forking from KJS and PCRE, JavaScriptCore has been improved with many new features and greatly improved performance.[33] On June 2, 2008, the WebKit project announced they rewrote JavaScriptCore as "SquirrelFish", a bytecode interpreter.[34][35] The project evolved into SquirrelFish Extreme (abbreviated SFX), announced on September 18, 2008, which compiles JavaScript into native machine code, eliminating the need for a bytecode interpreter and thus speeding up Javascript execution.[36] As of September 28, 2008, the only supported architecture for SFX is the x86 architecture. DroseraDrosera is a JavaScript debugger that was included with the nightly builds of WebKit.[37][38] It was named after Drosera, a genus of carnivorous plants (i.e. bug-eaters). Drosera has been replaced by the inclusion of debugging functionality in the Web Inspector.[39] SunSpider
A benchmark suite that aims to measure JavaScript performance on tasks that are relevant to the current and near future use of JavaScript in the real world, such as screen drawing, encryption and text manipulation.[40] The suite further attempts to be balanced and statistically sound.[41] It was released by Apple's WebKit team in December 2007.[42] It was well-received,[43] and other browser developers also use it to compare the JavaScript performance of different browsers.[44] See also
References
External links
Directorio de Enlaces Directorio dmoz Directorio espejo dmoz Pedro Bernardo | ||||||||||||||||||||||||||||||||||||
