Symfony2.1 ResourceWatcher usage example

resource_watcher_usage.php

<?php

$watcher = new Symfony\Component\ResourceWatcher\ResourceWatcher;



// track any change inside directory:
$watcher->track('some/folder1', function($event) {
    echo '['.$event->getType().'] '.$event->getResource()."\n"
});



// track only creations inside directory:
$watcher->track('some/folder2', function($event) {
    echo $event->getResource()." was created\n"
}, Symfony\Component\ResourceWatcher\Event\Event::CREATED);



// track only *.xml file changes inside directory:
$watcher->track(
    new Symfony\Component\Config\Resource\DirectoryResource('some/folder3', '/\.xml$/'),
    function($event) use($watcher) {
        echo '['.$event->getType().'] '.$event->getResource()."\n"

        // stop tracking when first even occurs:
        $watcher->stop();
    }
);



// start tracking:
$watcher->start();

What about adding tracking_id to event names? For example:

<?php
$watcher = new Watcher();

// We can require users to specify unique tracking id in `track()` method:
$watcher->track('twig_templates', new DirectoryResource('/some/dir', '/regex/'));

And this way, watcher will send both watcher.twig_templates.file_changed and
watcher.file_changed events for this particular tracking. In this case, user will be able to
choose whether he needs to receieve all or only specific-track events. This will remove
the need in FilteredListener, which complicates things a lot.

I guess by now everyone are agreeing on accepting both a callable and an object so I would not jump in on that.

I'm more inclined towards @everzet last option. Way easier to understand and use.

Yes, sounds good to me as well.

How about reversing the order of arguments function track($resource, $alias = null);?

Well, there should be 3 parameters at least - $resource, $trackingId and $trackedEvents because there's no reason to track any folder change if user only interested in a file_change