ryan neptune

I suspect `(name, context)` [as parameters](../blob/a235704e5f823889ce8e5e4b7fa92b2ba54d7901/bean.js#L10-L12) is problematic for AMD because `define(definition)` [assumes default dependencies](https://github.com/amdjs/amdjs-api/wiki/AMD#dependencies-). `name` would be `require`. `context` would be `exports`. If `noConflict()` is needed, I'd create it...

Duplicate of #80 Yes we should fix this.

@rvagg I can tackle this within the next week or so. @ded Not lots but including it would help [normalize the handler signature](./80) between all events: native, custom, triggers. For...

Sounds like a plan.

A standalone solution I often use in my own modules is to create the `.fn` methods in the main file (not in the ender bridge) such that they are callable...

Maybe bean deserves its own simple wrapper: ``` js function Bean(o) { [].push.apply(this, null == o ? [] : o.nodeType || o.window == o ? [o] : o); } function...

@frosas @brianhaveri I've been pondering this issue too. I like the idea of using [overloading](http://php.net/manual/en/language.oop5.overloading.php). I think it'd be best to do it in reverse (using `__call` rather than `__callStatic`):...

@joseym Thanks - although not quite as good as how I originally thought. See my edit above. It's basically the reverse of what @frosas has.

Yo watch [this video](http://www.youtube.com/watch?v=-VBoTq4sTWk) I think "attr" functionality is a great idea. Something like this I reckon: ``` javascript Response.create({ prefix: "placeholder" , attr: "placeholder" // < does not exist...

@alanhogan Cool / I'll add the attr functionality in soon ( prob. early Sept ). It should be easy enough. There are several issues with the event methods that I'm...