Deprecating event()

[nbubna]

So, those reading the code will see that event() has landed but is not yet exposed in the main documentation on the gh-pages branch nor in a published/tagged release.

I'm hesitating on this, because i'm concerned it might be "bloat". addEventListener and friends are obviously part of the DOM interface HTML exposes, but not all of the DOM is about HTML. (notice i called the library HTML.js, not DOM.js)

After finishing the event.js code, i started to feel that it was suffering under the constraint of being in HTML.js and expanding the scope and weight of HTML.js in the process. It might be better suited for a separate library, where it can be free of HTML's constraints and grow a bit larger (there are other features i envision for it).

Obviously, if i pull it out to a separate library, it can still integrate smoothly with HTML.js, via HTML._.fn.

Any one out there have thoughts on this?

[jtenner]

I think that you're right on with your philosophy on the matter.
Especially with HTML being the kind of library that it is.

I'd say make a new library.

On Tue, Aug 13, 2013 at 1:37 PM, Nathan Bubna notifications@github.comwrote:

So, those reading the code will see that event() has landed but is not yet
exposed in the main documentation on the gh-pages branch nor in a
published/tagged release.

I'm hesitating on this, because i'm concerned it might be "bloat".
addEventListener and friends are obviously part of the DOM interface HTML
exposes, but not all of the DOM is about HTML. (notice i called the library
HTML.js, not DOM.js)

After finishing the event.js code, i started to feel that it was suffering
under the constraint of being in HTML.js and expanding the scope and weight
of HTML.js in the process. It might be better suited for a separate
library, where it can be free of HTML's constraints and grow a bit larger
(there are other features i envision for it).

Obviously, if i pull it out to a separate library, it can still integrate
smoothly with HTML.js, via HTML._.fn.

Any one out there have thoughts on this?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1
.

[arthurbarros]

@jtenner +1

[nbubna]

Thanks for the input, folks. I resolved this morning to pull event stuff out to a separate project, though that's sure to be an interesting challenge. I'm considering making it even more interesting by merging it with the richer native event world of http://github.com/nbubna/trigger just to keep me on my toes. :)

[nbubna]

For anyone who finds this that was interested in the event.js code, i currently plan to move it here: http://github.com/nbubna/Eventi

My intention is that Eventier will, in its primary dist artifact, plug itself into HTML.js with no effort on your part beyond inclusion. It will likely also provide more features than event() alone could bear.

[nbubna]

since https://github.com/nbubna/Eventi is now in useable condition (needs docs, though), i am going to pull event.js out of the main build and bump the minor version number. It will remain available in the dist and in the source as a separate artifact for the remainder of the 0.x branch, at least.