Announcing the first release of batman.js

Post by ktusznio » Thu, Aug 25, 2011, 6:10 AM UTC

nicklovescode wrote: post #9

paulocal wrote: post #4

PLEASE: body{ color: #000000; } Thankkk you! Other than that, looks cool! Definitely will be trying it out in my projects and reporting back!

p { color:#222; } will do

Post by walrus » Thu, Aug 25, 2011, 8:39 AM UTC

maaku wrote: post #62

nciagra wrote: post #15

Earlier quoted context omitted.

Sure, I'll break it down: batman.js is a JavaScript framework for rich JavaScript applications. It's designed to make development as fast and as painless as possible for developers and designers while giving them lots of power. We designed everything around a number of primary goals such as convention over configuration, HTML-based views, and the principle of least surprise. This is something we're using at Shopify i…

Sure, I'll break it down: batman.js is a JavaScript framework for rich JavaScript applications. It's designed to make development as fast and as painless as possible for developers and designers while giving them lots of power. Still nada. What does it actually do ? A framework for doing what w.r.t. rich JavaScript applications? Is this like Cappuccino? How does this "make development as fast and as painless as possi…

Post by sirclueless » Thu, Aug 25, 2011, 9:39 AM UTC

nciagra wrote: post #15

bprater wrote: post #6

From the site: "It gives us great pleasure to finally announce the release of batman.js to the JavaScript community today. This release represents the first code dump of something we’ve been working hard on at Shopify for a long time, so we’re very excited to get it into your hands and see what you do with it." I got zero value out of this lead. When you launch a product like this, please tell us why we'd want to use…

Sure, I'll break it down: batman.js is a JavaScript framework for rich JavaScript applications. It's designed to make development as fast and as painless as possible for developers and designers while giving them lots of power. We designed everything around a number of primary goals such as convention over configuration, HTML-based views, and the principle of least surprise. This is something we're using at Shopify i…

Post by insin » Thu, Aug 25, 2011, 10:32 AM UTC

nciagra wrote: post #46

MatthewPhillips wrote: post #43

Earlier quoted context omitted.

Their framework is intended solely for coffeescript devs. Here's their example in javascript: (function() { var Shopify; var __hasProp = Object.prototype.hasOwnProperty, __extends = function(child, parent) { for (var key in parent) { if (__hasProp.call(parent, key)) child[key] = parent[key]; } function ctor() { this.constructor = child; } ctor.prototype = parent.prototype; child.prototype = new ctor; child.__super__…

To be fair, that's the compiled CoffeeScript. While it certainly is still fairly readable (even writable), the JavaScript you write by hand won't have the same "compiled feel".

    var Shopify = Batman.App.extend()
    Shopify.root('products#index')
    Shopify.resources('products')

    Shopify.Product = Batman.Model.extend()
    Shopify.Product.persist(Batman.RestStorage)

    // I'm never sure about how much I'm expected to mimic CoffeeScript code
    // when using libraries written in CoffeeScript and the source code is
    // written in a language I'm not practiced at reading - I've been bitten in
    // the past by CoffeeScript-only examples which *assume* you're transpiling
    // to JS in your head to insert the implicit return of the result of the
    // last expression.
    Shopify.ProductsController = Batman.Controller.extend({
      index: function() {
        return this.redirect({action: 'show', id: 1})
      }

    , show: function(params) {
        return this.product = Shopify.Product.find(params.id)
      }
    })

    var Shopify = Batman.App.extend({
      root: 'products#index'
    , resources: 'products'
    })

Post by jurre » Thu, Aug 25, 2011, 11:45 AM UTC

MatthewPhillips wrote: post #43

mcantelon wrote: post #13

Earlier quoted context omitted.

>It's an alternative syntax Right... "alternative"... so makes sense to not give examples entirely in it unless your framework is intended solely for Coffeescript users.

Their framework is intended solely for coffeescript devs. Here's their example in javascript: (function() { var Shopify; var __hasProp = Object.prototype.hasOwnProperty, __extends = function(child, parent) { for (var key in parent) { if (__hasProp.call(parent, key)) child[key] = parent[key]; } function ctor() { this.constructor = child; } ctor.prototype = parent.prototype; child.prototype = new ctor; child.__super__…