=====
I made a book, its one page.
| scr_meta=<><![CDATA[ | |
| // ==UserScript== | |
| // @name @troynt's Twitter Script | |
| // @namespace http://twitter.com/troynt | |
| // @description Nested Replies, RT button, Custom Search Tabs, YouTube Embed, TwitPic Embed, URL Expansion, Hash Tag Search Links | |
| // @version 9.9 | |
| // @include http://twitter.com* | |
| // @include http://www.twitter.com* | |
| // @include https://twitter.com* | |
| // @include https://www.twitter.com* |
=====
I made a book, its one page.
| # Title: MP3 tag for Jekyll | |
| # Authors: Devin Weaver, Daniel Roos (youtube changes) | |
| # Description: Allows mp3 tag to include mp3 files embedded into the post. | |
| # It uses the player 'audio.js' from http://kolber.github.com/audiojs/ | |
| # | |
| # Install the plugin according to the manuel of the author by adding the necessary lines to the head-template | |
| # and adding the files into the right directories. | |
| # | |
| # Please read my [blog post about it][2]. | |
| # |
| --- | |
| layout: post | |
| title: "Episode 3: ExpressionEngine StackExchange" | |
| date: 2012-12-20 10:47 | |
| comments: true | |
| filename: some-file-name-without-extension | |
| length: 52409154 | |
| summary: ExpressionEngine Pro Anna Brown and Testing Hero Chris Hartjes join Ben Edmunds and Phil Sturgeon to discuss the recent rumblings in the ExpressionEngine community and the new EE StackExchange site. We talk about Inversion of Control (IoC), what it is, why its useful and how it's done. | |
| --- |
| # Ignore docs files | |
| styles/.sass-cache | |
| styles/.sass-cache/* | |
| # Not working? | |
| # Try: http://stackoverflow.com/questions/11451535/gitignore-not-working | |
| # Try: http://stackoverflow.com/questions/1139762/gitignore-file-not-ignoring |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
If you were learning graph algorithms, which approach would you prefer:
Imagine you have to take public transit from your home to your office. How do you figure out the fastest route? Use graph algorithms! OR
We can choose between two standard ways to represent a graph G = (V, E): as a collection of adjacency lists or as an adjacency matrix. Either way applies to both directed and undirected graphs.
I prefer the first way: lead with lots of examples, and clear writing. The second way is an excerpt from "Introduction to Algorithms"...that's how they start their section on graph algorithms.
| brew update | |
| brew link yasm | |
| brew link x264 | |
| brew link lame | |
| brew link xvid | |
| brew install ffmpeg | |
| ffmpeg wiki: | |
| https://trac.ffmpeg.org/wiki/Encode/MP3 |
I've come to a point where I had to swap django's user model with a custom one, at a point when I already had users, and already had apps depending on the model. Therefore this guide is trying to provide the support that is not found in the django docs.
Django warns that this should only be done basically at the start of a project, so that the initial migration of an app includes the creation of the custom user model.
It took a while to do, and I ran into problems created by the already existing relations between other models and auth.User.
There were good and not so good things regarding my project state, that influenced the difficulty of the job.
id field, that's just a usual default django id