Build engaged audiences through publishing by curation.
Sign up with Facebook
Sign up with Twitter
I don't have a Facebook or a Twitter account
Start a free trial of Scoop.it Business
We all recognize that we should be writing semantic code. Maybe, you’re even using or correctly, and feel pretty good about yourself. But, are you also considering the implied contract that exists when you code?
Get the idea of what interfaces can mean in Web Development.
Are you sure you want to delete this scoop?
Guys dont't cry. It's going to be a great sunny trip to Peru for a month. For your daily update consider:
There are a lot of front end development tools that will allow you to build an EmberJS application using CoffeeScript, Sass and the other tools that we like to use on projects. After evaluating them we settled on using a basic Rails application instead; primarily for simplicity. The project had a short timeline and we didn't want to have to worry about another tool that we were not familiar with. In the future I would love to try building an Ember UI using a front end tool such as Tapas with Ember but we didn't have any complaints with using Rails in this case and it made our stack a bit simpler to use.
LigerMobile is a lightweight open source framework that helps you develop hybrid apps quickly and easily. If you are looking for a tool to build a hybrid app, create a prototype, or just need a stepping stone to full native app development — this is a great way to begin.
In this article I’ll introduce you to QUnit, a testing framework that will help you spot errors and bugs in your code.
At first, this process may seem complex and tedious. Creating a test for all of your functions does take some time, but it will save you hours of debugging at the end of the project cycle.
Not only that, but you’ll save yourself the blushes we all get when a client emails us about a bug they’ve found.
As a further benefit, you’ll find that this workflow also benefits cross-browser testing, and using this approach you can test in several browsers straight out of the box.
Knockout 3.0 introduces a number of improvements in the binding pipeline, including a number of extension points for pre-processing binding values. For those just starting out and even those more experienced with MVVM, debugging bindings is still a key part of the development process. In this post I’ll run through some well known techniques for debugging bindings and touch on some changes that will impact debugging.
Single-Page Applications (SPAs) are Rich, Responsive Web apps that load a single HTML page and dynamically update that page as the user interacts with the app.
This code sample gives the demo application for creating Single Page Application using Hot Towel SPA Template (Knockout, Durandal, Breeze).
This application will be useful for understanding the basics of Single Page Application in some extend. If you follow and create the application your own, it will give great experience on SPA.
This code sample describes step by step creation of My Contact project using MVC 4 - Hot Towel Single Page Application Template.
I am explaining the step by step creation of My Contact project using MVC 4 Hot Towel SPA and I have written inline comment in the source code for better understanding the code. In this web page I am concentrating on steps for creating this application.
One of the great features of DozerJS is that it is extremely simple to work with, even for those new to NodeJS development.
In this post I'm going to walk through creating a basic Todo-List application to demonstrate basic usage and I/O.
1. Install the NPM2. Start a New Project3. Generate Modules4. Build A Model5. Inspect the API6. Setup The Controller7. The Public UI
First and foremost, this book is the print edition of my self-published ebook, but with actual copy editing, tech editing, and professional graphics. The topics covered are the same and are mostly covered in the same way (the No Starch version has additional clarifications in some places). As a bonus, there is a No Starch ebook version.
If you know me, you know it’s easy to get me talking about Ember.js. A year ago, I was deeply skeptical of developing client-side applications. Now, after spending a year shipping production applications in Ember, I believe that client-side apps represent the same generational leap that database-backed apps with Rails offered circa 2006.
Despite the title of this article, I can’t actually predict the future, but I can bet on it. And Charles and I are betting The Frontside’s future on the fact that Ember provides a foundation for creating amazing, next-generation user experiences for the web.
Server-side MVC frameworks rely on the classic Apple philosophy of optimizing for the 80% use case. These frameworks excel at taking a database, exposing CRUD (Create, Read, Update, Destroy) actions via HTTP, and building form-based UIs to work with these records. CRUD-oriented frameworks make it easy to build applications like blogs and contact management software.
What server-side MVC frameworks are not particularly well-suited to are user-driven, stateful UIs like you’d see in desktop apps like Word, Excel, or iTunes.
This post describes a prototype that uses Polymer webcomponents in D3.js.
Appending a single element, like a ‘rect’ to a D3 selection is straightforward. But when you want to append a more complex, nested structure to a selection, it would be nice if you could append a renderer or template. And I would find it even more comfortable if you could specify this in a structured language like xml/html. Furthermore, I would like to specify the behaviour of this renderer within the renderer itself.
I first encountered this desire when I tried to use D3 for visualizing Isotype charts. D3 maps data points to dom elements in a one-to-one relation, while Isotype maps data points to dom elements in a one-to-many relation. You can solve this by converting data points to arrays, but that feels a bit hackish.
I decided to use webcomponents.
I wrote the async library back when Node first removed Promises from core (yes, that really was the case). Back then, I preferred to do with plain callbacks what was usually done by including third-party Promise, Future or Continuable libraries instead.
Well, here is my proposal, for your consideration and feedback: Highland, a high-level streams library
Implementing single-page web applications that work on all browsers remains a challenge. For the basic task of uploading files, you still need some sort of polyfill or library that adds support for older browsers (read IE 8 and 9, which are still in wide use).
In this tutorial I’m going to describe how to integrate one such library, called mOxie, with one client-side MVC framework, called Ember.js.
Reusable web components in glorious isolation
Polymer lets you create your own <HTML>tags in complete isolation from what the rest of the web page is doing. The result is rock-solid, reusable code that just works™. Learn how to get the most out of this exciting new platform.
As web application complexity spirals out of control, next generation browser features that cut through the craziness remain out of reach.What if you could use next generation features today?
Today it’s possible for us to author in ES6 and transpile our sources down to ES5 at build-time, regardless of whether we’re using Grunt, Gulp or Broccoli. With projects like Ember and Angular looking to ES6 as part of their roadmaps too (Ember App Kit already supports ES6 modules!), now is a great time to learn how ES6 can be used in practice.
In this guide, we’ll re-write the well known TodoMVC application (implemented withBackbone.js) using ECMAScript 6 language semantics. The implementation is made possible using Google’s Traceur compiler and ES6-Module-Loader.
This post will show you how to setup Visual Studio 2013 to work with Github
A stamp is a factory function which has public properties that specify a delegate prototype, default instance state, and a function that sets up encapsulation for object instances. Stamps utilize three different types of inheritance to create the new object:
Delegate prototype – Delegation / Differential Inheritance
Instance state – Cloning / Concatenative Inheritance / Mixins
Encapsulation – Functional Inheritance
Stampit is a library written to demonstrate how we might use sugar to simplify prototypal OO. It exports a single function.
It demonstrates prototypal inheritance with factories.
Broccoli is a new build tool released recently by Jo Liss. Matt and I took the project for a spin last week, and we were impressed by the benefits of using Broccoli. Our task was simple. We wanted to achieve a bootstrapped Ember.js application, similar to what Stefan’s AppKit provides.
To list a few of the features:
A jQuery plugin that enables you to add gesture events such as 'pinch', 'rotate', 'swipe', 'tap' and 'orientationchange' just like native jQuery events. Includes event substitution: a "tapone" event can be triggered by "clicking", a "swipe" by performing a swipe-ish mousegesture.
Brings 27 new events to your bag.
With math-based art, creativity is still an important part of the equation. Of course no one can become a Bathsheba Grossman or Paul Nylander overnight, but if you're interested in learning some of the techniques that make math-based art possible (and don't have $1000 to spend on a copy of Mathematica) then Shapeways has the tool for you.
This will be a short post about two built in Ember.js route handlers – ApplicationRoute and IndexRoute.
I’ve been building a simple application which has an /entries route. Whenever someone visits my application via root path / I wanted them to be transitioned (think redirected) to the /entries route. To do this, we’ll be using the beforeModel hook in the Route object.
The Route handler is the perfect place for that because it’s responsible for an application state for a given url. Since I wanted to transition from / to /entries I quickly addedthis.transitionTo(“entries”) code inside of an ApplicationRoute’s beforeModel hook.
The beautiful thing about Sails is the ability to get alot of the boilerplate code generated quickly for you. This code gives you the basic nuts and bolts you would have to code by hand if you were not using a web framework with node. Sails is based on a MVC pattern heavily influenced by the Ruby on Rails framework, which is why when you define a model you get the basic CRUD functions out of the gate without writing any more code. The thing that Sails does well (never written any rails) is the ability to talk to any database that has an adapter written for you without having to change any of your code inside the app, change where the database is at along with any creds and you're off and running.
Sails has the concept of Policies, these are something that are evaluated prior to running any code inside a controller. Me coming from a .net C# background would litter decorators on my actions inside my controllers to lock down who has access to what methods. It would look a little like this...