Comments on: Organizing Javascript for Event Pooling with jQuery http://www.michaelhamrah.com/blog/2009/12/organizing-javascript-for-event-pooling-with-jquery/ All the stuff after "Hello, World!" Mon, 16 Jan 2012 14:42:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Chris http://www.michaelhamrah.com/blog/2009/12/organizing-javascript-for-event-pooling-with-jquery/comment-page-1/#comment-306 Chris Mon, 12 Apr 2010 17:30:39 +0000 http://www.michaelhamrah.com/blog/?p=289#comment-306 <p>Thanks for your response. I like the concept of breaking down individual components into their own files.</p> <p>My project can be thought of in this way to an extent. It's a role-based access control application. Basically there will exist a site.js, user.js and admin.js. The idea is based around a js hierarchy. An anonymous user gets site.js, an authenticated user gets site.js and user.js; and an Admin would get site.js, user.js and admin.js.</p> <p>Each script would contain both publisher/subscriber logic, but one file can publish an event while multiple files listen for that same event.</p> <p>Let me know if you spot any flaws in my thinking, but I think this will work perfectly. Thanks.</p> Thanks for your response. I like the concept of breaking down individual components into their own files.

My project can be thought of in this way to an extent. It’s a role-based access control application. Basically there will exist a site.js, user.js and admin.js. The idea is based around a js hierarchy. An anonymous user gets site.js, an authenticated user gets site.js and user.js; and an Admin would get site.js, user.js and admin.js.

Each script would contain both publisher/subscriber logic, but one file can publish an event while multiple files listen for that same event.

Let me know if you spot any flaws in my thinking, but I think this will work perfectly. Thanks.

]]> By: Michael http://www.michaelhamrah.com/blog/2009/12/organizing-javascript-for-event-pooling-with-jquery/comment-page-1/#comment-305 Michael Fri, 02 Apr 2010 12:43:19 +0000 http://www.michaelhamrah.com/blog/?p=289#comment-305 <p>@Chris- Great questions about how to map code to files. There's no easy answer for this. But in general, you want any "global" code in a global file: usually JS related to your header, etc. Shared components/widgets should get their own file. I like to keep most page-related functionality in the same file- keeping related code close together. If this grows too large, split up based on related logic. This should, I hope, be somewhat obvious.</p> <p>No matter what you do, always use a js minifier, like the YUI Compressor.</p> @Chris- Great questions about how to map code to files. There’s no easy answer for this. But in general, you want any “global” code in a global file: usually JS related to your header, etc. Shared components/widgets should get their own file. I like to keep most page-related functionality in the same file- keeping related code close together. If this grows too large, split up based on related logic. This should, I hope, be somewhat obvious.

No matter what you do, always use a js minifier, like the YUI Compressor.

]]> By: Chris http://www.michaelhamrah.com/blog/2009/12/organizing-javascript-for-event-pooling-with-jquery/comment-page-1/#comment-304 Chris Thu, 01 Apr 2010 13:30:31 +0000 http://www.michaelhamrah.com/blog/?p=289#comment-304 <p>Great article, I am always interested in finding better design patterns with JavaScript. I used to write every event listener and handler in my document.ready function and let it rip. That turned out to be a maintenance nightmare. I am starting a new project and I want to implement your event pooling pattern, but I want to pick your brain before I start.</p> <p>For the example you give, how many js files would you create? Would you have a publisher.js and a subscriber.js? Would you instead have one js for just this functionality, i.e. simpleforms.js?</p> <p>What if you had dozens of tasks similar to this form, would you: put them in one giant js file, break them down per task, or separate them into a publisher.js and subscriber.js.</p> <p>Great blog, thanks in advance!</p> Great article, I am always interested in finding better design patterns with JavaScript. I used to write every event listener and handler in my document.ready function and let it rip. That turned out to be a maintenance nightmare. I am starting a new project and I want to implement your event pooling pattern, but I want to pick your brain before I start.

For the example you give, how many js files would you create? Would you have a publisher.js and a subscriber.js? Would you instead have one js for just this functionality, i.e. simpleforms.js?

What if you had dozens of tasks similar to this form, would you: put them in one giant js file, break them down per task, or separate them into a publisher.js and subscriber.js.

Great blog, thanks in advance!

]]> By: Communication Between jQuery UI Widgets - DevPatch.com http://www.michaelhamrah.com/blog/2009/12/organizing-javascript-for-event-pooling-with-jquery/comment-page-1/#comment-303 Communication Between jQuery UI Widgets - DevPatch.com Mon, 22 Mar 2010 20:57:40 +0000 http://www.michaelhamrah.com/blog/?p=289#comment-303 <p>[...] http://www.michaelhamrah.com/blog/2009/12/organizing-javascript-for-event-pooling-with-jquery/ Tags: jQuery, jQueryUI Posted in Blog, JavaScript | No Comments » Share | [...]</p> [...] http://www.michaelhamrah.com/blog/2009/12/organizing-javascript-for-event-pooling-with-jquery/ Tags: jQuery, jQueryUI Posted in Blog, JavaScript | No Comments » Share | [...]

]]> By: Event Pooling with jQuery Using Bind and Trigger: Managing Complex Javascript | Adventures in HttpContext http://www.michaelhamrah.com/blog/2009/12/organizing-javascript-for-event-pooling-with-jquery/comment-page-1/#comment-175 Event Pooling with jQuery Using Bind and Trigger: Managing Complex Javascript | Adventures in HttpContext Wed, 30 Dec 2009 14:05:01 +0000 http://www.michaelhamrah.com/blog/?p=289#comment-175 <p>[...] Check out my follow up article Organizing Events for Event Pooling. [...]</p> [...] Check out my follow up article Organizing Events for Event Pooling. [...]

]]> By: jQuery resources « QuantuMatrix’s Weblog http://www.michaelhamrah.com/blog/2009/12/organizing-javascript-for-event-pooling-with-jquery/comment-page-1/#comment-171 jQuery resources « QuantuMatrix’s Weblog Mon, 28 Dec 2009 17:37:27 +0000 http://www.michaelhamrah.com/blog/?p=289#comment-171 <p>[...] Organizing JavaScript for Event Pooling with jQuery [...]</p> [...] Organizing JavaScript for Event Pooling with jQuery [...]

]]> By: 9eFish http://www.michaelhamrah.com/blog/2009/12/organizing-javascript-for-event-pooling-with-jquery/comment-page-1/#comment-163 9eFish Wed, 23 Dec 2009 02:24:28 +0000 http://www.michaelhamrah.com/blog/?p=289#comment-163 <p><strong>Organizing Javascript for Event Pooling with jQuery...</strong></p> <p>9efish.æ„Ÿè°¢</p> Organizing Javascript for Event Pooling with jQuery…

9efish.æ„Ÿè°¢

]]> By: DotNetShoutout http://www.michaelhamrah.com/blog/2009/12/organizing-javascript-for-event-pooling-with-jquery/comment-page-1/#comment-160 DotNetShoutout Mon, 21 Dec 2009 15:14:45 +0000 http://www.michaelhamrah.com/blog/?p=289#comment-160 <p><strong>Organizing Javascript for Event Pooling with jQuery | Adventures in HttpContext...</strong></p> <p>Thank you for submitting this cool story - Trackback from DotNetShoutout...</p> Organizing Javascript for Event Pooling with jQuery | Adventures in HttpContext…

Thank you for submitting this cool story – Trackback from DotNetShoutout…

]]>