- Platform: Browser
- https://github.com/organizations/{ORGNAME}/dashboard/issues
- Platform: Browser
# Initial setup | |
git clone -o framework -b develop https://github.com/laravel/laravel.git project-name | |
cd project-name | |
git checkout --orphan master | |
git commit -m "Initial commit" | |
# Pulling changes | |
git fetch framework | |
git merge --squash -m "Upgrade Laravel" framework/develop | |
# Fix merge conflicts if any and commit |
/* | |
WildText CommonJS module for Appcelerator Titanium | |
Create dynamic gradient filled text in your iOS Applications using this simple module. | |
@params : text - String. The text for your label | |
font - Font. Specify the font attributes for the label (defaults to standard size, weight and family), | |
backgroundGradient - BackgroundGradient. Specify your backgroundGradient object (defaults to White to Black linear gradient), | |
Top - Integer. Top property for your label, | |
Left - Integer. Left Property for your Label, |
This is just a small post in response to [this tweet][tweet] by Julien Pauli (who by the way is the release manager for PHP 5.5). In the tweet he claims that objects use more memory than arrays in PHP. Even though it can be like that, it's not true in most cases. (Note: This only applies to PHP 5.4 or newer.)
The reason why it's easy to assume that objects are larger than arrays is because objects can be seen as an array of properties and a bit of additional information (like the class it belongs to). And as array + additional info > array
it obviously follows that objects are larger. The thing is that in most cases PHP can optimize the array
part of it away. So how does that work?
The key here is that objects usually have a predefined set of keys, whereas arrays don't:
/** | |
* Handle Item Swipe | |
* @param {Object} _event | |
*/ | |
$.handleItemSwipe = function(_event) { | |
var row = _event.source; | |
var id = row.id; | |
var controls = Alloy.createController("rowControls"); | |
row.add(controls.wrapper); |
<snippet> | |
<content><![CDATA[ | |
class ${1:TABLENAME}TableSeeder extends Seeder { | |
public function run() | |
{ | |
\$${1} = [ | |
${2} | |
]; |
I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.
From Require.js - Why AMD:
The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"
I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.
<?php | |
class DogsController extends BaseController { | |
protected $db; | |
// Let the db-layer be injected. Don't worry... | |
// Laravel will automatically inject the dependencies for you. | |
function __construct(DogInterface $db) { | |
$this->db = $db; | |
} |
function doClick(e) { | |
alert($.label.text); | |
} | |
function showmenu(e){ | |
$.main.animate({left:200,duration:100}); | |
} | |
function hidemenu(e){ | |
$.main.animate({left:0,duration:100}); |