WHO AM I?KENNETH ROHDE CHRISTIANSEN DANISH WORKS AT NOKIA DANMARKFORMERLY NOKIA TECHNOLOGY INSTITUTE, BRAZIL DISTRIBUTED Q...
“ACCOMPLISHMENTS”BRAZIL WORKED IN A CONCEPTING TEAM, MOSTLY TOUCH BASED DESIGNSFIRST TOUCH PORTED WEBKIT TO THE ENLIGHTENM...
WHAT IS ON THE INSIDE?WEB CONTENTS ENGINE         SECURELAYOUT ENGINE               PORTABLEFETCHING OF DATA            GO...
WOW, THAT IS A MOUTHFULWHAT IS MORE INTERESTING IS WHAT IT IS NOT:WEBKIT IS NOT A BROWSER IT IS AN ENGINEERING PROJECT, NO...
WHO ARE THE PEOPLE BEHIND?MOSTLY BIG COMPANIES, THOUGHT WE HAVE A FEW OPEN SOURCE CONTRIBUTORSSOME OF THE ACTIVE ONES NOKI...
SO WHERE IS IT IN USE?GOOGLE CHROME APPLE SAFARI IPHONE PLAYSTATION 3BLACKBERRY PLAYBOOK NOKIA N9 VALVE STEAM EA ORIGINNET...
BACKSTORY
BORN OUT OF OPEN SOURCESO WEBKIT WAS FORGED IN THE CATACOMBS OF APPLE? NAH…WEBKIT STARTED AS A FORK OF THE KHTML+KJS LIBRA...
THE WEBKIT / KHTML WARSIN JANUARY 2003 STEVE JOBS ANNOUNCED THE OPENSOURCING OF WEBCORE AND    THE TEAM INTRODUCED THEMSEL...
A ROCKY MARRIAGEAPPLE HAS THEIR OWN PRIORITIES AND CULTURECODE DUMPS WHICH SEEMINGLY WERE HARD TO UNDERSTAND  AND BACKPORT...
THE TRUE OPEN SOURCING7TH OF JUNE, 2005, APPLE ANNOUNCED THE OPEN SOURCING OF WEBKIT (API, CORE    AND JS ENGINE)SOURCE CO...
AND THE REST IS HISTORYSOME SMALL EXCERPTS:NOKIA DID THE FIRST MOBILE PORT OF WEBKIT TO THEIR S60 FRAMEWORKAPPLE USED WEBK...
SO HOW? PORTS? HUH?HOW CAN WEBKIT BE SO VERSATILE AND IS THERE REALLY JUST ONE WEBKIT?WEBKIT IS NOT A BROWSER BUT AN ENGIN...
HOW DO THE PORTS STACK UP?IT IS HARD TO TELLTHE APPLE AND CHROME PORTS ARE THE MOST WELL MAINTAINED ONES. THEY   HAVE BEEN...
WHAT CAN I USE WEBKIT FOR? (SOME MARKETING)YOU COULD WRITE A BROWSER? ;-) OR YOU COULD USE IT FOR HYBRID APPDEVELOPMENTQT ...
NEAR FUTURE
HOW TO CONTRIBUTEGET THE CODE FROM GIT.WEBKIT.ORG (OR SIMILAR)BUILD IT USING Tools/Scripts/build-webkitFOR QT: Tools/Scrip...
PITFALLS AND COMMON SENSECREATE BUG REPORT PER PATCH CC RELEVANT PEOPLE (CHECK THE WIKI)ACCEPT THAT YOU ARE A NEWBIE AND A...
REVIEWERS AND COMMITTERS?COWBOYS AND INDIANS?IF YOU UNDERSTAND HOW THE PROJECT WORKS AND ACTS AS SUCH THEN    10-30 PATCHE...
+1
WebKit, why it matters (PDF version)
WebKit, why it matters (PDF version)
Upcoming SlideShare
Loading in …5
×

WebKit, why it matters (PDF version)

780 views
738 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
780
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

WebKit, why it matters (PDF version)

  1. 1. WHO AM I?KENNETH ROHDE CHRISTIANSEN DANISH WORKS AT NOKIA DANMARKFORMERLY NOKIA TECHNOLOGY INSTITUTE, BRAZIL DISTRIBUTED QTWEBKIT TEAM
  2. 2. “ACCOMPLISHMENTS”BRAZIL WORKED IN A CONCEPTING TEAM, MOSTLY TOUCH BASED DESIGNSFIRST TOUCH PORTED WEBKIT TO THE ENLIGHTENMENT FOUNDATION LIBRARIES (EFL)NOKIA AQUIRED TROLLTECH JOINED THE QT WEBKIT TEAM DEVELOPMENT / MAINTENANCEBECAME OFFICIAL WEBKIT REVIEWERPART OF A SMALL GROUP OF FRIENDS DEVELOPING THE YBERBROWSER FOR FUNWHICH EVENTUALLY TURNED INTO THE N9 BROWSER, CODE NAMED GROBSTILL WORKING ON BROWSERS, W3C WORK, PLUS DELIVERING THE QT WEBKITMODULE INTO QT5
  3. 3. WHAT IS ON THE INSIDE?WEB CONTENTS ENGINE SECURELAYOUT ENGINE PORTABLEFETCHING OF DATA GOOD USABILITYPARSING OF HTML, CSS, ETC HACKABLEPAGE RENDERING EMBEDDABLEOPEN SOURCECOMPATIBLE HYBRID ENABLERSTANDARDS COMPLIANT APPLICATION PLATFORMSTABLE MORE AND MORE, AN OS
  4. 4. WOW, THAT IS A MOUTHFULWHAT IS MORE INTERESTING IS WHAT IT IS NOT:WEBKIT IS NOT A BROWSER IT IS AN ENGINEERING PROJECT, NOT A SCIENCE PROJECTALSO, WEBKIT HAS A STRONG FOCUS ON BEING A WEB CONTENT / APP ENGINE AND THOUGH IT COMES WITH GENERAL PURPOSE PARTS, THOSE ARE ONLY GEARED TOWARD THE ABOVE.
  5. 5. WHO ARE THE PEOPLE BEHIND?MOSTLY BIG COMPANIES, THOUGHT WE HAVE A FEW OPEN SOURCE CONTRIBUTORSSOME OF THE ACTIVE ONES NOKIA, APPLE, GOOGLE, RIM, ADOBE
  6. 6. SO WHERE IS IT IN USE?GOOGLE CHROME APPLE SAFARI IPHONE PLAYSTATION 3BLACKBERRY PLAYBOOK NOKIA N9 VALVE STEAM EA ORIGINNETFLIX ADOBE AIR HP TOUCHPAD ANDROID GOOGLE EARTH NOKIAS60 (SYMBIAN) BLACKBERRY PHONES WEBOS CHROMEBOOKSSPOTIFY SAMSUNG TIZEN SENCHA ANIMATOR APPLE MAIL AMINOFREEDOM JUMP AMAZON KINDLE FIREPLUS LOTS OF HYBRID APPS ON IOS AND ANDROID
  7. 7. BACKSTORY
  8. 8. BORN OUT OF OPEN SOURCESO WEBKIT WAS FORGED IN THE CATACOMBS OF APPLE? NAH…WEBKIT STARTED AS A FORK OF THE KHTML+KJS LIBRARIES FROM THE OPEN SOURCE KDE PROJECT, WHICH ITSELF WERE A FORK OF THE KHTMLW – THE KDE HTML WIDGETMUCH WORK NEEDED TO BE DONE TO FOLLOW THE W3C STANDARDIZATIONIN ‘99 LARS KNOLL (CURRENT QT PROJECT MAIN MAINTAINER) LEAD AN EFFORT TO CATCH UP AND IT BORE FRUITSKHTML WAS NOW SO GOOD THAT APPLE FORKED IT INTO WHAT WE TODAY KNOW AS WEBKIT
  9. 9. THE WEBKIT / KHTML WARSIN JANUARY 2003 STEVE JOBS ANNOUNCED THE OPENSOURCING OF WEBCORE AND THE TEAM INTRODUCED THEMSELVES TO KHTML DEVELOPERS “When we were evaluating technologies over a year ago, KHTML and KJS stoodout. Not only were they the basis of an excellent modern and standards compliantweb browser, they were also less than 140,000 lines of code. The size of your codeand ease of development within that code made it a better choice for us than otheropen source projects. Your clean design was also a plus. And the small size of yourcode is a significant reason for our winning startup performance…” Don Melton, AppleFAST FORWARD TWO YEARS AND THE OPEN SOURCE ATTEMPT WAS FAILING
  10. 10. A ROCKY MARRIAGEAPPLE HAS THEIR OWN PRIORITIES AND CULTURECODE DUMPS WHICH SEEMINGLY WERE HARD TO UNDERSTAND AND BACKPORT (OBJECTIVE C, UNRELATED CHANGES, ETC)KHTML AND KJS WERE GREAT TO BUILD UPON BUT GIVING BACK TO THE COMMUNITY IN A WAY THEY COULD MAKE ACTUAL USE OF AND APPRECIATE WAS JUST NOT WORKING OUT AS PLANNED
  11. 11. THE TRUE OPEN SOURCING7TH OF JUNE, 2005, APPLE ANNOUNCED THE OPEN SOURCING OF WEBKIT (API, CORE AND JS ENGINE)SOURCE CONTROL TREES, BUGTRACKING TOOLS (NOT THE INTERNAL ONE)BASICALLY THE BUILDING BLOCKS TO CREATE A BROWSER + A CONTRIBUTION MODEL WHICH ALLOWED OTHER TO CONTRIBUTE IN A FAIR AND EQUAL MANNERAND SO THE WORLD TOOK AND WELCOME WEBKIT WITH OPEN ARMS
  12. 12. AND THE REST IS HISTORYSOME SMALL EXCERPTS:NOKIA DID THE FIRST MOBILE PORT OF WEBKIT TO THEIR S60 FRAMEWORKAPPLE USED WEBKIT FOR THEIR IPHONE PLATFORMGOOGLE CREATED THE ANDROID BROWSER USING WEBKITGOOGLE ABANDONED FIREFOX AND CREATED CHROMEWEBKIT BECAME THE DEFACTO MOBILE BROWSER ENGINE, “FORCING” OTHER MOBILE BROWSER TO SUPPORT WEBKIT EXTENTIONS AND CSS PREFIXES.AND IT IS ALL JUST GETTING STARTED…
  13. 13. SO HOW? PORTS? HUH?HOW CAN WEBKIT BE SO VERSATILE AND IS THERE REALLY JUST ONE WEBKIT?WEBKIT IS NOT A BROWSER BUT AN ENGINE AND A VERY FORKED ONEIT CONSISTS OF PORTS (APPLE, GOOGLE, GTK+, QT, ETC) WHICH PROVIDES API, AND PLATFORM INTEGRATION.MANY BROWSER USES FORKS OF TRUNK WEBKIT
  14. 14. HOW DO THE PORTS STACK UP?IT IS HARD TO TELLTHE APPLE AND CHROME PORTS ARE THE MOST WELL MAINTAINED ONES. THEY HAVE BEEN DEVELOPED FOR A LONG TIME AND HAVE BIG WELL-ESTABLISHED TEAMS.APPLE PORTS PROVIDES API FOR APP DEVELOPMENT AS WELL, ACROSS IOS, WIN AND MAC, CHROME DOESN’T, IT IS A BROWSER.QT IS A MULTI-PLATFORM PORT, DESIGNED FOR DEVELOPING BROWSER BUT PROVIDES AN EXTENSIVE API FOR APP DEVELOPMENT AS WELL. IT IS ALSO CLOSING IN ON CHROME AND APPLE PORTS IN STANDARDS SUPPORT AND TESTING. QT WEBKIT COMES WITH MOBILE FEATURES, SOMETHING OTHER PORTS ONLY DO TO A LIMITED EXTEND.
  15. 15. WHAT CAN I USE WEBKIT FOR? (SOME MARKETING)YOU COULD WRITE A BROWSER? ;-) OR YOU COULD USE IT FOR HYBRID APPDEVELOPMENTQT IS POPULAR FOR THIS: SPOTIFY, NETFLIX (PS3, BOX ETC), EA ORIGINI WILL RECOMMEND TAKING A LOOK AT QT WEBKIT•  CROSS PLATFORM•  MOBILE FEATURES•  VIBRANT COMMUNITY•  RASHBERRY PI•  NOKIA N9•  HYBRID FEATURES, EASILY EMBEDDABLE, QT QUICK VIEW
  16. 16. NEAR FUTURE
  17. 17. HOW TO CONTRIBUTEGET THE CODE FROM GIT.WEBKIT.ORG (OR SIMILAR)BUILD IT USING Tools/Scripts/build-webkitFOR QT: Tools/Scripts/build-webkit –qtRUN IT (check the wiki or the tools in Tools/Scripts as this can differ per platform)READ THE FOLLOWING SITES:http://www.webkit.org/coding/technical-articles.htmlhttp://www.webkit.org/coding/coding-style.htmlhttp://www.webkit.org/coding/contributing.html
  18. 18. PITFALLS AND COMMON SENSECREATE BUG REPORT PER PATCH CC RELEVANT PEOPLE (CHECK THE WIKI)ACCEPT THAT YOU ARE A NEWBIE AND ARE GOING TO DO EVERYTHING WRONGDO NOT GIVE UP!CODING STYLE / NAMING IS VERY IMPORTANT FOR SUCH A BIG PROJECT ACCEPT IT AND USE THE SCRIPTS TO FIND THE MOST COMMON ISSUESRUN THE TEST SUITEJOIN THE IRC CHANNELS (FREENODE #WEBKIT, #QTWEBKIT, QTWEBKIT-CPH)JOIN THE MAILING LISTS
  19. 19. REVIEWERS AND COMMITTERS?COWBOYS AND INDIANS?IF YOU UNDERSTAND HOW THE PROJECT WORKS AND ACTS AS SUCH THEN 10-30 PATCHES WILL GRAND YOU A COMMITTER NOMINATIONIF YOU HAVE 80-120 SUBSTANTIAL PATCHES, THEN YOU CAN BE NOMINATED TO BECOME A REVIEWER AND BE ADDED TO THE REVIEWER MAILING LISTMOSTLY EVERY YEAR THERE IS A CONTRIBUTOR SUMMIT (FOR COMMITTERS AND REVIEWERS) IN THE BAY AREA (CUPERTINO SO FAR) WHERE THE FUTURE OF THE PROJECT IS DISCUSSED AND WHERE YOU CAN MEET FELLOW CONTRIBUTORS
  20. 20. +1

×