openMIC barcamp 11.02.2010

HTML5 provides new semantic elements, forms, and multimedia capabilities without plugins. While support is still evolving, HTML5 can be used today with feature detection and polyfills for older browsers. Key features include <video>, <audio>, <canvas>, geolocation, and application cache APIs. HTML5 aims to unify browser support for emerging web standards, but support varies - it is best to use progressive enhancement and have fallback options. Overall HTML5 enhances the web platform, but may not completely replace other technologies like Flash in the near future.

This document provides an overview and introduction to the webOS platform. It discusses the webOS architecture including application architecture using stages and scenes. It covers building a basic "Destroy World" app using the command line tools. It also discusses the webOS emulator, advanced APIs like camera, storage and accelerometer access. Finally it discusses submitting apps to the webOS app catalog and a promotion for hot new apps.

Tony Parisi is a serial entrepreneur and consultant architect who has authored a book on WebGL. He provides an overview of using WebGL for game development, including what WebGL is, popular frameworks like Three.js, techniques for loading models, animating scenes, implementing interaction, creating particle systems, and integrating 2D and 3D. He also discusses considerations for making WebGL games robust and putting all the pieces together.

This document discusses the technologies behind the HP webOS platform, including Enyo and Node.js. It provides an overview of Enyo, describing it as a framework for building web applications that targets developers and supports flexible layouts, device and desktop applications, and code reuse through components. It also discusses Node.js and how it is used as the runtime for webOS services, allowing applications to access system services and process data without blocking the user interface. The architecture of webOS applications is also summarized, including how the Enyo framework is used to build the user interface and application structure.

The document discusses ways to improve the performance of hybrid mobile applications that use WebView. It describes how WebView has less powerful capabilities and worse web standard compatibility compared to mobile browsers. This can cause issues like fragmentation across device versions. The document proposes techniques for creating a high-performance WebView, including adding new capabilities like WebSockets, and replacing slower native elements like Canvas 2D with optimized custom implementations. It provides code examples for calling JavaScript from native and vice versa on Android and iOS. Lessons learned emphasize minimizing native/JavaScript communication and dealing with threading issues.

This document discusses HTML5 on mobile devices. It begins by explaining why mobile web is growing and why HTML5 is well-suited for mobile. It then provides an overview of what HTML5 is and examples of features like forms, multimedia, geolocation that can be used on mobile. It also discusses considerations for mobile web development like responsive design and frameworks. The document recommends tools for mobile debugging and testing performance.

This document discusses cross-platform mobile development using Xamarin and Visual Studio. Key points include: - Using C# and .NET with Xamarin allows building iOS, Android, and Windows Phone apps with one shared codebase while still getting native performance and user experience. - The code compiles to native for each platform, rather than being interpreted, and full access to platform SDKs is provided. Shared code, data layers, and platform abstractions allow code reuse. - Visual Studio solutions can contain projects for shared code, platform-specific code for each mobile OS, and tests. Linking or portable class libraries are recommended for sharing code. - Considerations include designing native U

This document discusses background capabilities in iOS 7. It summarizes the three new background modes available: background fetching, remote notifications, and background transfers. Background tasks now run for 3 minutes instead of 10 minutes. Apps can now download content in the background in response to push notifications or on a scheduled basis using background fetch APIs. Developers have close control while Apple prioritizes battery life and network usage.

A CocoaDynamicFramework is a collection of compiled code and public headers that can be shared between applications and extensions to avoid duplicating code. It provides extensions, code sharing between apps, and public distribution. Dynamic frameworks allow updated code to be used without relinking applications. CocoaPods can be used to manage frameworks and extensions need to check for availability on iOS since some classes are not available. Frameworks have visibility settings of public, private, or project.

HTML5 and its related technologies are enabling new ways to build beautiful sites and applications for contemporary mobile devices. Native mobile developers can now use web technologies to surmount cross-platform headaches, and desktop web developers can reach mobile users in familiar, app-like ways. This session explores the state of the art in HTML5-based mobile web frameworks, and demonstrates the practical possibilities that this powerful and standards-based approach can bring.

Vue.js is described as a "boring" framework that helps developers get work done without unnecessary complexity. It borrows best practices from other frameworks like React but aims to have simpler dependencies and templates. Vue.js uses reactive templates that can be written with plain JavaScript or JSX, and allows separating component logic from presentation with single file components. It also avoids unnecessary re-renders through its reactive system. The document demonstrates how Vue.js can be preferable for teams with mix of experience levels due to its flexibility and lack of complexity compared to other frameworks like React.

This document summarizes the Firefox OS, an open web platform for building mobile apps and customizing the user interface using HTML5, CSS, and JavaScript. It outlines key web APIs, the process for developing and publishing open web apps, and the different types of apps including regular web apps, installed web apps, and privileged web apps with additional capabilities. Security levels and permissions for APIs are also discussed.

In a world dominated by React and Angular, Vue is the open source framework that brings a third alternative to the table, combining the strengths of the first two while trying to weed out their weaknesses. The result is an easy to use, lightweight and versatile framework. In this talk we will explore Vue's architecture, see how components interact among themselves, have a look at the event model and in the end, how to wrap everything together in a SPA using Webpack.

Rendr is a JavaScript library that allows Backbone.js applications to run on both the client and server sides. It provides common classes and logic that can be reused across both environments, such as BaseView, BaseModel, and routers. On the server, it renders the HTML output using the same application logic. On the client, it hydrates the views by attaching them to the corresponding DOM elements. The goal is to write application logic in a way that is agnostic to the environment, avoiding duplicating code or context switching between client and server implementations.

Doing it, then doing right and finally improving. Have you ever had the feeling that your jQuery could run faster? And isn’t that the natural evolution of a developer? From new browser features and well known techniques to script breakup, sizzling, chaining and selector comparison... Tuning of any technology requires deep understanding of its core principles. In order not to just guess we need to learn how browsers execute JavaScript and how jQuery is built. If these issues have been bothering you recently – join us to see how or share your experience.

This document discusses using Polymer mixins and Vaadin Elements to create reusable CRUD components. It introduces CrudListMixin and CrudItemMixin that provide APIs for list and item views. A <crud-view> element wraps the grid and editor. The components support filtering, sorting, validation, theming and can retrieve/modify data from sources like PouchDB. A step-by-step demo shows integrating the components for a user management app.

Vue.js is an open-source progressive framework for building user interfaces that focuses on the view layer. It has a virtual DOM and reactive components. Its core is small and works well with companion libraries. Single file components allow importing of templates, logic, and styles. Popular companion libraries include Vuex for state management and Vue Router for routing. The Vue CLI makes it easy to scaffold Vue projects with features like routing, lazy loading, and preloading for improved performance.

The document summarizes a meeting of the Open Annotation Collaboration (OAC) project team. The OAC aims to develop an interoperable annotation model and specification to facilitate sharing annotations across systems. In phase 1, the OAC will analyze existing annotation practices, develop a data model and specification, integrate annotation tools into Zotero, and create a proof-of-concept implementation.

Talk including tips and tricks on how to bring up a performance culture showing of various tools to monitor performance related metrics.

This document provides an overview of HTML5 and XHTML2. It discusses the history of each standard, including periods where work took place outside the W3C. Key differences are that HTML5 focuses on evolving the existing web incrementally to support applications, while XHTML2 aimed to switch to a more declarative XML-based approach. HTML5 is natively supported in browsers, while XHTML2 likely remains most useful for server-side authoring.

Presentation made at The Future of Books at Olswang March 19 along with Gerd Leonhard, Media Futurist and Clive Rich, Rich Futures.

Presentation on integration of W3C and WebKit test

Au coeur des applications Web riches, de HTML5 ou des applications Web mobiles, JavaScript est désormais incontournable. Sa communauté très dynamique a contribué à créer un écosystème complet pour répondre aux problématiques courantes de test, qualité du code ou intégration continue comme l'a fait avant elle la communauté Java il y a pas loin de dix ans... Parmi les projets les plus observés du moment, c'est curieusement côté serveur que JavaScript fait le plus parler de lui avec Node.js, un environnement de développement Web qui cultive sa différence. Téléchargement du Coding Kata :

Expanded version of my "Making your site mobile-friendly" speed talk, delivered via Skype for the Russian Internet Technology (RIT) conference, Moscow, 12 April 2010

Patrick Lauke gives an overview of new web technologies available in HTML5, including canvas, video, geolocation, offline support, storage and more. He discusses the history and development of HTML5, how it standardizes current browser behavior, and new powerful form and semantic elements. Patrick provides demonstrations of canvas, video, geolocation and other features, noting their importance for building applications without plugins. He encourages developers to start using these technologies today.

This document appears to be a presentation about web standards given by Zibin Cheah on December 8, 2009. The presentation discusses the history and development of web standards including HTML, CSS, and SVG. It provides examples of how Opera browser supports these standards and highlights some of its features like Opera Unite and Turbo which allow file sharing and faster page loading. The presentation concludes by thanking the audience and providing contact information for further details.

These are the slides from the talk that Brian Ford and I did at Philly ETE 2013.

My presentation about the HTML5 canvas element at the Standards.Next Meetup in London, 27 June 2009. Current and future implementations of canvas in games, applications, and video.

Bruce Lawson of Opera toured Indonesian Universities discussing web standards, HTML5, CSS Media Queries and cross-device development.

1. Open web standards democratize the web by making it accessible to people with disabilities or without the latest hardware, and reduce reliance on any single vendor. 2. Adaptive content and responsive design allow a single website to work well on any device through techniques like CSS media queries. 3. The browser is emerging as a platform for applications through standards like HTML5, widgets, and JavaScript APIs that programmatically access device capabilities like contacts and cameras.

Forget the empty "Web 2.0" buzzword! Web development, however, is changing. In this session, Bruce gives and overview of HTML5, its intelligent forms, scriptable images and native video. Together with CSS3 and SVG, it will change the way you work making it easier to develop exciting applications. The emergence of more and more Web-enabled devices presents headaches: do you write and test many sites for different devices, or make one site for all? Some simple techniques help you write one site to work everywhere, saving you time and grey hairs. Web development 2.0: Web workers of the world, relax!

W3C Widgets are applications developed with web standards that can run across different mobile platforms using the browser engine. A widget consists of an index.html file, assets, and a config.xml file packaged into a .wgt file. Widgets take advantage of HTML5 features like the Application Cache, WebSQL storage, and local storage. They can run on browser runtimes including Opera Mobile, Widgeon, Windows Mobile 6.5, Nokia Qt Web Runtime, and Apache Wookie. The W3C is working to define JavaScript APIs for contacts, calendar, media capture, and messaging to provide more capabilities to widgets.

Open web standards are beneficial because they make the full web accessible to more people and devices, reduce reliance on single vendors, and can increase profits. Some key benefits of open standards include being royalty-free and not tied to specific vendors. HTML5 introduces new form elements, canvas, video, and audio elements to standardize functionality without plugins. With tools like CSS media queries and W3C widgets, content can be adapted for different devices by using the browser as a platform instead of each device's native operating system, bringing the web to more users.

The document discusses the origins and development of HTML5. It describes how in 2004, the W3C was focused on XHTML 2.0 but browser developers grew concerned about single-vendor solutions filling gaps without standards. Opera submitted a paper to the W3C proposing a unified web applications standard with principles like backwards compatibility and avoiding device-specific profiling. This led to the WHATWG forming in 2004 to develop new web standards, producing HTML5. The document outlines key HTML5 design principles and new features like SVG, CSS, geolocation and forms.

The document discusses the development of HTML5 multimedia capabilities. It describes an experimental <video> element being implemented by Opera that provides a simple JavaScript API for controlling video playback. Issues around choosing a baseline video format that is universally supported are also discussed, along with considerations for audio formats and giving users options to play video across different browsers. The maturity of various HTML5 multimedia features is assessed.

A general overview of HTML5, CSS 3, CSS Meedia Queries, mobile, DAP. You might find the organically-grown hand-selected list-of-links-o-rama™ at http://my.opera.com/ODIN/blog/over-the-air-2010-bruce-lawsons-web-developments-2-0-talk to be useful.

The document discusses the future of web technologies, focusing on three main areas: 1. New web standards like HTML5 that provide more capabilities without plugins through elements, forms, canvas and video. CSS3 media queries also allow adaptive content for different devices. 2. Adaptive content through media queries and responsive design can make sites work across devices that vary in screen size, input, and capabilities. 3. The browser is emerging as a platform through widgets, JavaScript APIs and the browser runtime, allowing development across devices without writing for each platform natively. Standards will make the browser a ubiquitous platform.

Extended version of my "Making your site mobile-friendly" talk, including a short look at native applications vs web apps, for the UKOLN DevCSI event "Developing for Mobile Applications in Education" in Reading http://www.ukoln.ac.uk/events/devcsi/mobile_applications/

This document discusses various techniques for making web applications work offline and with unreliable network connections, including: - The application cache manifest which allows specifying cached resources to work offline - Issues with the current manifest specification and potential enhancements - The window.applicationCache API for caching resources and monitoring cache status - Detecting online/offline status using the navigator.onLine property In 3 sentences or less, it summarizes approaches for offline web applications using the application cache manifest, applicationCache API, and navigator.onLine property.

This document discusses how HTML5 can be used to build engaging mobile applications. Key features covered include offline storage using the Application Cache API, storing data locally using Web Storage, using a SQL database with Web SQL, advanced graphics capabilities with Canvas and SVG, real-time communications over WebSockets, and tools for developing HTML5 apps like jQuery Mobile, Sencha Touch, and Google Web Toolkit. It emphasizes testing on multiple platforms and browsers to ensure compatibility.

Today JavaScript is a ubiquitous runtime.  JavaScript is everywhere - from Browser,  server side, embedded device, mobile and gaming. JavaScript can be leveraged to write once and run everywhere or have a consistent programming style, and drive consistent experience across multiple channels – browser, Servers side, or Native Mobile apps.

Андрій Вандакуров Team Lead та Senior Developer у ELEKS Наскільки круто бути фронтенд розробником і які задачі вже можна вирішувати знаючи тільки JavaScript, HTML и CSS. Тулзи, підходи і технічки; можливості сучасного фронтенда (клієнський та серверний код, роботи та візуалізація данних).

The document provides an overview of various web technologies including: - Fundamental technologies that formed the foundation of the early web such as HTML, URIs, and HTTP. - Real-time communication technologies like WebSockets and WebRTC that enable features like video chatting. - Client-side storage options including LocalStorage, IndexedDB, and PouchDB. - APIs that enable richer user experiences such as the Full Screen API, Page Visibility API, and Vibration API. - Styling techniques like CSS shapes, blend modes, and 3D transforms. - Web component specifications like Custom Elements and Shadow DOM. - Options for building different types of applications including desktop apps, TV apps,

This document provides an agenda for a presentation on building mobile map applications. It will cover 3 approaches to mobile map apps, frameworks for building them like CSS3 and HTML5, and hybrid map apps. It introduces the two presenters, Antoon Uijtdehaag and Andy Gup, and covers topics like why build mobile apps, demos of mobile apps, usage statistics, approaches, frameworks, and hybrid apps. It also includes questions that may come up around topics like panning and zooming maps, loading map layers, performance, and using GPS in surveys.

This document discusses modern web applications using progressive web apps (PWA) and WebAssembly (WASM). It begins by defining a web application and describing challenges like performance issues. It then introduces PWAs and WASM as solutions, explaining what they are, how they work, and providing examples. The document shares links to starter kits and success stories to help readers get started with building modern web apps using these technologies.

This document discusses developing a mobile web application to access data from the Hydstra software database on web-enabled mobile phones. It compares the advantages and disadvantages of developing native applications versus a cross-platform web application. It recommends using the jQuery Mobile framework to build a cross-platform mobile web app that can be accessed on any mobile device with a web browser. The document also discusses tools for developing the app, such as Google Chrome and Eclipse, as well as hosting and administration requirements.

Flutter and Java are compared for GUI development. Both support common layouts like rows, columns and flex boxes. Flutter has material widgets that mimic Android and iOS while Java has Swing/AWT for desktop. Both support common components like text fields, radio buttons, sliders. Key differences are Flutter targets mobile/web while Java targets desktop primarily. Flutter uses widgets for reactive UIs while Java uses MVC/MVP frameworks.