| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> | |
| <title>SoundCloud OAuth 2 User Agent Authentication Flow Demo</title> | |
| <script type="text/javascript" charset="utf-8" src="javascript/jquery-1.4.2.js"></script> | |
| <script type="text/javascript" charset="utf-8"> | |
| $(function () { | |
| var extractToken = function(hash) { |
| <?php | |
| namespace Acme\DemoBundle\Listener; | |
| use Acme\DemoBundle\Security\Authorization\Voter; | |
| use Symfony\Component\HttpFoundation\Response; | |
| use Symfony\Component\HttpKernel\HttpKernelInterface; | |
| use Symfony\Component\HttpKernel\Log\LoggerInterface; | |
| use Symfony\Component\Security\Core\SecurityContextInterface; | |
| use Symfony\Component\Security\Core\Authentication\Token\TokenInterface; |
This totally happened, y'all can stop +1ing this now. GitHub Blog post. Direct link to settings where you can set this.
#Per-organization / per-repo email overrides - A feature suggestion
Here the concepts "organization" and "user" are interchangeable, I'm talking about an entity that owns a repo, whether it is jQuery or John Resig. I'll stick to using organization as it best represents my original use-case.
##TL;DR
| var parser = document.createElement('a'); | |
| parser.href = "http://example.com:3000/pathname/?search=test#hash"; | |
| parser.protocol; // => "http:" | |
| parser.hostname; // => "example.com" | |
| parser.port; // => "3000" | |
| parser.pathname; // => "/pathname/" | |
| parser.search; // => "?search=test" | |
| parser.hash; // => "#hash" | |
| parser.host; // => "example.com:3000" |
| fos_js_routing: | |
| routes_to_expose: | |
| - "^api_.*" # expose all routes with a name starting with api_ |
| { | |
| "require": { | |
| "monolog/monolog": "1.1.*" | |
| } | |
| } |
| <?php | |
| /** | |
| * Created by JetBrains PhpStorm. | |
| * User: Marco Pivetta | |
| * Date: 16.08.12 | |
| * Time: 11:05 | |
| * To change this template use File | Settings | File Templates. | |
| */ | |
| class CriteriaTest extends \PHPUnit_Framework_TestCase | |
| { |
| // Source: https://groups.google.com/forum/#!topic/angular/hVrkvaHGOfc | |
| // jsFiddle: http://jsfiddle.net/pkozlowski_opensource/PxdSP/14/ | |
| // author: Pawel Kozlowski | |
| var myApp = angular.module('myApp', []); | |
| //service style, probably the simplest one | |
| myApp.service('helloWorldFromService', function() { | |
| this.sayHello = function() { | |
| return "Hello, World!" |
The reflow appens as many times as there are frames per seconds. It recalculate all positions that change in order to diplay them. Basically, when you scroll you execute a function where you move things between two reflows. But there are functions that triggers reflows such as jQuery offset, scroll... So there are two things to take care about when you dynamically change objects in javascript to avoid too many reflows:
