NamelessCoder

<?xml version="1.0" encoding="UTF-8"?>
<scheme name="Solarized Dark" version="124" parent_scheme="Default">
  <option name="LINE_SPACING" value="1.1" />
  <font>
    <option name="EDITOR_FONT_NAME" value="SourceCodePro-Regular" />
    <option name="EDITOR_FONT_SIZE" value="13" />
  </font>
  <font>
    <option name="EDITOR_FONT_NAME" value="Monaco" />
    <option name="EDITOR_FONT_SIZE" value="13" />

NamelessCoder

/**
 * ## FooBar ViewHelper
 *
 * Blabla
 *
 * ### Argument: foo
 *
 * See: https://raw.github.com/bla/bla.md
 *
 * ### Argument: barFromParent

NamelessCoder

<?php
/***************************************************************
 *  Copyright notice
 *
 *  (c) 2011 Claus Due <claus@wildside.dk>, Wildside A/S
 *  All rights reserved
 *
 *  This script is part of the TYPO3 project. The TYPO3 project is
 *  free software; you can redistribute it and/or modify
 *  it under the terms of the GNU General Public License as published by

NamelessCoder

<?php

/**
 * Content Element Definition Provider
 * 
 * Contains methods to either remove/change or add
 * content definitions to the new content wizard
 * and content type selectors.
 * 
 * Same instance is used for removing and adding

NamelessCoder

<?php

$test = new ArrayIterator(array(1, 2, 3));
$exec = [];

foreach ($test as $l1) {
        $exec[] = 'outer ' . $l1;
        foreach ($test as $l2) {
                $exec[] = 'inner' . $l2;
        }

NamelessCoder

#!/usr/bin/env bash

# phase one: core install

# Pro tip: edit the script and use this repository instead to try out the
# codename "Awesome Ocelot" project - which should be even faster than the
# bare 6.2 core: https://github.com/NamelessCoder/TYPO3.CMS.git
# Live demo of "Awesome Ocelot" is at http://staging.namelesscoder.net

git clone https://github.com/TYPO3/TYPO3.CMS.git --depth 1

NamelessCoder

My vision for TYPO3 content/page integrations

Estimated 15 minute read

Continuing from my vision for Fluid I'd like to describe another vision related to it. Where the first article is mainly about what we could do with the Fluid template engine outside of TYPO3, this article focuses on what we can do with it in TYPO3. It assumes the previous vision was realised.

The vision can be summarised as follows:

We should have a way to drop-in replace and add content templates, instead of requiring massive amounts of boilerplate configuration/code. And we should have a method for managing nested content which is provided by the core itself.

NamelessCoder

Vision: Grid as TCA type for TYPO3

Synopsis

This little gist is an attempt to describe my vision for a nested content / grid feature for TYPO3. It contains a description of the vision I have and relates this vision to the current blueprint and WIP which are available at https://wiki.typo3.org/Blueprints/StructuredContentContainers and https://review.typo3.org/#/c/41936/.

NamelessCoder

<?php

/*
 * Demonstrates how to configure `namelesscoder/typo3-cms-multilevel-cache` for
 * added L1 (runtime) and L2 (memcached) caches on existing database-backed caches.
 *
 * Tip: if your site changes frequently, consider assigning a low expiration time
 * on the "default_memcached" cache configuration.
 */

NamelessCoder

The following are examples of new syntax capabilities that will/may become possible if switching Fluid away from regular expression parsing, to a lexer yielding a stream of tokens that can then be parsed to become a Fluid "syntax tree".

The lexer is a research project, in progress, but nearing completion. I plan to combine it with a "streaming node parser" which only processes the tokens it must, as opposed to processing everything like the current Fluid parser does.

Some of these already work - most of them are being researched