Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
The latest Ember Data has been totally overhauled to follow JSON API. The plan here is to put them to work. We’ll build a CLI-powered Ember 2.0-ready app step by step, hooked to a Rails 5 API using JSON API. Bleeding edge anyone? We will create a simple bookstore. 
No comment yet.
Sign up to comment
Scoop.it!
Since those dark times, a few tools have cropped up and improved the landscape. As I mentioned before, I have recently been working on a project that I wanted to have a stand-alone front-end app for (inb4 single page apps don't work). I wanted to avoid the messes I've encountered with JavaScript-heavy Rails apps and keep Rails as API-centered as possible. Once I had a functioning back-end, I knocked together a rudimentary front-end with React using Bower to manage dependencies and Jekyll to compile it all down to a static page.
Scoop.it!
mber.js and Rails code kit to get your Software as a Service application up and running in no time at all. Uses Ember.js and Ember Data for the frontend application, and Ruby on Rails for the backend API
Scoop.it!
In this comparison, Rails expert Fernando Villalobos breaks down the difference between AngularJS and Ember.js when it comes to choosing a JS framework for Rails applications.
Scoop.it!
Contents: * The front end of the pool
Scoop.it!
Ember can be used as a front end to any server-side stack, but today I’m here to discuss how to avoid some common pitfalls when using it with my personal favorite web framework: Ruby on Rails. Though Ember and Rails make a great pair, it’s easy to get a little lost in the early days as you find your way around. Well, I did, anyway. This is your chance to learn from my mistakes so you can get to making your own mistakes a little more quickly. Shall we begin?
Scoop.it!
John looks at AngularJS and the MEAN stack as an alternative to Ruby on Rails as a productive stack for building typical web applications. To dive into MEAN, what better way for a Rails fan to get up to speed than by following the path of the famous demo, and creating my own blog application with MEAN.js. A more up-to-date version of the Rails blog exercise, without the “Uoooops,” is the Rails getting started guide. Our journey here will mirror this guide and summarize my comparison with Rails.
Scoop.it!
From
medium
By splitting the development of the frontend and the Rails backend we could distribute the work over two development teams and keep the application as a whole very extensible. In my opinion this is the best approach when you split your frontend and backend however not everyone shares that opinion. In this blogpost I will cover why we believe that testing the apps separately and thus mocking the API requests is the way to go.
Scoop.it!
From
medium
Today we’re going to assemble the first pieces of this app by creating a Rails server, an Ember.js App and some basic Bootstrap styling. We want to be able to expose all of our stats from various internal and third party services with a consistent API so this server will primarily handle authentication and data transformation. This server could just as easily be written in Node.js or any language/framework, but for now we’ll stick with Rails.
Jan Hesse's insight:
Scoop.it!
If you render a React component with the same data, it will always return the same result. It makes absolutely no difference whether you do that rendering on the client or the server. That brings us to the official front end buzzword of 2014: Isomorphic JavaScript. The Holy Grail. The united UI layer. Serve up real HTML on first page load, then kick off a client side JS app. All without duplicating a single line of UI code. React makes this really easy if your back end is Node.js:
Scoop.it!
We built our API and our JavaScript application as two completely separate applications. We had one repo that held a very basic Rails application with Ember on top and another repo that held the API built in Rails. 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. For Ember in our Rails app we used the ember-rails gem. It provides a basic folder structure for your Ember application inside the app/assets/javascripts directory. The directory structure is similar to a Rails application as you can see below...
Scoop.it!
Unfortunately, building a prototype is always the easy part. Doing the whole port has had a bunch of problems I did not take forsee. I put in a proposal outlining the goals and how to reach those goals on December 4'th, 2013. As of writing this, it's February 1'st, 2014, and we have still not managed to remove all of our Rails views. Thankfully, we made this a progressive transition, which meant we could roll out changes progressively. The basic idea is that we'd convert one page at a time, and push it out to our customers. We weren't exactly perfect on this, and ended up taking a few weeks before we rolled anything out, but as of right now, we're at the point where we can move pages from Rails to AngularJS very easily. The ultimate goal is to get Rails to just handle our API, and the angular app can handle the console experience; it also means removing all of our assets from Rails. I'm going to share how our development workflow looks, some of the issues we encountered, and how we solved them.
Scoop.it!
Ruby on Rails MVC Is Not the Same as Ember.js MVC One of the most confusing parts for people coming from Rails (or any other backend web application framework) it’s that what Ember.js calls MVC is very different to what other frameworks call MVC. The following are the steps mention by Yehuda and the components in charge of each in both Ruby on Rails and Ember.js...
|
Scoop.it!
Integrate React.js with Ruby on Rails to build web apps Summarizing, the application will behave as follows:
Scoop.it!
I’ve been less than enamored with Rails lately. It’s not that I don’t love the framework, I’ve just been spending more and more time wanting to build more front-end heavy applications using an MVVM like EmberJS and Rails is just way to much framework for an API-only application. Problem is I still love Ruby and ActiveRecord and I’m honestly not a fan of all the callbacks in Node/Express. Enter Sinatra, or more specifically activerecord-sinatra. My goal is to convert my Password manager application Passweb from a Rails app to a Sinatra/EmberJS app. This is a fairly simple project with only a few models so it shouldn’t be too hard to replicate in your project.
Scoop.it!
Get this party started. Let's build an API and CMS to expose our data layer to the world. Ember.js has a gang now. It's got a lot of characters and it could be quite daunting for someone without any knowledge of how the different pieces fit and play along. Some call this Ember's "learning cliff". Ember's "learning cliff" is tough, but it instills a bit of what makes server-side frameworks like Rails so nice...
Scoop.it!
KnockoutJS and MVVM (Comes with a sample application) - It's a beginner's guide that discusses about Knockout in particular and MVVM pattern in general. Knockout is a very cool piece of technology that makes your view code less cluttered. This ppt reaches every (not all :-) detail of Knockout. By following this ppt you'll surely be in position to get started with Knockout on your own projects.
Scoop.it!
I wrote this tutorial because I had a pretty tough time getting Rails and Angular to talk to each other as an SPA. The best resource I could find out there was Ari Lerner’s Riding Rails with AngularJS. I did find that book very helpful and I thought it was really well-done, but it seems to be a little bit out-of-date by now and I couldn’t just plug in its code and have everything work. I had to do a lot of extra Googling and head-scratching to get all the way there. This tutorial is meant to be a supplement to Ari’s book, not a replacement for it. I definitely recommend buying the book because it really is very helpful.
Scoop.it!
In this comparison, Rails expert Fernando Villalobos breaks down the difference between AngularJS and Ember.js when it comes to choosing a JS framework for Rails applications. Contents: 1. Introduction
Scoop.it!
Before continuing, I will like to share a very simple application I have created as the result of what we are going to achieve after finishing this post. It consists of:
Jan Hesse's insight:
Scoop.it!
Imagine a web app. You browse it and you decide you want to register yourself. Then you put your credentials on a login form. The web page will send you a token via JSON. What can you do with that token? In that concrete app, you can access your user profile, your messages or even add new friends. The same fact applies: You can access your profile but not others profiles (Imagining they are private) and you can’t certainly remove friends from your partner account :P Now that we have an idea of how JWT works, let’s see it from a more technique perspective. A JWToken is self-contained, so when we create one, it will have all the necessary pieces needed inside of it. What are those pieces? A token is divided in 3 parts:
Scoop.it!
This series will take us through building and structuring an application with an Ember front-end built with ember-cli and a Ruby on Rails backend. We'll discuss project structure, testing, and deployment to Heroku. During the course of this series I am going to re-build the Boston Ember website.
Scoop.it!
One of the most confusing parts for people coming from Rails (or any other backend web application framework) it’s that what Ember.js calls MVC is very different to what other frameworks call MVC. To understand what MVC is in both frameworks I recommend watching Yehuda Katz presentation: A tale of two MVC’s. Instead of talking about MVC, Yehuda proposes an unified model for GUI programming which is composed by a series of steps and then explains how different frameworks handle each step. The following are the steps mention by Yehuda and the components in charge of each in both Ruby on Rails and Ember.js...
Scoop.it!
With the increasing prevalence of JavaScript and JSON you can pretty much find a lot of framework choices out there that covers both points even if you are a front-end developer primarily knowing only JavaScript. As for me, my roots are in Java server-side development. I do write JS for front-end development but I am not as comfortable to structure and write JS to develop server-side code. If you're like me, then what's the solution? What're we making? In honor of TodoMVC we are going to build a Todo app which enables us to post a list of things to do. Just simple enough to give a taste of what these frameworks we're choosing are capable of.
Scoop.it!
Getting an Ember project started is really easy thanks to EAK, it already puts the basic structure of our apps so we can focus on what we like the most, developing. 1. Keep two separate projects, a Rails app (probably using rails-api) and an EAK app.
|
