Ian Channing ianchanning

## gist:188166
# RSpec
require 'spec/expectations'

# Webrat
require 'webrat'

require 'test/unit/assertions'
World(Test::Unit::Assertions)

Webrat.configure do |config|

## mdc-web-closure-compatibility.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              1 star
            
          
                traviskaufman
                / mdc-web-closure-compatibility.md
            
            
              Created
              February 22, 2017 16:30
            
              
                MDC-Web Closure Compatibility
              
          
    material-components/material-components-web#134
Closure Compiler Support
Google Closure Compiler support is required in order to support the Google projects and properties which are built around this toolchain. Concretely, MDC-Web must be able to compile with ADVANCED_OPTIMIZATIONS enabled, and produce no errors or warnings. There are implications for internal support as well, but that is outside the scope of this issue.
Goals


Full compilation of MDC-Web using ADVANCED_OPTIMIZATIONS
Test infrastructure to verify both compilation, as well as runtime correctness, e.g. our closurized code behaves correctly


## n
#!/bin/sh
# Flora Note by LeaskH.com

list() {
    ls $note_path
}

edit() {
    "$editor" $note_path
}

## index.html
<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
    <title>React + D3</title>
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <script src="http://cdnjs.cloudflare.com/ajax/libs/underscore.js/1.5.2/underscore.js"></script>
    <script src="http://cdnjs.cloudflare.com/ajax/libs/react/0.8.0/react.js"></script>
    <script src="http://cdnjs.cloudflare.com/ajax/libs/react/0.8.0/JSXTransformer.js"></script>
    <script src="http://cdnjs.cloudflare.com/ajax/libs/d3/3.3.13/d3.js"></script>

## gist:a9c9a5989dc383ed73b4

      
              1 file
            
          
              1 fork
            
          
              5 comments
            
          
              3 stars
            
          
                brettcannon
                / gist:a9c9a5989dc383ed73b4
            
            
              Last active
              September 19, 2017 10:27
            
              
                Initial email about Python development process and proposed improvements
              
          
    This was posted as an email to python-dev.
History lesson

Since I signed up for the python-dev mailing list way back in June 2002, there seems to be a cycle where we as a group come to a realization that our current software development process has not kept up with modern practices and could stand for an update. For me this was first shown when we moved from SourceForge to our own infrastructure, then again when we moved from Subversion to Mercurial (I led both of these initiatives, so it's somewhat a tradition/curse I find myself in this position yet again). And so we again find ourselves at the point of realizing that we are not keeping up with current practices and thus need to evaluate how we can improve our situation.
Where we are now

Now it should be realized that we have to sets of users of our development process: contributors and core developers (the latter whom can play both roles). If you take a rough outline of our cur

  
## meteor-windows-vagrant-tutorial.md

      
              2 files
            
          
              0 forks
            
          
              3 comments
            
          
              11 stars
            
          
                gabrieljenik
                / meteor-windows-vagrant-tutorial.md
            
            
              Last active
              December 16, 2017 08:57
                — forked from ahoereth/meteor-windows-vagrant-tutorial.md
            
          
    Tutorial: Meteor on Windows using Vagrant

Requirements

Before doing anything else, install those:

VirtualBox: https://www.virtualbox.org/wiki/Downloads
Vagrant: https://www.vagrantup.com/downloads.html
git: http://git-scm.com/download/win


## gist:57736
<!--//

RubyRobot
Copyright (c) 2008 Fabio Zendhi Nagao <http://zend.lojcomm.com.br/>

Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or sell

## CakePhp Rest Route with api prefi steps.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              3 stars
            
          
                mdemblani
                / CakePhp Rest Route with api prefi steps.md
            
            
              Last active
              May 28, 2018 20:59
            
              
                CakePhp Rest Route with api prefix. A small hack in cakephp v2.X Lib to support restful routes with api prefix
              
          
    I had my api ready and faced the problem of converting them into rest routes with api and version prefixs using the cakephp Router::mapResources function that was provided by default by CakePhp,
My api was intially,

http://www.xyz.com/controller/

supporting basic rest routes and I wanted it to be in the form

http://www.xyz.com/api/version_number/controller/action

that would support basic rest routes with prefix including api and version number.
To achieve this there are two ways:

Create routes using Router::connect for each function and list them down manually in your routes.php file.


## README.md

      
              2 files
            
          
              4 forks
            
          
              2 comments
            
          
              26 stars
            
          
                johnpbloch
                / README.md
            
            
              Created
              August 23, 2012 13:55
            
              
                A bash script to make .pot files for WordPress plugins
              
          
    Installation

To install, you need to have the WordPress i18n library on your computer. Check it out using SVN:
sudo svn co http://i18n.svn.wordpress.org/tools/trunk/ /usr/lib/wpi18n

You don't have to put the library in /usr/lib/wpi18n, but if you don't put it there, make sure to set the $WP_I18N_LIB environment variable in your .bashrc file (with no trailing slash):
export WP_I18N_LIB="/path/to/i18n/lib"

  
## win10colors.cmd
@echo off
cls
echo [101;93m STYLES [0m
echo ^<ESC^>[0m [0mReset[0m
echo ^<ESC^>[1m [1mBold[0m
echo ^<ESC^>[4m [4mUnderline[0m
echo ^<ESC^>[7m [7mInverse[0m
echo.
echo [101;93m NORMAL FOREGROUND COLORS [0m
echo ^<ESC^>[30m [30mBlack[0m (black)
	# RSpec
	require 'spec/expectations'

	# Webrat
	require 'webrat'

	require 'test/unit/assertions'
	World(Test::Unit::Assertions)

	Webrat.configure do \|config\|
	#!/bin/sh
	# Flora Note by LeaskH.com

	list() {
	ls $note_path
	}

	edit() {
	"$editor" $note_path
	}
	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="utf-8">
	<title>React + D3</title>
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<script src="http://cdnjs.cloudflare.com/ajax/libs/underscore.js/1.5.2/underscore.js"></script>
	<script src="http://cdnjs.cloudflare.com/ajax/libs/react/0.8.0/react.js"></script>
	<script src="http://cdnjs.cloudflare.com/ajax/libs/react/0.8.0/JSXTransformer.js"></script>
	<script src="http://cdnjs.cloudflare.com/ajax/libs/d3/3.3.13/d3.js"></script>
	<!--//

	RubyRobot
	Copyright (c) 2008 Fabio Zendhi Nagao <http://zend.lojcomm.com.br/>

	Permission is hereby granted, free of charge, to any person
	obtaining a copy of this software and associated documentation
	files (the "Software"), to deal in the Software without
	restriction, including without limitation the rights to use,
	copy, modify, merge, publish, distribute, sublicense, and/or sell
	@echo off
	cls
	echo [101;93m STYLES [0m
	echo ^<ESC^>[0m [0mReset[0m
	echo ^<ESC^>[1m [1mBold[0m
	echo ^<ESC^>[4m [4mUnderline[0m
	echo ^<ESC^>[7m [7mInverse[0m
	echo.
	echo [101;93m NORMAL FOREGROUND COLORS [0m
	echo ^<ESC^>[30m [30mBlack[0m (black)