nicolasalarconrapela nicolasalarconrapela

SVG sprite generator, by Sérgio Lopes

Requirements

Python
Inkscape (on command line path)
ImageMagick

Katana Code's Git Strategy

Introduction

The purpose of this document is to define the strategy which all Katana Code employees and subcontractors must adhere to when working on Katana Code projects.

The aim is to develop a uniform, coherent and effective solution. This document is not written in stone and can be updated as and when better approaches are discovered.

Topic Branches

Git práctico

Conceptos clave

Antes de empezar a soltar comandos como un bellaco, hay que explicar los conceptos clave que se necesitan conocer para trabajar con Git.

Comenzaremos con los diferentes estadios en los que puede encontrarse nuestro código (nuestros cambios sobre el contenido de los ficheros, en realidad).

Workspace: Es el estado real de nuestros ficheros. Tal y como los vemos en nuestro editor.
Stage: Aquí se encuentran los cambios sobre nuestros ficheros que se incluirán en el próximo commit. Cuando hacemos un git add, un git rm o un git mv, estamos introduciendo cambios en el stage, indicándole a Git que en el próximo commit esos cambios irán incluidos.

Directory structure for JavaScript/Node Projects

While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.

Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.

Directories

lib/ is intended for code that can run as-is
src/ is intended for code that needs to be manipulated before it can be used

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

Cómo colaborar en un proyecto en GitHub

Fork del repositorio
Clonar el repositorio
Actualizar la rama master
Crear una rama
Hacer los cambios
Hacer un Pull Request

	<!DOCTYPE html>
	<html>
	<head>
	<title>Box Shadow</title>

	<style>
	.box {
	height: 150px;
	width: 300px;
	margin: 20px;

	#!/bin/bash

	# current Git branch
	branch=$(git symbolic-ref HEAD \| sed -e 's,./\(.\),\1,')

	# v1.0.0, v1.5.2, etc.
	versionLabel=v$1

	# establish branch and tag name variables
	devBranch=develop

	# Customize BASH PS1 prompt to show current GIT repository and branch.
	# by Mike Stewart - http://MediaDoneRight.com

	# SETUP CONSTANTS
	# Bunch-o-predefined colors. Makes reading code easier than escape sequences.
	# I don't remember where I found this. o_O

	# Reset
	Color_Off="\[\033[0m\]" # Text Reset

	#!/bin/bash

	function showHelp {
	version=0.0.1
	versionDate="2014-07-07"

	echo "$0 - tic/toc timer pair

	Usage: $0 [id] Stores initial time (w/optional id marker)
	$0 [-u\|--unique] Creates and returns unique id