juriansluiman

<?php

namespace MyEmailThingy;

class Module
{
    public function onBootstrap($e)
    {
        $app = $e->getApplication();
        $em  = $app->getEventManager();

juriansluiman

<?php                                                                        
                                                                             
include 'vendor/autoload.php';

$pheanstalk = new Pheanstalk_Pheanstalk('127.0.0.1');
$pheanstalk->useTube('default');

$n     = 1000000;
$start = microtime(true);

juriansluiman

'slm_queue' => [
  'worker' => [
    'max_runs' => 100,
  ],

  'queues' => [
    'default' => [
      'deleted_lifetime' => -1
    ],
  ],

juriansluiman

<?php

class DbResolver implements ResolverInterface
{
    protected $adapter;

    public function __construct(AuthAdapter $adapter)
    {
        $this->adapter = $adapter;
    }

juriansluiman

<?php

namespace EasterEgg;

use DateTime;

class Module
{
    public function onBootstrap(MvcEvent $e)
    {

juriansluiman

<?php

namespace Foo\Controller;

use Foo\Repository\BarInterface as Repository;
use Foo\Form\BarInterface       as Form;
use Foo\Service\BarInterface    as Service;
use Foo\Options\ModuleOptions;

use Zend\Mvc\Controller\AbstractActionController;

juriansluiman

<?php

// Dependency

class Dependency
{
}

// Service

juriansluiman

Proposal for a new navigation component

This document is a start to get a new navigation component of the ground. The current Zend\Navigation has shown to be a powerful component for navigation purposes. On the other hand, the code is since it's introduction in Zend Framework 1.8 not really updated. The complexity is for some features very difficult to comprehend. In ZF2, the overhaul of the view helpers made it even more difficult to customize the behaviour of Zend\Navigation.

The good parts:

1. A structure of containers and pages to create hierarchal trees
2. A set of domain layer-like objects (containers and pages) and view helpers to render them into html
3. The option to mark pages as "active"
4. The option to tune visibility of pages
5. The option to attach an ACL object to the navigation list to show or hide parts based on access permission

juriansluiman

<?php
namespace Application;

use Locale;
use Zend\EventManager\Event;
use Zend\ModuleManager\Feature;

class Module implements
    Feature\BootstrapListenerInterface
{

juriansluiman

Assetic module in ZF2

This file describes my opinion of the integration of a public asset management tool within Zend Framework 2. It doesn't necessarily involve Assetic, but because Assetic is the most advanced and most used tool, I will focus on that. There is already an alternative module for Assetic integration, but the configuration of this module strikes 100% against my opinion of usage patterns. Therefore I write this document, to open up the discussion about improvements of zf2-assetic-module or write an alternative module.

Main usage pattern

The people using asset management tools are probably the frontend developers, as they write the html code in views, layouts etc. Currently they use helpers like headLink, headScript and inlineScript to control the assets. Starting point for this text is their workflow should not change as much as possible.

This means, an Assetic module should override the view helpers plugin broker, providing al