<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.web.ezcomponents.devel">
    <title>gmane.comp.web.ezcomponents.devel</title>
    <link>http://blog.gmane.org/gmane.comp.web.ezcomponents.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4049"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4047"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4044"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4041"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4040"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4039"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4038"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4033"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4031"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4030"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4027"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4023"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4016"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4012"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4005"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4004"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4001"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4000"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/3999"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/3997"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4049">
    <title>eZ Components 2008.2beta1 released</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4049</link>
    <description>Hello!

The eZ Components team just released the first beta version of the new 
2008.2 release. This beta version implements the issues that were found 
during our review process as well as some other major improvements. The 
MvcTools component received quite a bit of attention from both internal 
and external reviews, and therefore has quite a few changes. A new 
version of the Webdav component including support for locking and 
authentication has been bundled as well as beta version. Besides this, 
there is a good deal of other minor changes that you can find below in 
the ChangeLog.

The ChangeLog and other information can be found in the official release 
announcement: http://ezcomponents.org/resources/news/news-2008-12-01

</description>
    <dc:creator>Derick Rethans</dc:creator>
    <dc:date>2008-12-02T10:05:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4047">
    <title>ezcWebdavSimpleBackend class</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4047</link>
    <description/>
    <dc:creator>Urs Lang</dc:creator>
    <dc:date>2008-12-01T22:45:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4044">
    <title>ezcWorkflow difference between cancelling and ending aexecution</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4044</link>
    <description>Hi,

I'm wondering if there's any particular reason why
ezcWorkflow-&gt;cancel() doesn't call the method doEnd (which cleans
execution_state and workflow_execution tables).

The cancel() and end() methods has the same outcome in the execution's
attributes (activatedNodes, waitingFor) but in the database that new
status are not updated. This allow the execution to be resumed if I
reload the instance from the database.

Can someone explain me better the difference between cancelling and
ending a workflow instance and the current behaviour?

Thanks,

</description>
    <dc:creator>Cinxgler Mariaca Minda</dc:creator>
    <dc:date>2008-11-19T20:46:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4041">
    <title>HowTo incoperate ManyToMany Related data inezcPersistentObject, a proposal.</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4041</link>
    <description>There are cases when in many to many relationships you need additional data 
that is only relevant, when in the context of the m:n relation but in neither 
object context alone. Currently this is not possible in ezcComponents.

I have looked at the ezcPersistentSession and relation related source code and 
came to the conclusion that is not an easy task to integrate without looking 
somewhat hackish.

My first thought was to extend ezcPersistentSession::addRelatedOject to accept
a new parameter with the additional data to be saved in the relation table via 
an relation data object. This is a very bad solution, since you now have the 
problem of how to retrieve the addtional data, and how their representations 
is defined and can be accessed.

Then again, the data within m:n relation tables is only needed, when the 
relation is in full context, so i came up with a nicer solution that 
recognizes this relationsip: I would add a new 
ezcPersistentManyToManyDataRelation class that extends 
ezcPersistentManyToManyRelation. It has an additional property 
'manyToManyClass', which is a representation of the aggregated
data of destination and relation table.

"manyToManyClass" has to full fill a a state aggregation interface 
ezcPersistentObjectAggregate, that has to functions getStates() and 
setStates() which return arrays of setState() and getState() of the related 
objects where keys are unique definition table names '$def-&gt;table'. Internally 
then all resolutions between the different tables can be resolved by iterating
over the getStates() records and calling the appropriate means for each object 
state of the aggregate.

A note: Technically the relation table with data has no definition and hence 
the definition manager will fail to locate it.

Therefore many to many tables with data also have to have a definition file for 
this approach to work, also to define the fields that the relation table 
contains. A Definition has to exist for all the loader methods too. What 
information exactly this file should contain for my proposal to work i cant say 
for now, i'll have to build a prototype.

Any ideas and/or comments? This is by far no issue i have thought to the end, 
so in questions of detail my proposal might utterly fail. :-)

beberlei

Attachment: Some Use cases of using my proposed relation:

For a simple example in the ezcPersistentObject Tutorial context. Now 
'persons_addresses' contains additional data on how long this person is 
already registered at this address:

1. definition

$def-&gt;relations["Address"] = new ezcPersistentManyToManyDataRelation(
    "persons",
    "addresses",
    "persons_addresses"
);
$def-&gt;relations["Address"]-&gt;columnMap = array(
    new ezcPersistentDoubleTableMap( "id", "person_id", "address_id", "id" )
); 
$def-&gt;relations["Address"]-&gt;manyToManyClass = "PersonAddress";

2. PersonAddress

class PersonAddress implements ezcPersistentObjectAggregate
{
    /**
     * &lt; at &gt;var Address
     */
    private $address;

    /**
     * &lt; at &gt;var array
     */
    private $persons_addresses;

    public function getStates()
    {
        return array(
            'persons_addresses' =&gt; $this-&gt;persons_addresses,
            'addresses' =&gt; $this-&gt;address-&gt;getState();
        );
    }

    public function setStates(array $states)
    {
        foreach($states AS $table =&gt; $state) {
            switch($state) {
                case 'addresses':
                    $this-&gt;address = new Address();
                    $this-&gt;address-&gt;setState($state);
                    break;
                case 'persons_addresses':
                    $this-&gt;persons_addresses = $state;
                    break;
            }
        }
    }

    public function setRegisterDate($date)
    {
        $this-&gt;persons_addresses['register_date'] = $date;
    }
}

3 Use Case:

$person = $session-&gt;load('Person', 1);
$addresses = $person-&gt;getRelatedObjects();

foreach($addresses AS $address) {
    // now $address instanceof PersonAddress:
    $address-&gt;setRegisterDate(mktime(0, 0, 0, 5, 1, 2007));

    // session recognizes aggregation interface, iterates over the states
    $session-&gt;update($address);
}
</description>
    <dc:creator>Benjamin Eberlei</dc:creator>
    <dc:date>2008-11-15T10:15:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4040">
    <title>eZImageManager</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4040</link>
    <description/>
    <dc:creator>Rob Gaus</dc:creator>
    <dc:date>2008-11-14T22:55:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4039">
    <title>Webdav auth API change for extensibility</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4039</link>
    <description>Hi all!

I thought about changing the Webdav API for authentication slightly
before we once go stable with it, to make it easier for people to
implement additional / custom authentication schemes (like NTLM).

We currently have 3 interfaces for authentication:

interface ezcWebdavAnonymousAuthenticator
{
    public function authenticateAnonymous(
        ezcWebdavAnonymousAuth $data
    );
}

interface ezcWebdavBasicAuthenticator extends
    ezcWebdavAnonymousAuthenticator
{
    public function authenticateBasic( ezcWebdavBasicAuth $data );
}

interface ezcWebdavDigestAuthenticator extends
     ezcWebdavBasicAuthenticator
{
    public function authenticateDigest( ezcWebdavDigestAuth $data );
}

This means, that the server currently decides, which authenticator is
capable to handle which type of credential struct.

I'd suggest to go for a single authenticator interface now:

interface ezcWebdavAuthenticator
{
    public function authenticate( ezcWebdavCredentials $auth );

    public function getAuthHeader( $realm );
}

authenticate() returns true on successfull authentication, false on
failure and throws an exception if a struct is received that could not
be handled. getAuthHeader() returns an array of WWW-Authenticate headers
indicating which types of authentication are supported.

This would allow users to implement their custom authentication schemes
more easily. They need to extend the transport (and possibly client
specific transports), add a new credential struct and implement the
neccessary authentication() methods.

To make it easier to have basic and digest auth, I'd provide 2 abstract
base classes (1 for basic and anonymous, 1 for basic, digest and
anonymous) that produce the correct headers.

In addition I'd like to make the authorize() methods
(ezcWebdav(Lock)Authorizer) recieve the complete credential struct
instead of the username only. Just for the case that some authentication
scheme does not work with a username.

Does that sound reasonable to you?

Regards,
Toby
</description>
    <dc:creator>Tobias Schlitt</dc:creator>
    <dc:date>2008-11-12T06:55:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4038">
    <title>eZ Components 2008.2alpha1 released</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4038</link>
    <description>Hello!

After the earlier release of the first alpha releases of the MvcTools
components set, we're now releasing other alpha versions of other 
components.

The Document component now has support for reading and writing wiki 
formats, writing reST files and full support for XHTML. The Feed, 
Graph, Mail, PersistentObject, and Workflow components have all 
minor feature enhancements. The MvcTools component has seen many 
improvements over the first alpha after feedback. There is now also a 
tutorial[1] available.

The full release announcement can be found online [2].


[1] http://ezcomponents.org/docs/api/trunk/introduction_MvcTools.html
[2] http://ezcomponents.org/resources/news/news-2008-11-10

with kind regards,
</description>
    <dc:creator>Derick Rethans</dc:creator>
    <dc:date>2008-11-10T12:55:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4033">
    <title>transparent svg background</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4033</link>
    <description>Hi every body, very simple problem here, I'm trying to get a transparent 
SVG background, which is easy to make with a real SVG file, you just 
have to erase the background color definition.
Of course I've tried :

$graph-&gt;background-&gt;background = '';


But it didn't work, any ideas?

</description>
    <dc:creator>Julien Cochennec</dc:creator>
    <dc:date>2008-11-07T22:03:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4031">
    <title>Horizontal Bars diagram</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4031</link>
    <description>Hello! I'm new in the list. I'm using the june 2008 version under
linux (ubuntu). I have discovered these great components and trying to
use for several Open Source projects.

I'm trying to do two things using the graph component and I have one question:

- First is how to create an horizontal bars diagram. Is it possible?
If so, how can I do it?

- Second, How can I change the line thickness and border color for bar
diagrams? I've seen it in
http://kore-nordmann.de/blog/comparison_of_php_image_libraries_update.html

- Third. Are there more dataSetSymbols to use in line graphs?

Kind regards and thanks in advance,

Raul
</description>
    <dc:creator>Raul Mateos</dc:creator>
    <dc:date>2008-11-04T17:00:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4030">
    <title>Experiences with Zend Core for i5</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4030</link>
    <description>Hi,

I am a new to ezComponent. We are thinking about using it at our company.
We are running PHP via "ZendCore for i5" on some IBM i5 systems.

Does anybody here has any experiences with such a configuration?

Are there any known problems, hooks, suggestions for running 
ezComponents on the i5?

Thanks in advance for your advice.

Greetings
Thorsten
</description>
    <dc:creator>Thorsten Franke</dc:creator>
    <dc:date>2008-11-03T10:20:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4027">
    <title>EzcWorkflow</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4027</link>
    <description>Hi, I'm looking for EzcWorkflow manuals, tutorials, examples, ect...

I see the web of EzComponents, but i need more info

Regards


Daniel González Cerviño
tel 653965048
ikarush&lt; at &gt;gmail.com
</description>
    <dc:creator>Daniel González</dc:creator>
    <dc:date>2008-10-30T19:28:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4023">
    <title>auto fill up ezcGraphLineChart</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4023</link>
    <description>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello,

I 've a problem with the ezcGraphLineChart class. I have the following 
array as example:

array(7) {
    ["2008-10-14"] =&gt; string(2) "18"
    ["2008-10-15"] =&gt; string(2) "53"
    ["2008-10-21"] =&gt; string(3) "101"
    ["2008-10-22"] =&gt; string(3) "104"
    ["2008-10-23"] =&gt; string(3) "116"
    ["2008-10-24"] =&gt; string(2) "96"
    ["2008-10-25"] =&gt; string(2) "69"
  }

but for a clean graph I need a array like this:

array(7) {
    ["2008-10-14"] =&gt; string(2) "18"
    ["2008-10-15"] =&gt; string(2) "53"
    ["2008-10-16"] =&gt; string(2) "0"
    ["2008-10-17"] =&gt; string(2) "0"
    ["2008-10-18"] =&gt; string(2) "0"
    ["2008-10-19"] =&gt; string(2) "0"
    ["2008-10-20"] =&gt; string(2) "0"
    ["2008-10-21"] =&gt; string(3) "101"
    ["2008-10-22"] =&gt; string(3) "104"
    ["2008-10-23"] =&gt; string(3) "116"
    ["2008-10-24"] =&gt; string(2) "96"
    ["2008-10-25"] =&gt; string(2) "69"
  }

Is there a way to fill out the vacencies automaticly with the class?

Best Regards Stefan Riedel

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.6.3 (Build 3017)
Charset: ISO-8859-15

wsBVAwUBSQShHR4gSnXe4RZZAQg71wf/ZQIHNybJrmd4G9WYx0UxB7vbxL+GmlU3
Y9ZcK+Vpxhh0Y7ALpHSN9jk89fOugbk7QBMKZ2yz1AesVbwjmWu2u7P/nPUzSj4U
sI6I9HUDQqgLqDh6wHNIL3ep1qtfDQYS4h3PrHBzd8Ae5dqLokjGTLVe/LSYVMW8
c1hw1DX8T3/6A0xD40XOs+/shz7ZLx8lqvwckAvaUpRiUuDmjWX8m2E7/TJNM4Yi
BhTU0+zgXB8hdl7F7ULnwjYsduVrIMK/Lk5lMa8zHyw7/qFiFm7NQFan7mG4iAPI
cUTwV1Ga374G7bRUJr4D8Lg9mFhSP5BrJnVj7wbBs3WjbH7JMffeQg==
=JkwG
-----END PGP SIGNATURE-----
</description>
    <dc:creator>Stefan Riedel</dc:creator>
    <dc:date>2008-10-26T16:55:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4016">
    <title>Webdav lock purging</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4016</link>
    <description>Hi!

While working on the lock support I now dealt with purging of locks.
This part looks to be quite complex and would need to be done on almost
every request. It means very much overhead and IMO should not be done in
request processing itself.

I'd suggest to add a maintanance script to the Webdav component, which
must be called by the administrator of the server periodically. The
script locks the backend, goes through all locks and purges those that
are orphan.

This way, administrators can decide on their own, how much time is spent
on lock purging and how often they need it.

Any objections?

Regards,
Toby
</description>
    <dc:creator>Tobias Schlitt</dc:creator>
    <dc:date>2008-10-25T19:01:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4012">
    <title>template engines: anybody tested dwoo?</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4012</link>
    <description>http://dwoo.org/

At first sight it looks new, but promising.

I especially like the concept of subclassing instead of including.

HAs anbydoy tested it for speed / features vs. ezc templates?

Bye
Gaetano
</description>
    <dc:creator>Gaetano Giunta</dc:creator>
    <dc:date>2008-10-25T11:07:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4005">
    <title>components WorkflowSignalSlotTiein</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4005</link>
    <description/>
    <dc:creator>eddier waldir gallego rios</dc:creator>
    <dc:date>2008-10-23T21:00:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4004">
    <title>setting space between Y-axis and Y-axis labels</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4004</link>
    <description>Hello list,

I'm using "ezcGraphLineChart".

How do I set some spacing between my Y-axis and the Y-axis labels ?

In some situations the labels are over the axis and I'dd like to avoid
that.

thx
Joao


</description>
    <dc:creator>Joao Ferreira gmail</dc:creator>
    <dc:date>2008-10-23T09:36:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4001">
    <title>not register an object</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4001</link>
    <description/>
    <dc:creator>eddier waldir gallego rios</dc:creator>
    <dc:date>2008-10-21T03:42:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4000">
    <title>MvcTools tutorial: best practices</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/4000</link>
    <description/>
    <dc:creator>James PIC</dc:creator>
    <dc:date>2008-10-20T13:21:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/3999">
    <title>How to bind a UserInput field to a PersistentObjectfield?</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/3999</link>
    <description/>
    <dc:creator>James PIC</dc:creator>
    <dc:date>2008-10-20T06:24:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/3997">
    <title>constants vs. strings</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/3997</link>
    <description>Hi,

out of curiosity: There are several places in ezc where strings are used
internally as kind of flags or enums:

- Column Types in ezcDatabaseSchema
- MvcTools
- ?

In contrast Sebastian used numeric constants in ezcWorkflow to indicate
different activation states of nodes:

    const WAITING_FOR_ACTIVATION = 0;
    const WAITING_FOR_EXECUTION = 1;

I thought, that using constants should be preferred, because
- the compiler tells you, if you mistyped a constants name
- comparing two integers is faster then comparing two strings(?)
- You have a central place, where you can lookup all possible values

Or is there anything I missed?

Thanks for your time reading this,
</description>
    <dc:creator>Thomas Koch</dc:creator>
    <dc:date>2008-10-17T14:34:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/3996">
    <title>inDevMode</title>
    <link>http://comments.gmane.org/gmane.comp.web.ezcomponents.devel/3996</link>
    <description>Hi,

yesterday evening I started to port my ymcGitWiki[1] to MvcTools. I
found the following code in MvcTools/src/router.php:

    public function getRoutingInformation()
    {
        $routes = $this-&gt;createRoutes();

        if ( ezcBase::inDevMode() &amp;&amp; ( !is_array( $routes ) || !count( 
$routes ) ) )
        {
            throw new ezcMvcNoRoutesException();
        }

        foreach ( $routes as $route )
        {
            if ( ezcBase::inDevMode() &amp;&amp; !$route instanceof ezcMvcRoute )

ezcBase::inDevMode() is called several times in this method so it would
be better to save the mode once in a method local variable 
$inDevMode = ezcBase::inDevMode();

Another thing I thought about only now unfortunately:
Wouldn't it be faster to use a combination of 

define( 'EZC_PROD_MODE', TRUE ); // in ezcBase::setRunMode()
and 
if( !defined( 'EZC_PROD_MODE' ) ... {slow devmode code here} ?
  
[1] https://www.ohloh.net/projects/ymcgitwiki
</description>
    <dc:creator>Thomas Koch</dc:creator>
    <dc:date>2008-10-17T09:16:16</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.ezcomponents.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.ezcomponents.devel</link>
  </textinput>
</rdf:RDF>
