dmitry

# Put this content to ~/.irbrc file (no extension)

require "rubygems"

begin
  require "ap"
rescue LoadError => err
  puts "Cannot find awesome_print gem. Please run 'gem install awesome_print' to install it."
end

dmitry

class Ability
  include CanCan::Ability
  
  def initialize(user)
    user ||= User.new # guest user
    
    if user.role? :admin
      can :manage, :all
    else
      can :read, :all

dmitry

module FormtasticExtensions
  module Formtastic
    module TextileEditor
      
      def self.included(base)
        base.class_eval do
          @javascript_included = false
        end
      end

dmitry

React now supports the use of ES6 classes as an alternative to React.createClass().

React's concept of Mixins, however, doesn't have a corollary when using ES6 classes. This left the community without an established pattern for code that both handles cross-cutting concerns and requires access to Component Life Cycle Methods.

In this gist, @sebmarkbage proposed an alternative pattern to React mixins: decorate components with a wrapping "higher order" component that handles whatever lifecycle methods it needs to and then invokes the wrapped component in its render() method, passing through props.

While a viable solution, this has a few drawbacks:

1. There's no way for the child component to override functionality defined on the higher order component.

dmitry

import { Component } from "React";

export var Enhance = ComposedComponent => class extends Component {
  constructor() {
    this.state = { data: null };
  }
  componentDidMount() {
    this.setState({ data: 'Hello' });
  }
  render() {

dmitry

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout. This is also called reflow or layout thrashing, and is common performance bottleneck.

Element

Box metrics

• elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
• elem.clientLeft, elem.clientTop, elem.clientWidth, elem.clientHeight
• elem.getClientRects(), elem.getBoundingClientRect()

dmitry

  // Allows you to specify events on the data tied to the view in the same way
  // that you can specify dom events:
  //
  // dataEvents: {
  //   instanceName: {
  //     'change:name': 'mothed',
  //     delete: 'otherMethod'
  //    }, ...
  //  }
  registerDataEvents: function(unbind) {

dmitry

/** 
   Big thanks to Derick Bailey for his post here: 
   http://lostechies.com/derickbailey/2011/09/15/zombies-run-managing-page-transitions-in-backbone-apps/ 
*/
(function(Account) {
        
        /** LOTS OF MODEL, COLLECTION, AND VIEW CREATION GOING ON UP HERE, LEFT IT OUT FOR SIMPLICITY */

	/**
	*  Define Routing.

dmitry

:+1:
:-1:
:airplane:
:art:
:bear:
:beer:
:bike:
:bomb:
:book:
:bulb:

dmitry

namespace :routes do
  desc "Writes doc/routes.html. Requires Graphviz (dot)"
  task :visualizer => :environment do
    File.open(Rails.root.join('doc', 'routes.html'), 'wb') do |f|
      f.write Rails.application.routes.router.visualizer
    end
  end
end