janmarek

{gridito usersGrid}
	{* top toolbar *}
	{gridito.toolbar.button addUser text => "Nový uživatel", icon => "plusthick", plink => "add"}

	{* columns *}
	{gridito.column username text => "Uživatelské jméno", sortable => true}
	{gridito.column name text => "Jméno", sortable => true}
	{gridito.column mail text => "E-mail", sortable => true}
	{gridito.column allowed text => "Aktivní", sortable => true}
	{gridito.column created text => "Datum založení", sortable => true, dateTimeFormat => "j.n.Y"}

isaacs

echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
. ~/.bashrc
mkdir ~/local
mkdir ~/node-latest-install
cd ~/node-latest-install
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1
./configure --prefix=~/local
make install # ok, fine, this step probably takes more than 30 seconds...
curl https://www.npmjs.org/install.sh | sh

daveray

; A REPL-based, annotated Seesaw tutorial
; Please visit https://github.com/daveray/seesaw for more info
;
; This is a very basic intro to Seesaw, a Clojure UI toolkit. It covers
; Seesaw's basic features and philosophy, but only scratches the surface
; of what's available. It only assumes knowledge of Clojure. No Swing or
; Java experience is needed.
;
; This material was first presented in a talk at @CraftsmanGuild in
; Ann Arbor, MI.

gudbergur

This is a fork of Bootstrap Typeahead that adds minimal but powerful extensions.

For example, process typeahead list asynchronously and return objects

  # This example does an AJAX lookup and is in CoffeeScript
  $('.typeahead').typeahead(
    # source can be a function
    source: (typeahead, query) ->
 # this function receives the typeahead object and the query string

fprochazka

{block #content}

{define #control-grouped-mailing}
    {input $name}
{/define}

{define #control-submit}
    {input $name, class => 'btn btn-primary'}
{/define}

juzna

Simple backups with Git

Git calls itself "stupid content tracker", which means that the core just stores any data you put in and allows you to get it back. On top of that, there's all the fancy stuff like branching, diffs, remote repos etc, but that's not important for us today. We just want to track content, and the more stupidier (i.e. simple) way, the better - it'll be simpler to do any crazy stuff we imagine later on.

Motivation

I wanted to do backups of couple of terabytes of data, consisting of quite small files (< 10MB) which usually don't change. I wanted to have incremental backups (not to transfer all data) and I wanted to see history and be able to get into any version.

So why not to use git for it?

Mikulas

common:
	parameters:
		adminer_editor:
			role: moderator

		database:
			host: localhost
			dbname: yourDbName
			user: yourDbUser
			password: yourDbOass

vvondra

<?php

namespace Vondra;

class GitBranchPanel implements \Nette\Diagnostics\IBarPanel
{

	public function getPanel()
	{
		return '';

fprochazka

<?php

/**
 * @author Filip Procházka <[email protected]>
 */
abstract class BasePresenter extends Nette\Application\UI\Presenter
{

	/**
	 * @var \Img\ImagePipe

kaja47

<?php

// advanced bit-twiddling

abstract class AbstractIntArray {
  protected $length;
  protected $data;
  protected $typeSize;

  function __construct($length) {