以前書いた記事の反省を元にMarionetteに移行した。 思った以上に快適！ 大規模になったらMarionette.js使えとか書いているのは嘘で、普通にBackbone使うときは、初めから使うべき。 Backboneで一番恐ろしいのは、各現場/各開発者毎に異なるオレオレ実装。オレオレ実装作るコストに加え、使う人の思わぬバグや学習コストやスイッチングコスト等諸々考えると、特別な理由がない限りMarionetteみたいな既存のframework使うべき。 あんど。データバインディングを提供してくれる、stickitと一緒に使うと、より一層効果的。 めっちゃ、ソースコードの量が減って、ソースの意図が明快になった。悩みも少ない。工数も勿論減る。 ここから、幾つか思った事を、サッカー見ながらお酒飲みながら、ダラダラ書く。※ちなみに、日本vsオランダ戦見てる。 railsアプリでのjs周辺の作りの
これ読んでたらr7kamura君にJSのMVCどうするの的な話きかれてたのを思い出したので、自分がBackboneを使う時のパターンをr7kamura君の記事をベースに書きなおしてみた。 > サバクラ両方で動く JavaScript の大規模開発を行うために ― Gist https://gist.github.com/1362110 > client-side javascript - ✘╹◡╹✘ http://r7kamura.hatenablog.com/entry/2012/10/18/023629 以下の様なコードを書いた。かなり冗長だが、複雑なアプリだとこれぐらいの冗長性は必要になる。 (なお概念を伝えるための解説用コードなのでそのままじゃ動かない) Backbone.Model # 名前空間の初期化 App = {} App.View = {} App.Model = {}
Backbone.js users usebind andbindAll methods provide byunderscore.js a lot. In this blog Iam going to discuss why these methods are needed and how it all works. It all starts with applyFunction bindAll internally uses bind . And bind internally uses apply.So it is important to understand what apply does. var func = function beautiful() { alert(this + " is beautiful");};func();If I execute above co
February 28, 2012 This article will be appearing in my forthcoming book on Backbone.js and continues the section on unit testing. We previously looked at Jasmine and will now look at QUnit and SinonJS. QUnit is a powerful JavaScript test suite written by jQuery team member Jörn Zaefferer and used by many large open-source projects (such as jQuery and Backbone.js) to test their code. It’s both capa
Post.has().many('comments', { collection: Comments, inverse: 'post' }); Comment.has().one('post', { model: Post, inverse: 'comments' }); var post = Post.create({ id: 1, comments: [{id: 2}, {id: 3}, {id: 4}] }); post.comments().length; // 3 var comment = Comment.create({id: 5, post_id: 1}); post.comments().length; // 4 comment.post() === post; // true :D Source The source for Supermodel is hosted o
After more work with Backbone on projects at Sheepdog, we are starting to develop a solid foundation that will allow us to easily develop, test, and maintain our Backbone.js applications. Having these properties in our JS / CoffeeScript is very important, as we're striving toward better test coverage from server to client in order to best deliver the highest quality product to our clients. The app
References, Routing, And The Event Aggregator: Coordinating Views In Backbone.js 19 July, 2011. It was a Tuesday. I recently found myself needing to facilitate communication between two backbone views. The first view is a medication – one that is currently being taken by a particular patient. The second view is the add/edit view that allows the patient to either add new medications or edit existin
December 20, 2012 Backbone: Dealing with stateful applications (part 1) For the last ~20 years the web has relied on the stateless HTTP protocol. We are all used to working with the request/response model but as the web evolves, new features are demanded by its users such as realtime and desktop-like experience. The request/response model The request/response model is stateless because it relies o
Single Page Web Apps with Backbone.js About a month ago, we decided that we needed to give the front-end of sendhub.com a face-lift. The site looked a bit dated, and it just didn’t feel as snappy as we wanted it to. All pages were rendered almost entirely on the server, and only a couple of places used Ajax to pull in data asynchronously. In parallel to this, we were also in the process of releasi
Backbone.Paginator - New Pagination Components For Backbone.js March 30, 2012 Pagination is a ubiquitous problem we often find ourselves needing to solve on the web. Perhaps most predominantly when working with back-end APIs and JavaScript-heavy clients which consume them. On this topic, today I'd like to announcethe pre-release of a new set of pagination components for Backbone.js, which should h
Backbone.js Patterns - a tutorial/presentationBackbone.js Patterns Prologue Let me be clear: there are virtually endless ways you can build a JavaScript application, between modules, loaders, sync and async, reliance on advanced features and whatnot. I often feel like I'm just scratching the surface, no matter how many I build, nor how many I read the source of. These are a set of patterns that I
Hey guys. Today we’re going to take a look at how you can build a single-page application (SPA) supporting graceful degradation using some of jQuery’s Best friends; DocumentCloud’s Backbone.js, Underscore.js, LAB.js and jQuery templating to name but a few.Alex Sexton has been giving a great presentation highlighting these tools in few recent conferences and I thought it would be useful to write up
Available free for open-source reading below or for purchase via the O'Reilly store. Pull requests and comments always welcome. Prelude Not so long ago, “data-rich web application” was an oxymoron. Today, these applications are everywhere and you need to know how to build them. Traditionally, web applications left the heavy-lifting of data to servers that pushed HTML to the browser in complete pag
Backbone Patterns Building apps with Backbone.js Here, I try to document the good practices that our team has learned along the way building Backbone applications. This document assumes that you already have some knowledge of Backbone.js, jQuery, and of course, JavaScript itself. Table of contents Model patterns Bootstrapping data View patterns Inline templates JST templates Partials Animation buf
Quick intro, the hype and awesomeness that is Node Node.js is pretty freakin' awesome, yes. But it's also been hyped up more than an Apple gadget. As pointed out by Eric Florenzano on his blog a LOT of the original excitement of server-side JS was due to the ability to share code between client and server. However, instead, the first thing everybody did is start porting all the existing tools and
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
