• We have a plan for making the Horde UI consistent between all applications and application views, as well as to make it look much better. Also to reduce the number of views we maintain, hopefully increasing our developer productivity
• Some really snazzy automated updates coming for the demo server
• The develop branch of nag now supports ajax completion of tasks, creating tasks, and basic viewing of tasks
• Trean finally has a migration from folders to tags, with basic working functionality for viewing bookmarks with tags. This was on my list FOREVER.
• Lots of good discussion about how we fit into the larger PHP and groupware ecosystem
• New timezone support from Jan
• New weather support to replace the now-commercial weather.com feed
• New documentation tools

... and almost certainly a ton more that is slipping my mind right now. Going to miss everyone once we head our separate ways again tomorrow, but hopefully the momentum will keep up, and I'm really looking forward to next year!

• Much better support for unicode characters
• We now auto-link URLs like example.com/foo
• Support for some limited parentheses matching so that URLs that contain matching parentheses are properly matched, even if a parentheses is the last character in the URL

Horde's pattern differs from the one posted by Gruber in a few ways, as well:

• It does not match mailto: URLs. This is to better match how Horde has historically separated linking of web addresses from email addresses; mailto: links are handled by Horde_Text_Filter_Emails.
• It matches URLs that start with ://
• URL protocols are limited to 20 characters to avoid excessive memory use when PCRE does backtracking
• "+" is allowed in a protocol (so svn+ssh:// works)

A good-sized list of test data has been incorporated into the Horde_Text_Filter test suite, but let me know if there are kinds of URLs that used to work but now don't, or if you see any other problems with the new auto-linking. Hopefully the new pattern will help polish the experience for those using the new Horde 4 alphas!

The neat thing about this implementation is that it doesn't duplicate the string, and it also doesn't use global scope to pass the string to the stream wrapper. The first is accomplished through references; not such a huge trick. The second is harder, since there isn't an obvious way to pass arbitrary data to a stream wrapper implementation. You can pass an object to fopen() as the $path, and if it has a __toString() method it will be used - an interesting trick that I'm still looking for a good use for. Unfortunately the string-ified value is what gets passed to stream_open() inside the stream wrapper implementation.

But! You can use the stream context to pass arbitrary parameters. So the $context parameter becomes the vehicle to pass the Horde_Support_StringStream object to the stream methods, which are implemented in Horde_Stream_Wrapper_String.

Here's an example:

$str = 'large data passed as a string';
$stream = new Horde_Support_StringStream($str);

$fp = $stream->fopen();
while (!feof($fp)) {
    $chunk = fread($fp, 1024);
    // Do something chunked
}

<?php

// To populate an <entry> element:
$e = new Horde_Xml_Element('<entry/>');
$e->fromArray(array(
    'id' => 1,
    'title' => 'Hi neighbor!',
    'author' => array('name' => 'Chuck', 'email' => 'chuck@horde.org'),
));
echo $e->saveXmlFragment();

<entry><id>1</id><title>Hi neighbor!</title><author><name>Chuck</name><email>chuck@horde.org</email></author></entry>

<?php

$e = new Horde_Feed_Entry_Atom(array(
    'id' => 1,
    'title' => 'Hi neighbor!',
    'author' => array('name' => 'Chuck', 'email' => 'chuck@horde.org'),
));
echo $e->saveXmlFragment();

$e = new Horde_Xml_Element('<atom:feed/>');
$e->registerNamespace('dc', 'http://purl.org/dc/elements/1.1/');
$e->fromArray(array(
    'atom:entry' => array(
        'atom:link' => array(
            '#rel' => 'self',
            '#title' => 'Feed title',
            '#dc:date' => '2011-01-31 01:00:00',
            '#href' => 'http://planet.horde.org/atom/',
        ),
    ),
));
echo $e->saveXmlFragment(true) . "\n";

Which produces:

<atom:feed xmlns:atom="http://www.w3.org/2005/Atom">
  <atom:entry>
    <atom:link xmlns:dc="http://purl.org/dc/elements/1.1/" rel="self" title="Feed title" dc:date="2011-01-31 01:00:00" href="http://planet.horde.org/atom/"/>
  </atom:entry>
</atom:feed>

To show off the new library, I've added a "quick add" feature to Nag, the Horde task manager. This adds a tasks/quickAdd registry method, that takes a single string. Dates in the string are parsed out as due dates, and multiple tasks can be added by separating them with newlines. Child tasks can also be created with indentation (including * or - lists).

For example:

laundry tomorrow
* buy detergent tonight 

Will create two tasks: a parent task named "laundry" with a due date of tomorrow, and a child task named "buy detergent" with a due date of tonight.

In addition to the API call there's a pretty UI for this:

Gives:

Others have these features of course. However our version handles some cases that some of them don't:

After a little hacking, the Horde_Controller package in git now has Cli request and response objects and this script is all you need to give command-line access to a set of controllers:

#!/usr/bin/env php
<?php

require 'Horde/Autoloader.php';

// Set up our request and routing objects
$request = new Horde_Controller_Request_Cli();
$response = new Horde_Controller_Response_Cli();
$mapper = new Horde_Routes_Mapper();
$mapper->connect(':controller/:action');

// Create our controller context.
$context = array(
    'mapper' => $mapper,
    'controllerDir' => dirname(__FILE__) . '/../lib/controllers',
);

// Dispatch.
try {
    $dispatcher = Horde_Controller_Dispatcher::singleton($context);
    $dispatcher->dispatch($request, $response);
} catch (Exception $e) {
    var_dump($e->getMessage());
}

Error handling can obviously be improved, and your controllers need to produce plaintext output for this to be friendly, but it gives you the flexibility to add new commands to your script just by dropping in new controller classes to the controllerDir.

Arguments are parsed with the Horde/Argv package, using a new allowUnknownArgs parameter that auto-creates simple text values for options unknown to the parser. This lets you take arbitrary command line arguments in your controller without having to tell the dispatcher script what arguments you expect ahead of time (of course the trade off is that the dispatcher can't validate the arguments, so the controllers are responsible for that, just like they are with web requests).

Here's an example of invoking the index() method of a MigrateController class:

$ ./dispatch.php migrate

To invoke the currentVersion() method of the same controller:

$ ./dispatch.php migrate/current_version

To pass an argument named target_version with the value "11" to the controller's index() method:

$ ./dispatch.php migrate --target-version=11

It's still a work in progress, but I'm happy with the possibilities.

...

K is asleep, and Obama has been introduced. Even wide awake she wouldn't remember this; it will be up to J and I, and her grandparents and other elders, to tell her about it. I'm so proud and grateful to have that chance, both to have her to tell, and this moment to tell about.

...

K woke up just in time for the oath, and she stood on my lap for it. She still won't remember it, but now I can tell her she saw it. She was content through almost all of the speech before needing to get back to the important business of learning how to self-locomote.

...

My choices for lines to remember... from Obama:

"We reject as false the choice between our safety and our ideals"

and from the poem by Elizabeth Alexander:

"A farmer considers the changing sky/A teacher says, 'Take out your pencils, begin.'"

On Election Night, thinking mostly of over a year and a half of work and 1.3 billion emails and more, I said to J., "It's over". She responded, "No, it's just beginning." Indeed. Let us begin.