You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
As modern web applications do more and more on the client-side (the fact itself that we now refer to them as “web applications†as opposed to “web sites†is quite telling), there has been rising interest in client-side frameworks. There are a lot of players in this field but for applications with lots of functionality and many moving parts, two of them stand out in particular: Angular.js and Ember
Today, we're excited to announce the final release of Ember.js 1.0. The first commit to the repository that would become Ember.js happened on April 30th, 2011, almost two and a half years ago. At the time, Backbone.js was rocketing to popularity. In response to large JavaScript frameworks like SproutCore, Cappuccino, and Dojo, which tried to abstract away HTML, most web developers began rejecting
In response to this blog post about why Angular.js rocks, I thought I’d write something similar about Ember.js. Ember.js is a MVC (Model – View – Controller) JavaScript framework which is maintained by the Ember Core Team (including Tom Dale, Yehuda Katz, and others). It helps developers create ambitious single-page web applications that don’t sacrifice what makes the web great: URI semantics, RES
Feb 07 2013 Hey everyone! I made a video today about Ember.js and accessibility. I had always been repeating what I’d heard about screen readers: they can’t work with JavaScript. Turns out that’s not exactly true. The video is the best way to show you: VoiceOver, Ember.js, and WAI-ARIA from Steve Klabnik on Vimeo. Here’s a rough transcript, if you don’t want to watch it: Hey everyone. I recently w
Deleted articles cannot be recovered. Draft of this article would be also deleted. Are you sure you want to delete this article? 今日ã¾ã§ Ember.js ã®ç´¹ä»‹ã‚’ã—ã¦ãã¾ã—ãŸã€‚ æ€ãˆã°Advent Calendarを書ã始ã‚ãŸ12/1ã®æ™‚点ã§ã¯ã€ç§è‡ªèº«ã€Ember.jsã«ã¤ã„ã¦ã¯ã»ã¨ã‚“ã©ä½•ã‚‚知らãªã„状態ã§ã‚¹ã‚¿ãƒ¼ãƒˆã—ã¾ã—ãŸã€‚ ã‚‚ã£ã¨ã‚‚knockout.jsã‚’æ¥å‹™ã«ä½¿ã£ã¦ã„ãŸã®ã§ã€ãƒ‡ãƒ¼ã‚¿ãƒã‚¤ãƒ³ãƒ‡ã‚£ãƒ³ã‚°æ©Ÿèƒ½ã®ä¾¿åˆ©ã•ã¯ç†è§£ã—ã¦ã„ã¾ã—ãŸã—ã€Ember.jsãŒè¨˜è¿°ã®æŸ”軟性ã®ãƒ¬ãƒ™ãƒ«ã§ã¯ä»–ã®ãƒ‡ãƒ¼ã‚¿ãƒã‚¤ãƒ³ãƒ‡ã‚£ãƒ³ã‚°ã‚ˆã‚Šæ´—ç·´ã•ã‚Œã¦ã„ã‚‹ã®ã§ã€ã‚³ãƒ³ã‚»ãƒ—トレベルã§ã¯é–“é•ã„ãªãã™ã°ã‚‰ã—ã„フレームワークã§ã‚ã‚‹ã€ã¨ã„ã†ã“ã¨ã¯ç¢ºä¿¡ã—ã¦ã„ã¾ã—ãŸã€‚ ãŸã ã€Router, ストレージã®åˆ©ç”¨æ–¹æ³•ã€æ‹¡å¼µæ–¹
Ember.js Docs 日本語訳 イントãƒãƒ€ã‚¯ã‚·ãƒ§ãƒ³ Ember.jsã¨ã¯ Ember.jsã¯å¤§è¦æ¨¡ã‚¦ã‚§ãƒ–アプリケーションã®æ§‹ç¯‰ã«æ¨™æº–çš„ãªã‚¢ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³æ§‹é€ ã‚’æä¾›ã—ã€ã‹ã¤ãƒœã‚¤ãƒ©ãƒ¼ãƒ—レートコードを排除ã—ãŸJavaScriptã®ãƒ•ãƒ¬ãƒ¼ãƒ ワーク。 ボイラープレートコードã®æŽ’除 å…¨ã¦ã®ã‚¦ã‚§ãƒ–アプリケーションã«ã¯ã€ä¾‹ãˆã°ã€ãƒ‡ãƒ¼ã‚¿ã‚’サーãƒã‹ã‚‰å–å¾—ã—ã€ã‚¹ã‚¯ãƒªãƒ¼ãƒ³ã«è¡¨ç¤ºã•ã›ã€ãƒ‡ãƒ¼ã‚¿ã«å¤‰æ›´ãŒã‚ã‚‹å ´åˆã«è¡¨ç¤ºã‚’アップデートã™ã‚‹ã€ãªã©ã€å…±é€šã®ã‚¿ã‚¹ã‚¯ãŒå˜åœ¨ã™ã‚‹ã€‚ ブラウザå´ãŒç”¨æ„ã—ãŸãƒ„ールã¯éžå¸¸ã«åŽŸå§‹çš„ãªãŸã‚ã€ã“れらタスクを行ã†ã®ã«åŒã˜ã‚³ãƒ¼ãƒ‰ã‚’何回も書ãã“ã¨ã«ãªã‚‹ã€‚Ember.jsã¯ãã®æ•°ç™¾å›žã‚‚書ã„ãŸã“ã¨ãŒã‚るよã†ãªåŒã˜ã‚³ãƒ¼ãƒ‰ã‚’書ãã‹ã‚ã‚Šã«ã‚¢ãƒ—リãã®ã‚‚ã®ã«é›†ä¸ã§ãるツールをæä¾›ã—ã¦ã„る。 ã„ãã¤ã‚‚ã®ã‚¢ãƒ—リケーションを作æˆã—ã¦ããŸçµŒé¨“ã‹ã‚‰ã€æ˜Žã‚‰ã‹ãªä½Žãƒ¬ãƒ™ãƒ«ã®ã‚¤ãƒ™ãƒ³ãƒˆãƒ‰ãƒªãƒ–ンã®æŠ½è±¡åŒ–ã¯ã‚‚ã¡ã‚ã‚“ã€ã‚¢ãƒ—リケーション全
Ember and Backbone are both promising JavaScript frameworks but have completely different philosophies. In this post, I'll compare the two, both from a practical and philosophical perspective. I'll defer to real world experience with Backbone and SproutCore (Ember's predecessor), as well as basic experiments with Ember (full disclosure: haven't built a large Ember app yet). I'll also supplement cl
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
処ç†ã‚’実行ä¸ã§ã™
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}