pmkhoa

require 'rubygems'
require 'middleman/rack'
 
protected_middleman = Rack::Auth::Basic.new(Middleman.server) do |username, password|
  [username, password] == ['theuser', 'thepassword']
end
 
run protected_middleman

pmkhoa

#encoding: UTF-8

require 'rubygems'
require 'sinatra'
require 'erb'
require 'pp'

class Sinatra::Request
    def pjax?
        env['HTTP_X_PJAX'] || self['_pjax']

pmkhoa

/**
 * This code should be added to functions.php of your theme
 **/
add_filter('woocommerce_get_catalog_ordering_args', 'custom_woocommerce_get_catalog_ordering_args');

function custom_woocommerce_get_catalog_ordering_args( $args ) {
  if (isset($_GET['orderby'])) {
    switch ($_GET['orderby']) :
    case 'date_asc' :
      $args['orderby'] = 'date';

pmkhoa

How to make faster scroll effects?

• Avoid too many reflows (the browser to recalculate everything)
• Use advanced CSS3 for graphic card rendering
• Precalculate sizes and positions

Beware of reflows

The reflow appens as many times as there are frames per seconds. It recalculate all positions that change in order to diplay them. Basically, when you scroll you execute a function where you move things between two reflows. But there are functions that triggers reflows such as jQuery offset, scroll... So there are two things to take care about when you dynamically change objects in javascript to avoid too many reflows:

pmkhoa

# for golang
# mkdir $HOME/go
# mkdir -p $GOPATH/src/github.com/user
export GOPATH=$HOME/go
export PATH=$PATH:$GOPATH/bin

pmkhoa

Warden::Manager.serialize_into_session{|user| user.id }
Warden::Manager.serialize_from_session{|id| User.get(id) }
 
Warden::Manager.before_failure do |env,opts|
  # Sinatra is very sensitive to the request method
  # since authentication could fail on any type of method, we need
  # to set it for the failure app so it is routed to the correct block
  env['REQUEST_METHOD'] = "POST"
end
 

pmkhoa

This post is also on my blog, since Gist doesn't support @ notifications.

---

Components are taking center stage in Ember 2.0. Here are some things you can do today to make the transition as smooth as possible:

• Use Ember CLI
• In general, replace views + controllers with components
• Only use controllers at the top-level for receiving data from the route, and use Ember.Controller instead of Ember.ArrayController or Ember.ObjectController
• Fetch data in your route, and set it as normal properties on your top-level controller. Export an Ember.Controller, otherwise a proxy will be generated. You can use Ember.RSVP.hash to simulate setting normal props on your controller.

pmkhoa

$coupon_code = 'UNIQUECODE'; // Code
$amount = '10'; // Amount
$discount_type = 'fixed_cart'; // Type: fixed_cart, percent, fixed_product, percent_product
					
$coupon = array(
	'post_title' => $coupon_code,
	'post_content' => '',
	'post_status' => 'publish',
	'post_author' => 1,
	'post_type'		=> 'shop_coupon'

pmkhoa

Server scripts

This is the source for the scripts discussed in https://robots.thoughtbot.com/improving-user-experience-with-shell-scripts

Both scripts are in the bin/ directory of the repo that contains all the markdown documents for blog posts. Users run bin/server and everything is automatically set up for them to view a local preview of the blog. bin/server-setup is a dependency of bin/server and is never run directly by users.

Maitre-d is the name of the "blog engine" discussed in the article.

pmkhoa

import { test, moduleForComponent } from 'ember-qunit';

moduleForComponent('gravatar-image', 'GravatarImageComponent', {
});

test('it renders with size and e-mail', function() {
  var component = this.subject();

  Ember.run(function(){
    component.set('size', 400);