compared with
Current by Benoît Durand
on Nov 23, 2011 20:53.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (24)

View Page History
{toc}
<ac:macro ac:name="toc" />

h2. Information
<h2>Information</h2>

* Date: 23 November 2011, 17:00-18:00 UTC
* [Agenda|2011-11-23 Meeting Agenda]
* Moderator: Ralph Schindler (nickname ralphschindler)
* Next meeting: [Wednesday, 7 December 2011, 17:00 UTC|2011-11-23 Meeting Agenda]
<ul>
<li>Date: 23 November 2011, 17:00-18:00 UTC</li>
<li><ac:link><ri:page ri:content-title="2011-11-23 Meeting Agenda" /><ac:link-body>Agenda</ac:link-body></ac:link></li>
<li>Moderator: Ralph Schindler (nickname ralphschindler)</li>
<li>Next meeting: <ac:link><ri:page ri:content-title="2011-11-23 Meeting Agenda" /><ac:link-body>Wednesday, 7 December 2011, 17:00 UTC</ac:link-body></ac:link></li>
</ul>

h2. Summary

h3. Magic Routing
<h2>Summary</h2>

* New users coming from ZF1 to ZF2 expect the /:module/:controller/:action to work as in ZF1
* Given the current module architecture, facilitating the above magic route is prohibitively expensive:
** one must know the full set of controllers and actions, and they must currently be exposed as di services
<h3>Magic Routing</h3>

*It was decided* that routes and dispatchables/controllers would be required to be explicitly set instead of magically discovered. There is the possibility of a non-core module providing this functionality - currently located in EdpMagicRoute.
<ul>
<li>New users coming from ZF1 to ZF2 expect the /:module/:controller/:action to work as in ZF1</li>
<li>Given the current module architecture, facilitating the above magic route is prohibitively expensive:
<ul>
<li>one must know the full set of controllers and actions, and they must currently be exposed as di services</li>
</ul>
</li>
</ul>

h3. Beta2 Status

* There are 3 components who's "beta2 featureset" must be decided on for Beta2 (2 weeks away):
** Console
** Log
** Mail
* i18n has been removed as a potential blocker for beta2, and that more information on its future development and contributors is required at this time.
<p><strong>It was decided</strong> that routes and dispatchables/controllers would be required to be explicitly set instead of magically discovered. There is the possibility of a non-core module providing this functionality - currently located in EdpMagicRoute.</p>

*It has been decided* to create a beta2 and a beta3 featureset/requirement list for Console, Log, & Mail.
*It has also been decided* that we need to get a status, set of requirements, timelines and general update on i18n from Thomas to better understand it's development in the ZF2 context.
<h3>Beta2 Status</h3>

h2. Log
<ul>
<li>There are 3 components who's &quot;beta2 featureset&quot; must be decided on for Beta2 (2 weeks away):
<ul>
<li>Cache</li>
<li>Log</li>
<li>Mail</li>
</ul>
</li>
<li>i18n has been removed as a potential blocker for beta2, and that more information on its future development and contributors is required at this time.</li>
</ul>

{html:output=html}
<p><strong>It has been decided</strong> to create a beta2 and a beta3 featureset/requirement list for Cache, Log, &amp; Mail.<br />
<strong>It has also been decided</strong> that we need to get a status, set of requirements, timelines and general update on i18n from Thomas to better understand it's development in the ZF2 context.</p>

<h2>Log</h2>

<ac:macro ac:name="html"><ac:parameter ac:name="output">html</ac:parameter><ac:plain-text-body><![CDATA[
<style>
pre.log {

</pre>
{html}
]]></ac:plain-text-body></ac:macro>