sdesai

USE CASES

• Render widgets on NodeJS, where DOM is absent.
• Optimize rendering of Widgets at scale (1000s of TreeViewNodes).

GOAL

• Avoid all Node references from Widget through the end of renderUI().
• bindUI()/syncUI() will still have Node references (to bind events and incrementally update DOM).

Satyam

/*
App plugins can be loaded over an instance of App by setting a route with a wildcard path
such as:
{
	path:'/:app/*', 
	callback: 'dispatchApp'
}
 where the app param is the module name of the plugin, 
 which should have its entry in the YUI config file (unless loaded by some other means)
*/

rgrove

var express = require('express'),
    app     = express.createServer();

app.configure(function () {
    // Use our custom Handlebars-based view engine as the default.
    app.register('.handlebars', require('./view'));
    app.set('view engine', 'handlebars');

    // ...
});

rgrove

{
    // enforcing options (true means potentially more warnings)

    "adsafe":       false,  // true if ADsafe rules should be enforced. See http://www.ADsafe.org/
    "bitwise":      true,   // true if bitwise operators should not be allowed
    "curly":        true,   // true if curly braces should be required around blocks in loops and conditionals
    "eqeqeq":       true,   // true if === should be required (for ALL equality comparisons)
    "forin":        false,  // true if unfiltered 'for in' statements should be forbidden
    "immed":        true,   // true if immediate function invocations must be wrapped in parens
    "newcap":       true,   // true if Initial Caps must be used with constructor functions

zachleat

// * iOS zooms on form element focus. This script prevents that behavior.
// * <meta name="viewport" content="width=device-width,initial-scale=1">
//      If you dynamically add a maximum-scale where no default exists,
//      the value persists on the page even after removed from viewport.content.
//      So if no maximum-scale is set, adds maximum-scale=10 on blur.
//      If maximum-scale is set, reuses that original value.
// * <meta name="viewport" content="width=device-width,initial-scale=1.0,maximum-scale=2.0,maximum-scale=1.0">
//      second maximum-scale declaration will take precedence.
// * Will respect original maximum-scale, if set.
// * Works with int or float scale values.

rgrove

Attribute Value Filters

With more and more application logic moving to the client, and with YUI becoming more popular on the server, it's increasingly important to design APIs that handle user input safely. Currently, YUI modules that store user input in attributes must do one of two things: either escape user strings before setting an attribute, or escape them manually before using them.

Escaping automatically before storing the value is safest, but also inconvenient if you sometimes need the unescaped value, since you must then store two versions (probably in two different attributes). This can lead to API clutter and confusion. Escaping manually before use avoids API clutter but increases the likelihood of mistakes, and also clutters up the codebase in general. It significantly increases the chances that another developer who is unaware of the need to escape the value will inadvertently introduce a security vulnerability.

Proposal

Attribute should provide a consistent, pluggable API for retrieving

davglass

{
    "name": "YUIDoc",
    "description": "YUIDoc documentation tool written in Javascript",
    "version": "0.1.0",
    "url": "http://yuilibrary.com/projects/yuidoc",
    "options": {
        "external": {
            "data": "http://yuilibrary.com/yui/docs/api/data.json"
        },
        "linkNatives": "true",

lsmith

Data normalization API proposal

Data API normalization/centralization in three layers

1. transport layer

2. transaction layer

3. encapsulated configuration layer (aka Resource/DataSource)

4. Transport layer

tivac

Parent/Child Y.Views

As I worked with Y.App it became clear that while Y.View is a great abstraction it would be easy to overwhelm a single instance with way too much functionality. This is my attempt to solve that issue by allowing multiple child views to be attached to a single parent view via an extension.

Usage

The extension is mixed into the parent view like any other extension using Y.Base.create.

var Parent = Y.Base.create("view", Y.View, [

rgrove

/*!
Copyright (c) 2012 Ryan Grove. All rights reserved.

Redistribution and use of this software in source and binary forms, with or
without modification, are permitted provided that the following conditions are
met:

  * Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.