Mooish Repository Template and an All-JsonP Showcase

Sunday, December 28th, 2008 @ 1:18 pm | filed under: 3rd Party Libraries, Examples, Organizing Code, Server-side Integration

Ian Collins is apparently hooked on MooTools because he sure has been writing a whole heckuva lot of it. He emailed me a few days back about his site that is all dynamically built off Twitter, Flickr, and other sources using JsonP to fetch all the data. The entire experience is built in JavaScript. Looking at the source of his site you find this lovely little easter egg:

<body>
  <-- I win at SEO -->
</body>

The source of the site itself is all cleanly written MooTools classes, reminding me of my thoughts on programming to patterns.

He’s also released through github a project structure based on MooTools and Clientcide tools and conventions. This is basically how I organize all the Clientcide code along with both test frameworks (Ian includes ScrewUnit – while Clientcide and MooTools use JSSpec, but they both do the same thing – and my Unit Test Framework).

Included also are some ruby scripts for compiling libraries and a demo page that builds a library on the client side.

The only two things that are missing, if you ask me, are a docs engine (like the one in my Clientcide repository that is all javascript driven), but maybe it doesn’t make sense for all projects to think that people are going to author mark-down files for documentation.

The other thing that’s missing is a compressor. It would be nice to see it include the YUI compressor as an option for the build script. It would also be nice to see it include my dbugScripts method wrapper, which I find is very useful in switching between compressed and uncompressed files on the fly.

Still, if you’re looking for a nice template to kick-start your own codebase organization, this is a wonderful package to consider. Nice work Ian.

No TweetBacks yet. (Be the first to Tweet this post)

This entry was posted on Sunday, December 28th, 2008 at 1:18 pm and is filed under 3rd Party Libraries, Examples, Organizing Code, Server-side Integration. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

3 Responses to “Mooish Repository Template and an All-JsonP Showcase”

  1. Ian Collins Says:
    December 29th, 2008 at 11:19 am

    Here is a link for the Mooish template: http://github.com/3n/mooish-template/tree/master

    Also, the source for my personal site can be found here: http://github.com/3n/3n.github.com/tree/master

    I plan on including your doc engine, just haven’t gotten around to it yet (Mooish is open source…). Also, I didn’t have a need for a compressor as most of my work is for powerset.com where our assets are packed by Merb and I wanted the source to stay intact for my personal site. Once again, it would be a nice addition to this open source project…

    And yes, your “programming to patterns” post really summed up how I feel about Javascript (specifically Mootools) development. Everyone should read it.

    Thanks for the rad post.

  2. Aaron N. Says:
    December 29th, 2008 at 11:52 am

    My bad, I meant to link to the github for the template. woops! I’ll update the post now.

  3. Why You Should Consider Releasing Code » Clientcide (Formerly CNET's Clientside) Says:
    December 31st, 2008 at 10:28 am

    [...] posted the other day about Ian Collins’ Moo-ish Template, a scaffold for putting together your own JavaScript library organized as MooTools does (and as I [...]