Description: Setup GitHub Pages "gh-pages" branch and "master" branch as subfolders of a parent project folder ("grandmaster").
Author: Chris Jacob @_chrisjacob
Tutorial (Gist): https://gist.github.com/833223
module Jekyll | |
class ArchivePage | |
include Convertible | |
attr_accessor :site, :pager, :name, :ext, :basename, :dir, :data, :content, :output | |
# Initialize new ArchivePage | |
# +site+ is the Site | |
# +month+ is the month | |
# +posts+ is the list of posts for the month |
Description: Setup GitHub Pages "gh-pages" branch and "master" branch as subfolders of a parent project folder ("grandmaster").
Author: Chris Jacob @_chrisjacob
Tutorial (Gist): https://gist.github.com/833223
# Note that while this file is in our config folder, it is | |
# symlinked to our site folders, so paths are relative from there | |
# Require gems and Compass plugins | |
# require 'rgbapng' | |
# require 'compass-fancybox-plugin' | |
require 'compass-growl' | |
# General | |
output_style = :expanded |
My approach to fix the iOS bug is documented here:
https://github.com/sergiolopes/ios-zoom-bug-fix
Here I present one experiment with a pure CSS solution, no JS required. It uses width=device-width
normally (no device-height
hacking) and scales down the page on landscape.
Works fine on all iOS versions.
There's only one problem: on old iOS versions (prior to 4.3.5), the page will get a big empty space at bottom, below the content, when on landscape. Recent iOS versions don't show this behavior.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> | |
<html xmlns="http://www.w3.org/1999/xhtml"> | |
<head> | |
<meta http-equiv="content-type" content="text/html; charset=utf-8"/> | |
<script type="text/javascript" src="jquery-1.7.1.min.js"></script> | |
<script type="text/javascript"> | |
$(document).ready(function () { | |
$.getJSON('estados_cidades.json', function (data) { |
Variáveis globais quase sempre são uma má ideia, mas como fugir delas em javascript ? É simples: não dá, o que podemos fazer é minimizar o número de variáveis globais.
Entendendo o problema:
O uso de variáveis globais é principal forma de trocar informações entre módulos javascript, então como usa-las sem diminuir a qualidade do código ?
Algumas maneiras de como resolver isso:
# Apache configuration file | |
# httpd.apache.org/docs/2.2/mod/quickreference.html | |
# Note .htaccess files are an overhead, this logic should be in your Apache config if possible | |
# httpd.apache.org/docs/2.2/howto/htaccess.html | |
# Techniques in here adapted from all over, including: | |
# Kroc Camen: camendesign.com/.htaccess | |
# perishablepress.com/press/2006/01/10/stupid-htaccess-tricks/ | |
# Sample .htaccess file of CMS MODx: modxcms.com |
/** | |
* Filter table rows as you type | |
* | |
* == How to use == | |
* Just add the script to the page and, on the input element, | |
* add the data-filter attibute with the selector to the table. | |
* <input type="search" data-filter="#tableID"> | |
* | |
* == Acknowledgements == | |
* This was inspired by jresig's liveUpdate plugin used on jQuery's |
(function() { | |
var script, | |
scripts = document.getElementsByTagName('script')[0]; | |
function load(url) { | |
script = document.createElement('script'); | |
script.async = true; | |
script.src = url; | |
scripts.parentNode.insertBefore(script, scripts); |