170 likes | 350 Views
Windows 8 Loves Web Developers. Lauri Svan, SC5 | 5.3.2013. #td2013fi. A Word on Lauri. An experienced developer and dreamer; that makes me an architect. I craft apps that run on several platforms (desktop and mobile ) and help our teams in SC5 to do the same.
E N D
Windows 8 Loves Web Developers Lauri Svan, SC5 | 5.3.2013 #td2013fi
A Word on Lauri • An experienced developer and dreamer; that makes me an architect. • I craft apps that run on several platforms (desktop and mobile) and help our teams in SC5 to do the same. • I try to stay neutral on technology choices; I want to minimize my and my customers’ costs and vendor lock-in. • My choice has lately been HTML5. • I am not a “web designer” or “Windows 8 expert”; the bulk of my career is about building Java and C++ frameworks.
What Windows 8 Means for Me? Fast, HTML5 compliant browser engine Growing and potentially huge ecosystem of consumer and enterprise users Access to system services like a native app New conventions I need to learn and live with #td2013fi
HTML5 and Windows 8 – Best of the Both Worlds? • A huge selection of open, extensible libraries • The widest developer base • Reusing of existing know-how • A wide selection of system APIs • The widest user base? • Platform-wide conventions • HTML5 / JavaScript • Windows 8 / WinRT
Windows 8 – a Holistic Developer Offering It feels a bit overwhelming at start But you will soon start seeing familiar patterns It is HTML5, CSS and JavaScript after all Your skills will transfer But your existing coding patterns might not #td2013fi
Anatomy of a Windows 8 HTML5 App A Sample HTML5 App Windows 8 HTML5 App Page SpecificLogic Pages Models Views Templates Data Sources Misc. Code Utility Libraries Utility Libraries WinJS.UI jQuery WinJS API Backbone.js Browser Runtime
Write your first app with MS stack – there is a lot of love put into it.Then see what you can reuse from your own toolbox.
Windows 8 Specific vs. Common • WinJS.UI • It is silly to reinvent the wheel if it already works • Grid – it is better than the one you are used to • Your existing CSS code will likely be wasted • Packaging • You will need to learn the conventions of packaging Windows 8 apps, including splash screens, tiles etc. • WinJS API • A good list of alternatives when you cannot use the 3rd party libraries • Server APIs and Bindings • XHRs work both normal way and with WinJS • Implement WinJS UI specific interfaces/adapters for your API (some reuse possible!) • Project layout, builds, infra • Nothing stops you adding a Windows 8 subproject into your project. • e.g. RequireJS and Grunt, Git work all fine • Some 3rd party libraries • As long as they don’t break the security sandbox, they should be fine. • to Learn • to Keep
My App in Windows 8 - It the Same Anymore? Your application will be a separate entity, not a result of a build parametrization You will have a separate UI skeleton with different HTML, and CSS You may share non-UI (and some UI) libraries #td2013fi
Demo: Using RequireJS, jQuery and D3 Libraries in Windows 8 App #td2013fi
Example Thank you for coming! Feedback can be given via mobile or laptop through techdays.fi seminar schedule. #td2013fi