| class Api::RegistrationsController < Api::BaseController | |
| respond_to :json | |
| def create | |
| user = User.new(params[:user]) | |
| if user.save | |
| render json: user.as_json(auth_token: user.authentication_token, email: user.email), status: :created | |
| return | |
| else |
| // Use Gists to store code you would like to remember later on | |
| console.log(window); // log the "window" object to the console |
Most of these guidelines are to match Apple's documentation and community-accepted best practices. Some are derived some personal preference. This document aims to set a standard way of doing things so everyone can do things the same way. If there is something you are not particularly fond of, it is encouraged to do it anyway to be consistent with everyone else.
This document is mainly targeted toward iOS development, but definitely applies to Mac as well.
NSString *foo = @"bar";
Some CoffeeScript (verbosely commented for clarity)
# Override Rails handling of confirmation
$.rails.allowAction = (element) ->
# The message is something like "Are you sure?"
message = element.data('confirm')
| #!/usr/bin/env ruby | |
| require "openssl" | |
| require 'digest/sha2' | |
| require 'base64' | |
| # We use the AES 256 bit cipher-block chaining symetric encryption | |
| alg = "AES-256-CBC" | |
| # We want a 256 bit key symetric key based on some passphrase | |
| digest = Digest::SHA256.new |
| # create the template | |
| template = PageOfflineTemplate.new | |
| template.quote = quote | |
| template.pages = quote.build_pages | |
| # Here I render a template with layout to a string then a PDF | |
| pdf = PDFKit.new template.render_to_string(:template=>"quotes/review.html.haml") | |
| class HelloWorldController < AbstractController::Base | |
| include AbstractController::Rendering | |
| include AbstractController::Layouts | |
| include AbstractController::Helpers | |
| include AbstractController::Translation | |
| include AbstractController::AssetPaths | |
| include ActionController::UrlWriter | |
| # Uncomment if you want to use helpers defined in ApplicationHelper in your views | |
| # helper ApplicationHelper |
| <html> | |
| <head> | |
| <script src="http://code.jquery.com/jquery-1.11.1.min.js"></script> | |
| <script type="text/javascript" src="https://www.google.com/jsapi"></script> | |
| <style> | |
| #piechart { | |
| top: 0; | |
| left: 0; | |
| width:100%; | |
| height:100%; |
Rails flash messages with AJAX requests
This is just a jotting of notes on how to embed Faye into a single Rails process. Makes it nice to do simple real time things without the need for a separate Faye server/process.
Also uses Faye Redis to work across load balanced Rails apps.
You also need to copy the compiled javascript into vendor/assets/javascripts and include into application.js manifest.
Ignore the numbers in the file names... just used to add order to the Gist.
This uses the faye/faye Github repo at edc5b42f6560d31eae61caf00f6765a90e1818d1 since I wanted to use with the Puma rack server and that is only available in the master branch (until Faye 1.0)