Geekup Leeds - Why the YUI?

My small presentation at Web Directions North 2009 introducing YUI as part of the "JavaScript Libraries Super Session"

Brief introduction to Yahoo's YUI library. Given as a presentation to college students who were new to JavaScript. Discusses DOM manipulation,

Last year, AOL adopted a new content strategy and has positioned itself as a premier destination for original content. Core to this strategy is having reusable, highly efficient and optimized common code and experiences at scale, which is where jQuery comes in. Check in with Dave Artz to see how jQuery has helped his front-end standards team tackle unique challenges like optimizing 3rd party widget performance, overriding plugin functionality, and managing dependencies and updates across 100+ sites spanning multiple back-end platforms.

This presentation will be a quick introduction to YUI version 3.3.0 and some of its core functions that should be most useful for building your hacks. We'll cover DOM manipulation and event subscription, animations, drag and drop, Ajax and YQL, and how to use CSS Grids for layout.

The Yahoo Developer Network provides APIs and services for many Yahoo products and services, including search, answers, Flickr, and more. It allows developers to access Yahoo's data through RESTful APIs. It also provides tools for mixing and matching data as well as UI frameworks. The document discusses several Yahoo APIs and services that can be used to build applications that incorporate Yahoo data and functionality.

Christian Heilmann discusses how the Yahoo! User Interface (YUI) library provides control for developers. YUI offers modular components that deal with specific tasks like DOM manipulation, events, animation, and debugging. It provides standards-based solutions with separation of concerns. YUI gives developers control through features like custom events, namespaces, validation, and debugging tools. It helps avoid issues across browsers and situations outside a developer's control.

My presentation at mashed in London describing the pains I went to to get there and the things Yahoo offers for developers.

My slides from the "Exceptional Website Performance with YSlow 2.0" show at CSDN (China Software Developers Network) in Beijing, Dec 6, 2008

The document discusses libyui, a library that provides abstraction from GUI and TUI toolkits to allow creating user interfaces that can run on multiple platforms from a single codebase. It demonstrates a simple "Hello World" application in C++, Perl, and Python using libyui. It also covers libyui internals, language bindings, debugging tips, and places to find documentation.

1) The document discusses various approaches for implementing copy and paste functionality for contacts in email applications using the Yahoo! UI library (YUI). 2) Key challenges include inconsistent browser clipboard APIs and security restrictions that require user-initiated actions for copying content. 3) The proposed solution is a YUI node plugin called "gallery-clipboard" that provides a normalized event interface between JavaScript and Flash to allow copying in response to user events like mouse clicks or key presses.

This document provides an introduction to creating custom widgets using the Web Tools Platform (WTP) and the Dojo JavaScript library. It discusses loading Dojo, using modules and classes, and creating a custom widget with a class and template. The document encourages readers to get involved by joining a newsgroup or filing bugs to provide feedback on WTP.

This document provides an overview of popular JavaScript libraries including Dojo Toolkit, YUI, Prototype, and jQuery. It discusses problems they aim to solve like cross-browser inconsistencies. Key features of each library are mentioned like Dojo's widgets, YUI's controls, Prototype's Ruby-like syntax, and jQuery's chaining and node selection. The document also covers ideas from the libraries like progressive enhancement, animation APIs, and leveraging hosting on CDNs.

The document discusses different approaches to using JavaScript libraries, including plug-and-play widgets, libraries that require some coding, and writing raw JavaScript from scratch. It then examines popular open-source JavaScript libraries like Prototype, jQuery, Yahoo UI, and Dojo, comparing their features, functionality, and widgets. The ideal library should have a robust core feature set along with user interface widgets, active development and support, and good documentation.

The document introduces Django, an open-source web framework written in Python. It provides an overview of Django, including its MVC structure, status updates, installation guide, basic tutorials, and features such as forms, generic views, sessions, caching, middleware, and its standard library. The document encourages learning additional skills like HTML, CSS, JavaScript, and SQL to become a strong web developer using Django.

jQuery 1.9 will be cleaning up the library's API, but even so there are still features that should be used with care--or avoided completely.

The document discusses the evolution of the YUI JavaScript framework architecture. Some key changes include a modular design that allows discrete modules to be loaded independently, a common component foundation using attributes and events, and a Node API that provides a normalized way to interact with DOM elements.

The document introduces jQuery, an open source JavaScript library that simplifies HTML and JavaScript interaction. It allows selecting elements, traversing DOM trees, manipulating elements, handling events, and adding effects. jQuery is extensible through thousands of plugins and the official jQuery UI includes widgets and interactions. The document recommends learning jQuery through books, blogs, Twitter accounts, and experimenting with the many demos and examples available.

We are obsessed with coding and creating automated workflows and optimisations. And yet our final products aren't making it easy for people to use them. Somewhere, we lost empathy for our end users and other developers. Maybe it is time to change that. Here are some ideas.

This document discusses ways to improve how web developers learn best practices through browser and tooling improvements. It suggests that linting and inline insights directly in code editors could help prevent mistakes by flagging issues early. A tool called webhint is highlighted that provides one-stop checking and explanations of hints related to performance, accessibility, security and more. The document advocates for customizing hints based on a project's specific needs and environment. Overall, it argues for accelerated learning through context-sensitive, customizable best practices integrated into development workflows.

This document discusses privilege in the context of social media and the internet. It acknowledges privileges like internet access, the ability to communicate, and supportive online communities. It warns that machine learning and algorithms risk creating echo chambers and guided messaging if they are not kept in check by human curation. The document advocates taking back the web for decent, thinking and loving humans and using privileges to help others gain access to learning, communication, and communities.

JavaScript is a bigger world than a language these days. Time to take stock and find happiness in that world.

This document discusses artificial intelligence and how it can help humans. It covers that AI is not new, having originated in the 1950s, and is now more advanced due to increased computing power. It also discusses how AI utilizes pattern recognition and machine learning. The document then covers several applications of AI including computer vision, natural language processing, sentiment analysis, speech recognition/conversion and moderation. It notes both the benefits of AI in automating tasks and preventing errors, as well as the responsibilities of ensuring transparency and allowing people to opt-in to algorithms.

The document discusses concerns about the perception and realities of coding careers. It expresses worry that coding is seen solely as a way to get a job rather than as a means of problem-solving. While coding can provide fulfilling work, the document cautions that the need for coders may decrease with automation and that the role may evolve from coding to engineering. It suggests a future where machines assist with repetitive coding tasks and people focus on delivering maintainable, secure products with attention to privacy and user experience.

PWA are a hot topic and it is important to understand that they are a different approach to apps than the traditional way of packaging something and letting the user install it. In this keynote you'll see some of the differences.

This document discusses privilege in technology and perceptions of technology workers. It acknowledges the privileges that tech workers enjoy, such as access to resources and high demand in the job market. However, it also notes problems like peer pressure, lack of work-life balance, and imposter syndrome. Both tech workers and the public have skewed perceptions of each other - tech workers feel others do not appreciate or understand their work, while the public sees tech workers as antisocial or caring only about profit. The document encourages taking small steps to improve the situation, such as being kind to oneself, considering others, sharing knowledge, and focusing on quality over quantity of work.

The document provides five ways for JavaScript developers to be happier: 1) Concentrate on the present and focus on creating rather than worrying about the past or future. 2) Limit distractions by streamlining your development environment and using an editor like VS Code that consolidates features. 3) Make mistakes less likely by using linters to catch errors as you code. 4) Get to know your tools better like debuggers to avoid console.log and gain insights to build better solutions. 5) Give back to others in the community by being helpful rather than causing drama.

The document discusses progressive web apps (PWAs) and provides suggestions for improving them. It notes that while PWAs aim to have engaging, fast, integrated, and reliable experiences like native apps, they still have room for improvement in areas like speed, integration, and reliability. It emphasizes that PWAs should adhere to web best practices and provide actually useful experiences rather than just focusing on technical features. The document encourages helping the PWA effort by providing feedback, using and contributing to tools, keeping messaging up-to-date, and promoting high-quality examples.