kevinGodell

#!/bin/bash
# convert, encrypt, decrypt, probe

echo "Hello ffmpeg mp4 encryption!"

echo -e "\n---------- convert wav to mp4 ----------\n"

ffmpeg -y -i long_input_44100.wav long_input_44100.mp4

echo -e "\n---------- encrypt mp4 ----------\n"

rmkane

#MooTools Timer Example

Below is a code snippet that uses the Timer and TimerTask classes.

##Script

function print(id, value) {
    document.getElementById(id).innerHTML = value;
}

fakedarren

I feel the need to have a little rant about MooTools and ES7 and the whole 'Array.contains' hoo-hah.

When MooTools came out in 2006, the most popular framework was Prototype. As the name suggests, it extended prototypes, as did MooTools. People still referred to making websites with JavaScript as 'DHTML', there was no trim method on strings, there wasn't even a forEach method on arrays. JavaScript was a crippled language. IE6 ruled the waves.

MooTools, Prototype, Dojo, Base2 - they made the language usable, even fun, to work with. By using an incredible feature of JavaScript, prototypical inheritance, we were able to add features to the language that made it palatable.

Be it simple methods like number.toInt, string.trim, array.forEach, or familiar programming constructs such as Class, MooTools and its ilk took JavaScript from something impossible to work with to something that you could properly use to build awesome sites, and even apps - Microsoft, IE and desktop ruled everything, and the concept of a 'we

GCheung55

{
    "paths": {
        "mootools": "path/to/mootools"
    },
    "shim": {
        "mootools/Types/Array": ["mootools/Core/Core"],
        "mootools/Types/Function": ["mootools/Core/Core"],
        "mootools/Types/Object": ["mootools/Core/Core"],
        "mootools/Types/Number": ["mootools/Core/Core"],
        "mootools/Types/String": ["mootools/Core/Core"],

termi

void function() {//closure

var global = this
  , _initKeyboardEvent_type = (function( e ) {
		try {
			e.initKeyboardEvent(
				"keyup" // in DOMString typeArg
				, false // in boolean canBubbleArg
				, false // in boolean cancelableArg
				, global // in views::AbstractView viewArg

WebReflection

/**
 * so here the thing ... you go in your github page
 * as example I go here: https://github.com/WebReflection
 * you open your console
 * you copy and paste this shit
 * then you write and execute in the console
 * write("Hi There!");
 * NOTE: Pixel Font from a 2006 project of mine :-) http://devpro.it/pixelfont/
 */
function write(text, color, start) {

DimitarChristoff

saw this artcile quoting 10 reasons why jquery is better than mootools. source: http://www.jquery4u.com/articles/jquery-mootools/

jQuery has better mobile support than Mootools – the latest release of jQuery Mobile Alpha 3 has been a breakthrough in how easy it can be to get your website “mobile efficient”. Mootools has mobile support including touch events but it’s not as widely available as jQuery options. (#1 was Previously jQuery vs Mootools filesizes).

not true. see http://moobilejs.com/

jQuery is less confusing than Mootools! – It has less native extensions (including element) – jQuery has about a dozen for Array, Object, and String and Mootools has about six dozen for Array, Object, String, Function, and Number.

how is less power and methods a good thing? the reason why mootools has more native methods is because it also shims browsers that lack ES5 functionality for all the natives that it extends. if anything, this goes against jquery.

arian

/*
---
name: Slick.Finder
description: The new, superfast css selector engine.
provides: Slick.Finder
requires: Slick.Parser
...
*/

(function(){