Kenneth Rohde Christiansen is a Danish engineer who currently works at Nokia Danmark and was formerly part of the distributed Qt WebKit team. He has extensive experience working on touch-based designs and was first to port WebKit to the Enlightenment foundation libraries. He is an active contributor to browsers, W3C standards, and integrating Qt WebKit into Qt5.
TWILIO was founded in 2007 by Jeff Lawson, Evan Cooke, and John Wolthuis and was originally based in both Seattle, Washington, and San Francisco, California.
It is a cloud communications platform which allows software developers to programmatically make and receive phone calls and send and receive text messages using its web service APIs.
TWILIO API have support for various languages like - PHP, .NET (C#), PYTHON, JAVA, RUBY
WebRTC has had a tough 3 or 4 years. But it's gone through a rebirth. Node.js developers are a perfect match for the technology. Come and play with it!
Various Mobile Operating Systems in Market presented by Ashish GaikwadAshish Gaikwad
There are many operating systems in market. But most of us only know about top 2 or 3 like android, ios, windows etc. But others like tizen, fire, firefox, sailfish etc. are also emerging and gaining their shares. This presentation will take you through those operating systems.
Ashish Gaikwad presented this at Atharva College of Engineering.
Pundit is an open source tool for semantic enrichment. It has been designed by the Italian software company Net7 as part of the DM2E Project, which is focused on building tools and communities that enable humanities researchers to work with manuscripts in the Linked Open Web, as well as within European projects mainly focused on Digital Humanities (SEMLIB - Semantic Digital Libraries, AGORA, ERC AdG 2011 Lookingatwords, ERC AdG 2009 EUROCORR) and thus used primary in the Humanities domain.
The session aims at illustrating Pundit main features and components (the client, feed, ask) as well as showing how it has been used by specific scholarly communities in Philosophy, History of Art, Philology and History of Thought domains.
Moreover, attendees will be practically introduced to Pundit through dedicated exercises thought to give them the first skills to produce semantic annotations on Digital Libraries and generic websites.
TWILIO was founded in 2007 by Jeff Lawson, Evan Cooke, and John Wolthuis and was originally based in both Seattle, Washington, and San Francisco, California.
It is a cloud communications platform which allows software developers to programmatically make and receive phone calls and send and receive text messages using its web service APIs.
TWILIO API have support for various languages like - PHP, .NET (C#), PYTHON, JAVA, RUBY
WebRTC has had a tough 3 or 4 years. But it's gone through a rebirth. Node.js developers are a perfect match for the technology. Come and play with it!
Various Mobile Operating Systems in Market presented by Ashish GaikwadAshish Gaikwad
There are many operating systems in market. But most of us only know about top 2 or 3 like android, ios, windows etc. But others like tizen, fire, firefox, sailfish etc. are also emerging and gaining their shares. This presentation will take you through those operating systems.
Ashish Gaikwad presented this at Atharva College of Engineering.
Pundit is an open source tool for semantic enrichment. It has been designed by the Italian software company Net7 as part of the DM2E Project, which is focused on building tools and communities that enable humanities researchers to work with manuscripts in the Linked Open Web, as well as within European projects mainly focused on Digital Humanities (SEMLIB - Semantic Digital Libraries, AGORA, ERC AdG 2011 Lookingatwords, ERC AdG 2009 EUROCORR) and thus used primary in the Humanities domain.
The session aims at illustrating Pundit main features and components (the client, feed, ask) as well as showing how it has been used by specific scholarly communities in Philosophy, History of Art, Philology and History of Thought domains.
Moreover, attendees will be practically introduced to Pundit through dedicated exercises thought to give them the first skills to produce semantic annotations on Digital Libraries and generic websites.
A mini intro to web components, starting from what you (presumable) already know and slowly adopting new vanilla web components features. After that, is shows how to accomplish the same using Polymer 2.0.
Intended to be instructor led.
ב-24 במרץ 2010 התקיים המפגש השני של פורום מפתחי ה-W3C הישראלי (W3C Developers Forum - W3CDF). המפגש עסק בפיתוח אפליקציות ואתרים למכשירים ניידים (Mobile Web).
Почему браузер Opera перешёл на WebKit, как оно к этому шло, чем обернётся для разработчиков, почему WebKit не станет IE6, что это вообще за зверь, откуда взялся Blink, и почему с веб-стандартами всё будет в порядке.
Après avoir conquis le marché des smartphones et tablettes, Android devient incontournable dans le domaine industriel. Son utilisation pour la conception de solutions embarquées industrielles soulève toutefois des problématiques techniques spécifiques : customisation de l'OS, développement de pilotes de périphériques, capacité à répondre à des contraintes temps réel.
S'appuyant sur son expertise des technologies Linux embarqué, Open Wide Ingénierie a accompagné avec succès la réalisation de nombreux systèmes sur mesure. Les experts du pôle Mobilité et Multimédia partage leur expérience à travers cette présentation en abordant les sujets techniques indispensables avant de migrer vers Android.
These are the accompanying slides to a tech talk given at airbnb.
Video here: http://www.youtube.com/watch?v=GGzmST5nNSM
Other tech talks here: https://www.airbnb.com/tech_talks
With more than 1.5 million developers worldwide, Appcelerator's ecosystem is a key part of its developers' success. Nolan Wright, Appcelerator's CTO, will discuss how ISVs like PayPal and Box.net are adding great fuel to the Titanium development fire with new capabilities and resources for mobile developers.
Nolan Wright, Co-founder and CTO, leads engineering and product management at Appcelerator.
Shows the value of mobile apps, and explain what it takes to create your own. Focuses on Qt, licensing, app stores, cost of development etc.
First given at FOSSDay2010 in Göthenburg
Introduction to (web) APIs - definitions, examples, concepts and trendsOlaf Janssen
This story is about the added value of APIs (application programming interfaces) for modern businesses, developers and software consumers. It deals with API-fundamentals and shows how APIs are the cornerstones of modern business development (BizDev2.0). By looking at casestudies from Google Maps, Twitter, Amazon, eBay, Moo, Flickr, Netflix and other web2.0-companies, it becomes clear how APIs add value for all parties on the modern web.
This presentation was given by Olaf Janssen - Open Data coordinator for the National Library of the Netherlands (KB) - as a lecture for students of the master's course "Digital Access to Cultural Heritage" at Leiden University on 13-3-2014
Overview of the mobile platform and development environment landscape in light of the recent announcements during and around MWC 2011.
Presented at the March 2011 Mobile Monday Edinburgh.
A mini intro to web components, starting from what you (presumable) already know and slowly adopting new vanilla web components features. After that, is shows how to accomplish the same using Polymer 2.0.
Intended to be instructor led.
ב-24 במרץ 2010 התקיים המפגש השני של פורום מפתחי ה-W3C הישראלי (W3C Developers Forum - W3CDF). המפגש עסק בפיתוח אפליקציות ואתרים למכשירים ניידים (Mobile Web).
Почему браузер Opera перешёл на WebKit, как оно к этому шло, чем обернётся для разработчиков, почему WebKit не станет IE6, что это вообще за зверь, откуда взялся Blink, и почему с веб-стандартами всё будет в порядке.
Après avoir conquis le marché des smartphones et tablettes, Android devient incontournable dans le domaine industriel. Son utilisation pour la conception de solutions embarquées industrielles soulève toutefois des problématiques techniques spécifiques : customisation de l'OS, développement de pilotes de périphériques, capacité à répondre à des contraintes temps réel.
S'appuyant sur son expertise des technologies Linux embarqué, Open Wide Ingénierie a accompagné avec succès la réalisation de nombreux systèmes sur mesure. Les experts du pôle Mobilité et Multimédia partage leur expérience à travers cette présentation en abordant les sujets techniques indispensables avant de migrer vers Android.
These are the accompanying slides to a tech talk given at airbnb.
Video here: http://www.youtube.com/watch?v=GGzmST5nNSM
Other tech talks here: https://www.airbnb.com/tech_talks
With more than 1.5 million developers worldwide, Appcelerator's ecosystem is a key part of its developers' success. Nolan Wright, Appcelerator's CTO, will discuss how ISVs like PayPal and Box.net are adding great fuel to the Titanium development fire with new capabilities and resources for mobile developers.
Nolan Wright, Co-founder and CTO, leads engineering and product management at Appcelerator.
Shows the value of mobile apps, and explain what it takes to create your own. Focuses on Qt, licensing, app stores, cost of development etc.
First given at FOSSDay2010 in Göthenburg
Introduction to (web) APIs - definitions, examples, concepts and trendsOlaf Janssen
This story is about the added value of APIs (application programming interfaces) for modern businesses, developers and software consumers. It deals with API-fundamentals and shows how APIs are the cornerstones of modern business development (BizDev2.0). By looking at casestudies from Google Maps, Twitter, Amazon, eBay, Moo, Flickr, Netflix and other web2.0-companies, it becomes clear how APIs add value for all parties on the modern web.
This presentation was given by Olaf Janssen - Open Data coordinator for the National Library of the Netherlands (KB) - as a lecture for students of the master's course "Digital Access to Cultural Heritage" at Leiden University on 13-3-2014
Overview of the mobile platform and development environment landscape in light of the recent announcements during and around MWC 2011.
Presented at the March 2011 Mobile Monday Edinburgh.
Session slides from Future Insights Live, Vegas 2015:
https://futureinsightslive.com/las-vegas-2015/
Modular front-end applications that can grow and evolve over time. Many front-end JS toolkits are optimized for building the first version of the app quickly. But for an app that powers a business, you have to think past initial launch. Your app will likely outlive the attention span of those who first wrote it. So, how do we pick tools and architectures that can be modified, maintained, and upgraded over time by a team of people?
Web Technologies in Automotive & Robotics (BlinkOn 10)Igalia
By Lokesh Kumar Goel and Jose Dapena Paz.
Slides at https://docs.google.com/presentation/d/1-iWFdgV1Aj5Ovt7essBtEaLJ1jNxQ0oUVik5jpEWWmI/edit#slide=id.p1.
(c) BlinkOn 10
Toronto, Ontario (Canada)
April 09 - 10, 2019
https://docs.google.com/document/u/1/d/e/2PACX-1vTgBrqyQ4KCchsymvssri1pN1BkOg3sEqHThqhvFDl9-zl-hLx1S5c8sc5gaZ_VzKEVaYj94H3m1vso/pub#h.igsyfaa103a0
Create Cross-Platform Native Mobile Apps in Flex with ELIPS StudioGuilhem Ensuque
In this FITC SF 2010 session, Guilhem explains what makes development of mobile applications development so special compared to Rich Internet Applications. You will learn what it means to be "native", why it matters for performance and user experience, and how OpenPlug's ELIPS Studio turns your Flex code into a native app. You'll also hear about the bewildering diversity in mobile operating systems and how ELIPS Studio helps keeping fragmentation at bay. Taking examples from popular apps created by ELIPS Studio users and some hands-on code examples, Guilhem will take you through the entire journey of specifying, designing, developing, testing and publishing an app created in Flex with ELIPS Studio on popular devices.
The improvements in size, features and price of hardware has ushered new opportunities in creating small, smart devices (aka internet-of-things) which can be integrated in homes and industries. In these places, the devices can help automate common tasks, as well as give information about the state of things, such as temperature of a machine, air quality etc.
Installing an app for one such devices might seem fine at first, but it doesn’t scale nicely to 100s of devices, or devices you seldom interact with, like in an industrial setting. Devices might even have different security restrictions, like being locked behind a physical key.
So how do we communicate with these devices? The web has always been known for its low fraction and easy onboarding. No need to install any software, just type in a URL and off you go. And it has always been very secure with its sandbox system, and companies can even have URLs be restricted to certain WiFi networks (intranet).
In the last couple of years, the web has taken a quantum leap in usability, with offline support, and many ways to make the experience very app-like. So the question is unavoidable, can the web be the platform to make smart devices succeed?
The web lives in a sandbox, and its security model has allowed people to trust it and for it to grow enormously over time, but the world is changing around us. There is a growing need to access new hardware capabilities such as sensors or just connect to devices around us.
The great news is that the web sandbox is growing with new capabilities and with new security models, allowing us to connect to devices via Bluetooth, USB or even talk NFC. There are now even ways to directly get magnetometer readings on Android devices.
In this talk we will look at this new landscape and how it enables the new wave of smart devices. We will also look at how easy it is to use some of these new APIs.
Come join me for a look at how the web can make your smart devices success
WebKit is everywhere, on desktops, mobiles, - and as an integrated part of the Qt platform, it is on Linux-based MeeGo as well.
n this session we will quickly introduce the WebKit project, and look at why it has become so popular on the mobile platform. We will look at some of the mobile adaptions normally done by the different WebKit ports and at the work we have been doing in Qt WebKit to make it more fit for mobile usage.
Some of the technologies we will touch, includes: frame flattening, tiling (including challenges), viewport meta information, touch events and fuzzy hit testing.
We hope the session will make people aware of the importance of the Qt WebKit project and its mobile efforts; create discussions and use-cases that we can use for integrating even better with, in particular, open source projects targeting mobile usage and the open source community in general.
Connecting Technology for Great Experiences - How does QML and Web fit together?
WebKit, why it matters (PDF version)
1.
2. WHO AM I?
KENNETH ROHDE CHRISTIANSEN DANISH WORKS AT NOKIA DANMARK
FORMERLY NOKIA TECHNOLOGY INSTITUTE, BRAZIL DISTRIBUTED QT
WEBKIT TEAM
3. “ACCOMPLISHMENTS”
BRAZIL WORKED IN A CONCEPTING TEAM, MOSTLY TOUCH BASED DESIGNS
FIRST TOUCH PORTED WEBKIT TO THE ENLIGHTENMENT FOUNDATION LIBRARIES (EFL)
NOKIA AQUIRED TROLLTECH JOINED THE QT WEBKIT TEAM DEVELOPMENT /
MAINTENANCE
BECAME OFFICIAL WEBKIT REVIEWER
PART OF A SMALL GROUP OF FRIENDS DEVELOPING THE YBERBROWSER FOR FUN
WHICH EVENTUALLY TURNED INTO THE N9 BROWSER, CODE NAMED GROB
STILL WORKING ON BROWSERS, W3C WORK, PLUS DELIVERING THE QT WEBKIT
MODULE INTO QT5
4.
5. WHAT IS ON THE INSIDE?
WEB CONTENTS ENGINE SECURE
LAYOUT ENGINE PORTABLE
FETCHING OF DATA GOOD USABILITY
PARSING OF HTML, CSS, ETC HACKABLE
PAGE RENDERING EMBEDDABLE
OPEN SOURCE
COMPATIBLE HYBRID ENABLER
STANDARDS COMPLIANT APPLICATION PLATFORM
STABLE MORE AND MORE, AN OS
6. WOW, THAT IS A MOUTHFUL
WHAT IS MORE INTERESTING IS WHAT IT IS NOT:
WEBKIT IS NOT A BROWSER IT IS AN ENGINEERING PROJECT, NOT A SCIENCE PROJECT
ALSO, 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.
7. WHO ARE THE PEOPLE BEHIND?
MOSTLY BIG COMPANIES, THOUGHT WE HAVE A FEW OPEN SOURCE CONTRIBUTORS
SOME OF THE ACTIVE ONES NOKIA, APPLE, GOOGLE, RIM, ADOBE
8. SO WHERE IS IT IN USE?
GOOGLE CHROME APPLE SAFARI IPHONE PLAYSTATION 3
BLACKBERRY PLAYBOOK NOKIA N9 VALVE STEAM EA ORIGIN
NETFLIX ADOBE AIR HP TOUCHPAD ANDROID GOOGLE EARTH NOKIA
S60 (SYMBIAN) BLACKBERRY PHONES WEBOS CHROMEBOOKS
SPOTIFY SAMSUNG TIZEN SENCHA ANIMATOR APPLE MAIL AMINO
FREEDOM JUMP AMAZON KINDLE FIRE
PLUS LOTS OF HYBRID APPS ON IOS AND ANDROID
10. BORN OUT OF OPEN SOURCE
SO 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 WIDGET
MUCH WORK NEEDED TO BE DONE TO FOLLOW THE W3C STANDARDIZATION
IN ‘99 LARS KNOLL (CURRENT QT PROJECT MAIN MAINTAINER) LEAD AN EFFORT TO
CATCH UP AND IT BORE FRUITS
KHTML WAS NOW SO GOOD THAT APPLE FORKED IT INTO WHAT WE TODAY KNOW AS
WEBKIT
11. THE WEBKIT / KHTML WARS
IN 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 stood
out. Not only were they the basis of an excellent modern and standards compliant
web browser, they were also less than 140,000 lines of code. The size of your code
and ease of development within that code made it a better choice for us than other
open source projects. Your clean design was also a plus. And the small size of your
code is a significant reason for our winning startup performance…”
Don Melton, Apple
FAST FORWARD TWO YEARS AND THE OPEN SOURCE ATTEMPT WAS FAILING
12. A ROCKY MARRIAGE
APPLE HAS THEIR OWN PRIORITIES AND CULTURE
CODE 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
13. THE TRUE OPEN SOURCING
7TH 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 MANNER
AND SO THE WORLD TOOK AND WELCOME WEBKIT WITH OPEN ARMS
14. AND THE REST IS HISTORY
SOME SMALL EXCERPTS:
NOKIA DID THE FIRST MOBILE PORT OF WEBKIT TO THEIR S60 FRAMEWORK
APPLE USED WEBKIT FOR THEIR IPHONE PLATFORM
GOOGLE CREATED THE ANDROID BROWSER USING WEBKIT
GOOGLE ABANDONED FIREFOX AND CREATED CHROME
WEBKIT BECAME THE DEFACTO MOBILE BROWSER ENGINE, “FORCING” OTHER
MOBILE BROWSER TO SUPPORT WEBKIT EXTENTIONS AND CSS PREFIXES.
AND IT IS ALL JUST GETTING STARTED…
15. 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 ONE
IT CONSISTS OF PORTS (APPLE, GOOGLE, GTK+, QT, ETC) WHICH PROVIDES API,
AND PLATFORM INTEGRATION.
MANY BROWSER USES FORKS OF TRUNK WEBKIT
16. HOW DO THE PORTS STACK UP?
IT IS HARD TO TELL
THE 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.
17. WHAT CAN I USE WEBKIT FOR? (SOME MARKETING)
YOU COULD WRITE A BROWSER? ;-) OR YOU COULD USE IT FOR HYBRID APP
DEVELOPMENT
QT IS POPULAR FOR THIS: SPOTIFY, NETFLIX (PS3, BOX ETC), EA ORIGIN
I 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
19. HOW TO CONTRIBUTE
GET THE CODE FROM GIT.WEBKIT.ORG (OR SIMILAR)
BUILD IT USING Tools/Scripts/build-webkit
FOR QT: Tools/Scripts/build-webkit –qt
RUN 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.html
http://www.webkit.org/coding/coding-style.html
http://www.webkit.org/coding/contributing.html
20. PITFALLS AND COMMON SENSE
CREATE BUG REPORT PER PATCH CC RELEVANT PEOPLE (CHECK THE WIKI)
ACCEPT THAT YOU ARE A NEWBIE AND ARE GOING TO DO EVERYTHING WRONG
DO 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 ISSUES
RUN THE TEST SUITE
JOIN THE IRC CHANNELS (FREENODE #WEBKIT, #QTWEBKIT, QTWEBKIT-CPH)
JOIN THE MAILING LISTS
21. 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 NOMINATION
IF YOU HAVE 80-120 SUBSTANTIAL PATCHES, THEN YOU CAN BE NOMINATED TO
BECOME A REVIEWER AND BE ADDED TO THE REVIEWER MAILING LIST
MOSTLY 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