kj187

Day 1 - Friday, 28/03/14

• Opening - Laser Intro 1 Laster Intro 2
• Robert Lemke - Keynote
• Christian Müller - Neos 101
• Sebastian Kurfürst - A Head Start Into TypoScript 2.0
• Martin Helmich - Bringing the Elephant up to speed - Running TYPO3 Flow on HipHop VM
• Tim Numan/Jesper Paardekooper - How Flow helps us save the world
• Henrik Møller Rasmussen - Domain Event - the hidden gem of DDD
• Karsten Dambekalns - [Migrating from TYPO3

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

radmiraal

-
  name: 'Search paginate'
  uriPattern:    '{node}/{--typo3-typo3cr-viewhelpers-widget-paginateviewhelper.currentPage}'
  defaults:
    '@package':    'TYPO3.Neos'
    '@controller': 'Frontend\Node'
    '@format':     'html'
    '@action':     'show'
    '--typo3-typo3cr-viewhelpers-widget-paginateviewhelper':
      '@package': ''

dwightwatson

<?php

class TestCase extends Illuminate\Foundation\Testing\TestCase {

    /**
     * Creates the appliation.
     *
     * @return \Symfony\Component\HttpKernel\HttpKernelInterface
     */
    public function createApplication()

kristianmandrup

Converting libraries to Ember CLI addons

In this guide we will cover two main cases:

• Ember specific library
• vendor library

Ember library

The Ember library will assume that Ember has already ben loaded (higher in the loading order) and thus will assume it has access to the Ember API.

paulirish

console.log wrap resolving for your wrapped console logs

I've heard this before:

What I really get frustrated by is that I cannot wrap console.* and preserve line numbers

We enabled this in Chrome DevTools via blackboxing a bit ago.

If you blackbox the script file the contains the console log wrapper, the script location shown in the console will be corrected to the original source file and line number. Click, and the full source is looking longingly into your eyes.

Version1_Not_Working.php

<?php
    namespace Typovision\Simpleblog\Service;

    class SignalService implements \TYPO3\CMS\Core\SingletonInterface {
        public function handleInsertEvent(\TYPO3\CMS\Extbase\DomainObject\DomainObjectInterface $object, $signalInformation) {
            if($object instanceof \Typovision\Simpleblog\Domain\Model\Blog) {
                $logfile    = "C:\\xampp\\htdocs\\t3Test\\testLog.txt";
                \TYPO3\CMS\Extbase\Utility\GeneralUtility::writeFile($logfile, "test");
            }
        }

alexanderschnitzler

An open letter to the Neos development team

Dear members of the development team, CU a few days ago I commented the announcement, that Neos and Flow get rid of "TYPO3" as part of their names, as follows:

Removing "TYPO3" from Neos and Flow makes it easier to quietly abandon these products. \o/

Additionally to this tweet I had a small twitter conversation resulting in this tweet:

chinshr

#!groovy
# Best of Jenkinsfile
# `Jenkinsfile` is a groovy script DSL for defining CI/CD workflows for Jenkins
node {
}

javier-lopez

#!/bin/sh
#postinst

_suspend_dpkg_process()
{
    rm -rf /var/lib/dpkg/updates.suspended/
    mv /var/lib/dpkg/lock     /var/lib/dpkg/lock.suspended
    mv /var/lib/dpkg/updates/ /var/lib/dpkg/updates.suspended
    mkdir /var/lib/dpkg/updates/
    mv /var/cache/apt/archives/lock /var/cache/apt/archives/lock.suspended