kyo_agoããã«èªããã¦ãCoffeeScriptã«ã¤ãã¦1ç« æ¸ãã¾ããã JavaScriptã¨ã³ã¸ãã¢é¤æèªæ¬ï¼»Webã¢ããªéçºã®å®çªæ§æBackbone.jsï¼CoffeeScriptï¼Gruntã1åã§ç¿å¾ï¼ï¼½ï¼æ¸ç±æ¡å ï½æè¡è©è«ç¤¾ ä»ã®ç« ã®ç´¹ä»ã¯ä»ã®èè ããã«ä»»ããã¨ãã¦ãèªåã®æ¸ããç« ã«ã¤ãã¦å°ãç´¹ä»ã JavaScriptã¨ã³ã¸ãã¢é¤æèªæ¬ãæ¸ãã¾ãã - watilde's blog å®è·µçCoffeeScript CoffeeScriptã®è¨èªä»æ§ã«ã¤ãã¦ãåå¿è ã§ã誤解ããªããããè¨èªããã¢ã§ãæ°ããå¦ã³ãããããã«æ¸ããã¤ããã§ãã ã¨ãã«ãªãã¸ã§ã¯ããé åã®ãã¿ã¼ã³ããããCoffeeScriptç¹æã®ãªãã¸ã§ã¯ãæåã®ã¤ãã£ãªã ãå¤§è¦æ¨¡éçºæã®ãã£ã¬ã¯ããªæ§æã«ã¤ãã¦å®ä¾ã交ãã¦æ¸ãã¾ããã ãã¨ãã°ãããªã³ã¼ã module.exports = class
Love Rails? You'll love batman.js. If you know Rails, then you'll be up and running with batman.js in minutes. batman.js was built with Rails development in mind, allowing you to save time and use less code. Serious Scalability. batman.js makes it easy. Building the next [insert trendy website/app]? batman.js was created with scalability in mind and currently powers Shopify. In other words, your p
kybernetikos / Dynamic Source Maps There are many pages about source maps online (e.g. this one), but almost none of them go into detail on how to decode VLQs (the smoosh of characters at the bottom of the source map where all the important data is stored), so lots of thanks to Peter van der Zee who wrote it up in enough detail that someone who hadn't heard of VLQs before (me) could write a decode
Hello, and welcome back to the rebooted #WorkflowThu series. Today we're going to see how ridiculously easy it is to debug CoffeeScript files with source maps. Watch the video (07:14) or read the article below. Tools mentioned in this video: Uglify.js v2 by Mihai Bazon (free) LiveReload by yours truly ($10) â alternatives include CodeKit by Brian Jones ($25), Fire.app by Handlino ($14), and others
In today's modern workflow, the code that we author in our development environments is considerably different from the production code, after running it through compilation, minification, concatenation, or various other optimization processes. This is where source maps come into play, by pointing out the exact mapping in our production code to the original authored code. In this introductory tutor
å½¦æ ¹å·¥å ´ã§50年以ä¸å¹ãããæè¡åã¨ãã¦ãã¦ããããããã¹ã¦çµéãã¦ä½ãä¸ããããã¡ã³ãºã·ã§ã¼ãã¼ãLAMDASHããä½å人ãã®æè¡è ããã¶ã¤ãã¼ã®ç ç©¶ãéçºã«ãã£ã¦ç£¨ãä¸ãããããç©¶æ¥µã®æ§è½ã¨æ´ç·´ããããã©ã«ã ããã£ã¨ããããããã£ã¨æ·±åãã¸ã LAMDASHã®é²åã¯ã¨ã©ã¾ããã¨ãç¥ããªãã
07 Feb 2012 Iâm the primary developer on the HTML/front-end components (but not the Flash) of the Camry Effect website. Itâs both the largest amount of client-side code Iâve written for a project, and the first project Iâve done with CoffeeScript. It was also a fairly high-pressure project for many different reasons. This post will describe the project, and detail my experiences developing it in C
This concise book shows JavaScript developers how to build superb web applications with CoffeeScript, the remarkable language thatâs gaining considerable interest. Through example code, this guide demonstrates how CoffeeScript abstracts JavaScript, providing syntactical sugar and preventing many common errors. Youâll learn CoffeeScriptâs syntax and idioms step by step, from basic variables and fun
A couple of weeks ago, I announced a CoffeeScript/JavaScript assertion library called ExpectThat. In this post, I'll provide a more real-world example of how ExpectThat can be used. For this example, I'll be using the jQuery plugin and tests from one of Josh Bush's posts entitled "Testing jQuery Plugins with Node.js and Jasmine". The jQuery plugin The code that follows is a re-write (in CoffeeScri
IcedCoffeeScript is a superset of CoffeeScript. The iced interpreter is a drop-in replacement for the standard coffee interpreter; it will interpret almost all existing CoffeeScript programs. IcedCoffeeScript (ICS) adds two new keywords: await and defer. These additions simply and powerfully streamline asynchronous control flow, both on the server and on the browser. Say goodbye to callback pyrami
A recent project has us using spine.js as well as a few other JavaScript libraries. Though spine.js comes with its own routing, it conflicts with pjax. The solution was to roll our own. The requirements are simple, we should be able to give it a set of routes and their corresponding callbacks and we should be able to process the browsers url upon request. The CoffeeScript for that looks like this:
次ã®ã¤ãã³ãäºå® ã¿ã¤ãã«ï¼ 第ï¼åCoffee女åä¼ æ¥æï¼ 2011/10/29-15:00 ãã 2011/10/29-17:00 ã¾ã§ å å®¹ï¼ è¨å¿µãã¹ã第ï¼åã§ãã ããããã©ããªãµãã«æ´»åãã¦ããããã³ã¼ãã¼ã飲ã¿ãªããã話ãããã¨æãã¾ããCoffeeScriptã«ã¾ã¤ãããã®ãã³ã¼ãã¼ã«é¢ä¿ãããã®ããªãã§ããæã¡ãã ããï¼ Coffeespotï¼ èèè¶ åå ç»é²ï¼ http://kokucheese.com/event/index/19683/ Coming soon! ä»ã¾ã§ã®ã¤ãã³ããè¦ã
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}