jQuery Conference 2012 keynote

This document compares several major JavaScript libraries, frameworks, and toolkits to help determine which is best for a given project. It defines the differences between libraries, frameworks, and toolkits. Features like modularity, code structure, utilities, and user interface capabilities are compared for libraries like jQuery, MooTools, AngularJS, BackboneJS, Dojo and YUI. Considerations around when to use MV* patterns and support, community, and usage statistics are also discussed.

Come and see the future of jQuery Templates, as it moves from Beta1 towards a V1 product. The new jQuery Templates is taking two forms: JsRender – lean and mean, for fast rendering of templates as strings, and JsViews – for powerful interactive browser apps in which Data Link and Templates work hand-in-hand. See how with declarative data linking and templating together, creating powerful data-driven UI is easy, whether using MVVM patterns or binding directly to JSON, and whatever the richness or complexity of the underlying data. jQuery UI is already building its future data-bound widgets on top of this technology. With JsViews and JsRender integration between jQuery UI controls and your own data and UI becomes trivially straightforward.

This document discusses JavaScript MV* frameworks and recommends Exoskeleton as a lightweight alternative to popular frameworks like AngularJS and Backbone. It compares the frameworks based on code size, community support and complexity. While frameworks provide structure, Exoskeleton extends Backbone to be faster and more customizable. The document argues Exoskeleton allows more control over code and fewer dependencies than larger frameworks. An example TODO app demonstrates how to use Exoskeleton.

A presentation I gave at ALT.NET Melbourne on February 26 2013 : http://www.basarat.com/2013/03/knockout-vs-angularjs-mvvm-frameworks.html

Introduction and Comparison of polpular JS Frameworks Knockout, Ember, Angular and Backbone. The presentation descrobes How and when to select each framework.

The document discusses plans to merge jQuery UI and jQuery Mobile to create code that works across all devices and environments. Key points include: 1) Creating a shared CSS framework and responsive widgets for layouts and user interfaces. 2) Developing techniques like SVG icons with PNG fallbacks to optimize performance across different platforms and devices. 3) Building a common widget factory and APIs to create reusable and customizable interface elements that work with or without JavaScript. 4) Continuing to improve form controls and other widgets to provide consistent styling and interactions across all form factors.

HTTP 2.0 makes the existing web faster, but there are things that web devs can do to make their sites and apps even better with very little work.

Web sites can be fast and responsive once you understand the process web browsers use to load and run web pages. We'll look at using tools like WebPageTest to analyze and optimize web pages.

AngularJS is a client-side JavaScript framework that allows developers to create single page applications. It provides two-way data binding, MVC architecture, templates and custom directives to help build testable web apps that can scale. Some key features include data binding, controllers, expressions to dynamically display data, modules to organize code, and services to handle back-end communication. Overall, AngularJS streamlines web development by handling many common tasks like DOM manipulation, data binding and communication with backend services.

This document discusses using jQuery Templates and Data Link to build dynamic data-driven browser applications. It describes how jQuery Templates can be used to render templates from data but offers limited interactivity. jQuery Data Link allows binding data to HTML but has no templating. The presentation previews a new approach called JsViews that integrates Templates and Data Link to provide both fast rendering of templates to static HTML strings as well as fully interactive and responsive views through two-way data binding between templates and JavaScript data objects.

Webpack is a module bundler that packs JavaScript files and their dependencies into small bundles for efficient loading on the browser. It builds a dependency graph by walking through imports and outputs bundles or individual files. Loaders allow transforming assets and piping them together, like using babel-loader to transpile JSX to ES5 and css-loader to bundle CSS. This summarizes the key points about Webpack's purpose, how it builds dependencies, and the role of loaders.

The document discusses the history and evolution of JavaScript packaging and module bundling from 2000 to the present. It covers early approaches using individual script tags to load JS files, the introduction of minification tools like JSMin in 2003, concatenating files together in the late 2000s, module loaders like RequireJS in 2009, the rise of Node.js and package managers in 2010, and the modern dominance of bundlers like Webpack since 2014 which use loaders to bundle dependencies and assets into single files or chunks.

Sails.js makes it easy to build custom, enterprise-grade Node.js apps. It is designed to resemble the MVC architecture from frameworks like Ruby on Rails, but with support for the more modern, data-oriented style of web app development. It's especially good for building realtime features like chat.

The best reason for writing tests is to automate your testing. Without tests, you'll likely be testing manually. This manual testing will take longer and longer as your codebase grows. In this session, you’ll learn how to test an Angular 2 application. You'll learn how to use Jasmine to unit testing components and Protractor for integration testing. We’ll also take a look at code coverage options and explore continuous integration tools.

Slides from Flexible UI Components talk given at Web Unleashed 2017 Build UI components that work seamlessly in every JavaScript Framework. Your core UI elements shouldn’t have to be different for your marketing site than they are in your application just because the former uses jQuery while the latter is built using Angular or React. Lessons learned from work on ZURB Foundation 7.

“There is no doubt AngularJS is one of the hottest JavaScript and Single Page Application (SPA) frameworks in use today. Is Angular just a bunch of hype, or is there substance behind its promise of teaching HTML new tricks? Join iVision principal architect Jeremy Likness when he shares his hands-on experience developing a massive Angular enterprise application with globally distributed teams of dozens developers over a period of several years. See practical examples of Angular and learn about the various concepts that make it a useful framework that isn’t as opinionated as other options in the market. Beginners will benefit from understanding what Angular does and how it impacts the bottom line of technology, people and process and experienced developers will learn best practices and advanced techniques from Jeremy’s extensive Angular experience. There’s something for everyone so be sure to RSVP now!”

How did a small, completely self-funded team build a web framework that became more popular than comparable tools with million-dollar budgets? By welcoming the outsiders. Mike will recount how Sails.js grew from an internal tool to one of the most popular frameworks for Node.js, without forgetting its roots. In this talk, Mike will reflect on the experiences he and his team have had building and managing an open-source Node.js framework, Sails.js. He'll discuss the success they've had attracting interlingual developers to Sails, and share some lessons and difficulties they've encountered migrating a new generation of developers from PHP, Java, .NET and Rails to Node.js. There will be discussion of examples from both sides of the spectrum addressing community-related and technical issues with a highlight about overcoming the "maintaining interest" challenge.

This document summarizes Anne-Gaëlle Colom's involvement with open source projects like jQuery and jQuery Mobile. It describes how she started contributing by reporting bugs and inconsistencies, eventually taking on a leadership role rewriting documentation. Her contributions led to opportunities like speaking at conferences, meeting open source leaders, and career advancement. Open source involvement provided learning opportunities that improved her teaching and opened doors for her students.

Unit testing involves writing small tests for individual units or functions of an application to ensure they work as expected. Tests should be written from the start of a project to prevent bugs and regressions. Unit tests allow for collaborative work by different contributors, help automate catching errors, and produce more reliable code by testing features as they are developed. While unit testing requires upfront effort, it saves work in the long run by reducing unexpected bugs that would otherwise be found by users. The testing framework QUnit can be used to write unit tests in separate .js files and run them from an index.html page.

Presented June 8, 2012 (Online) at the 'Access by Touch: Delivering Library Services Through Mobile Technologies' conference sponsored by Amigos Library Services. Description: By the end of 2012, it is expected that more than 80% of the world’s population will have access to a smartphone. Your library users will assume that your library can be accessible from anywhere, at any time, and on any device. Now is the time to be ready! During this webinar, you will: - learn what a mobile framework is. - acquire best practices in mobile Web development. - understand the various technologies (HTML, CSS, JavaScript) and how they work together to build mobile Web apps. - recognize the differences between native and web apps. - have an opportunity to continue to work with Chad after the webinar to demonstrate what you learned. - gain access after the webinar to a free Web server so you can see your mobile Web app live.

Mobile web development frameworks are targeting the builtin web browsers on iPhone and Android only; however, jQuery mobile has in a different vision, one that will reach the largest distribution of phones possible. Leveraging the ways of progressive enhancement, your website can be viewed in raw HTML on old mobile phones and then enhanced with nice CSS styles across mobile platforms that have a decent CSS and JavaScript support. In this session, Grabanski gives you his list of reasons to use jQuery mobile, an overview of the framework and will draw from his experiences building websites on top of jQuery Mobile.