phproberto

<?php
/**
 * @package     Joomla.Site
 * @subpackage  Layout
 *
 * @copyright   Copyright (C) 2005 - 2015 Open Source Matters, Inc. All rights reserved.
 * @license     GNU General Public License version 2 or later; see LICENSE.txt
 */

defined('_JEXEC') or die;

fredgrott

// in your android.applicationVariants.all { variant ->
// or in your android.libraryVariants.all { variant ->
// code block put this:
if (variant.productFlavors[0] == null){
                variant.outputs[0].outputFile = new File(variant.outputs[0].outputFile.parent,
                        project.ext.ourProjectName + "_"
                                + variant.buildType.name + "_"
                                + android.defaultConfig.versionCode + "_"
                                + android.defaultConfig.versionName + ".apk")
            }else{

Integralist

The three design patterns (Adapter, Facade and Bridge) all produce the result of a clean public API. The difference between the patterns are usually due to a subtle context shift (and in some cases, a behavioural requirement).

Adapter

The primary function of an Adapter is to produce a unified interface for a number of underlying and unrelated objects.

You will notice this pattern being utilised in many applications. For example, ActiveRecord (the popular Ruby ORM; object-relational mapping) creates a unified interface as part of its API but the code underneath the interface is able to communicate with many different types of databases. Allowing the consumer of the API to not have to worry about specific database implementation details.

The principle structure of this pattern is:

eguneys

'use strict';

define(['phaser'], function(Phaser) {
    function Gesture(game) {
        this.game = game;

        this.swipeDispatched = false;
        this.holdDispatched = false;

        this.isTouching = false;

sanderpotjer

<?php
/**
 * @package	Article Form override for Joomla 3
 * @copyright 	Copyright (c) 2014 Sander Potjer - www.perfectwebteam.nl
 * @license 	GNU General Public License version 3 or later
 */

defined('_JEXEC') or die;

JHtml::_('behavior.keepalive');

stefanhoth

android {
  
    // .. set up build flavors etc here
    
    //instead of "app-release.apk" this method will rewrite the name to
    // "MyCoolCompany-MyGreatProduct-v<defaultConfig.versionName>-RELEASE.apk which is much better suited for archiving and overall handling
    // To restore the default behavior just delete the whole block below
    applicationVariants.all { variant ->

        def apk = variant.outputFile;

markgoodyear

/*!
 * gulp
 * $ npm install gulp-ruby-sass gulp-autoprefixer gulp-cssnano gulp-jshint gulp-concat gulp-uglify gulp-imagemin gulp-notify gulp-rename gulp-livereload gulp-cache del --save-dev
 */

// Load plugins
var gulp = require('gulp'),
    sass = require('gulp-ruby-sass'),
    autoprefixer = require('gulp-autoprefixer'),
    cssnano = require('gulp-cssnano'),

shakalaca

buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:0.5.6'
    }
}

task wrapper(type: Wrapper) {

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

pboos

configurations {
    apt
}

dependencies {
    compile 'com.squareup.dagger:dagger:1.1.0'
    apt 'com.squareup.dagger:dagger-compiler:1.1.0'
}

android.applicationVariants.all { variant ->