<?xml version="1.0" encoding="utf-8" ?>

<rss version="0.91" >
<channel>
<title>phly, boy, phly</title>
<link>http://weierophinney.net/matthew/</link>
<description>Ramblings on PHP, Linux, and other Geeky Topics</description>
<language>en</language>
<image>
        <url>http://weierophinney.net/matthew/templates/matthew/img/s9y_banner_small.png</url>
        <title>RSS: phly, boy, phly - Ramblings on PHP, Linux, and other Geeky Topics</title>
        <link>http://weierophinney.net/matthew/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Form Decorators Tutorial posted</title>
    <link>http://weierophinney.net/matthew/archives/173-Form-Decorators-Tutorial-posted.html</link>

    <description>
        &lt;p&gt;
    As a continuing part of my MVC series, I&#039;ve posted a new article on 
    &lt;a href=&quot;http://devzone.zend.com/article/3450-Decorators-with-Zend_Form&quot;&gt;Form Decorators&lt;/a&gt;
    up on the DevZone.
&lt;/p&gt;

&lt;p&gt;
    I&#039;m hoping this will be the definitive guide to using form decorators. I
    cover the design decisions behind them, basics of operation, how to
    customize output by mixing and matching standard decorators, and how to
    create your own custom decorators. Among the examples are how to create a
    table-based layout for your forms (instead of the dynamic list layout used
    by default), and how to use a View Script as your form decorator in order to
    have full control over your form layout.
&lt;/p&gt;

&lt;p&gt;
    So, if you&#039;ve been playing with Zend_Form and having trouble wrapping your
    head around decorators, &lt;a href=&quot;http://devzone.zend.com/article/3450-Decorators-with-Zend_Form&quot;&gt;give it a read&lt;/a&gt;!
&lt;/p&gt;
 
    </description>
</item>
<item>
    <title>Zend Framework Q&amp;A Session</title>
    <link>http://weierophinney.net/matthew/archives/172-Zend-Framework-QA-Session.html</link>

    <description>
        &lt;p&gt;
    With 1.0 and 1.5 of &lt;a href=&quot;http://framework.zend.com/&quot;&gt;Zend Framework&lt;/a&gt;
    now released, there are a lot of questions flying around -- what will we do
    next, what components to expect, what are some of the best practices, etc.
    So, we&#039;re going to have an open 
    &lt;a href=&quot;http://devzone.zend.com/article/3448-Zend-Framework&quot;&gt;Question and
        Answer Session&lt;/a&gt; webinar, with all of us on the internal team.
&lt;/p&gt;

&lt;p&gt;
    If you have a question you want answered, please be kind enough to &lt;a
        href=&quot;http://framework.zend.com/wiki/pages/viewpage.action?pageId=43922&quot;&gt;submit
    your question in advance&lt;/a&gt;, so we have time to actually think about it
    (though you can always broadside us during the webinar).
&lt;/p&gt;

&lt;p&gt;
    &lt;a href=&quot;http://www.zend.com/en/company/news/event/webinar-zend-framework-the-big-q-a&quot;&gt;Sign up&lt;/a&gt; 
    in advance so you don&#039;t miss out!
&lt;/p&gt;
 
    </description>
</item>
<item>
    <title>View Helpers Tutorial on DevZone</title>
    <link>http://weierophinney.net/matthew/archives/171-View-Helpers-Tutorial-on-DevZone.html</link>

    <description>
        &lt;p&gt;
    I have another tutorial in my &lt;a href=&quot;http://framework.zend.com/&quot;&gt;Zend Framework&lt;/a&gt; MVC series up on &lt;a href=&quot;http://devzone.zend.com/&quot;&gt;DevZone&lt;/a&gt; 
    today, this time on &lt;a href=&quot;http://devzone.zend.com/article/3412-View-Helpers-in-Zend-Framework&quot;&gt;View
    Helpers&lt;/a&gt;. If you&#039;re curious on how to create view helpers, override the
    standard view helpers, or how some of the standard view helpers such as
    partials and placeholders work, give it a read!
&lt;/p&gt;
 
    </description>
</item>
<item>
    <title>ZF Plugins Tutorial on DevZone</title>
    <link>http://weierophinney.net/matthew/archives/170-ZF-Plugins-Tutorial-on-DevZone.html</link>

    <description>
        &lt;p&gt;
    I&#039;m doing a series of articles on various 
    &lt;a href=&quot;http://framework.zend.com/&quot;&gt;Zend Framework&lt;/a&gt; MVC topics for the
    &lt;a href=&quot;http://devzone.zend.com/&quot;&gt;Zend Developer Zone&lt;/a&gt;. Last week, I
    covered Action Helpers. This week, I cover 
    &lt;a href=&quot;http://devzone.zend.com/article/3372-Front-Controller-Plugins-in-Zend-Framework&quot;&gt;Front Controller Plugins&lt;/a&gt;.
    If you&#039;ve ever been mystified by or curious about this subject, head on over
    and give it a read!
&lt;/p&gt;
 
    </description>
</item>
<item>
    <title>Action Helpers in ZF</title>
    <link>http://weierophinney.net/matthew/archives/169-Action-Helpers-in-ZF.html</link>

    <description>
        &lt;p&gt;
    I&#039;ve posted &lt;a href=&quot;http://devzone.zend.com/article/3350-Action-Helpers-in-Zend-Framework&quot;&gt;a new article on Action Helpers&lt;/a&gt; in Zend Framework&#039;s MVC
    on the &lt;a href=&quot;http://devzone.zend.com/&quot;&gt;Zend Developer Zone&lt;/a&gt;. If you&#039;ve
    ever wanted more information on these, follow the link.
&lt;/p&gt;

 
    </description>
</item>
<item>
    <title>DHH on PHP</title>
    <link>http://weierophinney.net/matthew/archives/168-DHH-on-PHP.html</link>

    <description>
        &lt;p&gt;
    Somebody on &lt;a href=&quot;http://twitter.com/&quot;&gt;Twitter&lt;/a&gt; pointed this out, and
    I thought I&#039;d spread the word: &lt;a href=&quot;http://www.loudthinking.com/&quot;&gt;DHH&lt;/a&gt; of &lt;a
        href=&quot;http://rubyonrails.org/&quot;&gt;Rails fame&lt;/a&gt; has posted a nice, short,
    and very interesting thought on &lt;a
        href=&quot;http://www.loudthinking.com/posts/23-the-immediacy-of-php&quot;&gt;&quot;The
        immediacy of PHP&quot;&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
    I&#039;ve been delving a little into Rails lately myself, and what I find is: use
    the right tool for the job. For green-field, self-hosted projects, Rails is
    not a bad choice, and offers a very easy way to get your application up and
    running quickly. But due to the fact that PHP was built for the web, there
    are any number of tasks that are simpler and faster to accomplish using it.
    Evaluate your needs carefully, and choose the tool that best addresses them.
&lt;/p&gt;

&lt;p&gt;
    It&#039;s nice to see leaders of projects like Rails having this same attitude.
    It&#039;s a breath of fresh air in the competitive market of web development
    frameworks.
&lt;/p&gt;
 
    </description>
</item>
<item>
    <title>Zend Framework 1.5 Podcast</title>
    <link>http://weierophinney.net/matthew/archives/167-Zend-Framework-1.5-Podcast.html</link>

    <description>
        &lt;p&gt;
    Cal has released a new &lt;a
        href=&quot;http://devzone.zend.com/tag/PHP_Abstract&quot;&gt;PHP Abstract&lt;/a&gt; podcast
    today on the &lt;a href=&quot;http://devzone.zend.com/&quot;&gt;Zend Developer Zone&lt;/a&gt;, an
    interview with Wil Sinclair, the project manager for &lt;a
        href=&quot;http://framework.zend.com/&quot;&gt;Zend Framework&lt;/a&gt;, and Brad Cottel,
    Zend&#039;s product Evangelist. In it, they talk quite a bit about the work I&#039;ve
    done on Zend Form, and also a lot about the proposal process. 
&lt;/p&gt;

&lt;p&gt;
    If you&#039;re interested in the new 1.5 features, or how the proposal process
    works and who contributes to the community, 
    &lt;a href=&quot;http://devzone.zend.com/article/3348-PHP-Abstract-Podcast-Episode-37-Zend-Framework-1.5&quot;&gt;give it a listen!&lt;/a&gt;
&lt;/p&gt;
 
    </description>
</item>
<item>
    <title>Dojo 1.1.0 Released</title>
    <link>http://weierophinney.net/matthew/archives/166-Dojo-1.1.0-Released.html</link>

    <description>
        &lt;p&gt;
    &lt;a href=&quot;http://dojotoolkit.org/&quot;&gt;Dojo&lt;/a&gt; announced today the availability
    of 1.1.0. 
&lt;/p&gt;

&lt;p&gt;
    I&#039;ve been toying with Dojo off-and-on for almost a year now. It&#039;s the most
    framework-y of the various JS toolkits I&#039;ve tried, and I particularly
    appreciate its modularity. (That said, it can lead to a lot of HTTP requests
    to your site if you don&#039;t create a targetted bundle with the modules you
    need.)
&lt;/p&gt;

&lt;p&gt;
    The 1.1.0 release has me pretty excited, as it finally is doing something
    most other JS frameworks have been doing for some time: its XHR requests now
    send the &quot;X-Requested-With: XMLHttpRequest&quot; header, which allows it to
    conform to the &lt;code&gt;isXmlHttpRequest()&lt;/code&gt; method in Zend Framework&#039;s
    request object. This makes it much easier to provide a standard mechanism in
    your server-side code for detecting AJAX requests, allowing context
    switching to be automated.
&lt;/p&gt;
 
    </description>
</item>
<item>
    <title>Login and Authentication with Zend Framework</title>
    <link>http://weierophinney.net/matthew/archives/165-Login-and-Authentication-with-Zend-Framework.html</link>

    <description>
        &lt;p&gt;
    I&#039;ve fielded a number of questions from people wanting to know how to handle
    authentication and identity persistence in Zend Framework. The typical issue
    is that they&#039;re unsure how to combine:
&lt;/p&gt;

&lt;ul&gt;
     &lt;li&gt;An authentication adapter&lt;/li&gt;
     &lt;li&gt;A login form&lt;/li&gt;
     &lt;li&gt;A controller for login/logout actions&lt;/li&gt;
     &lt;li&gt;Checking for an authenticated user in subsequent requests&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
    It&#039;s not terribly difficult, but it does require knowing how the various
    pieces of the MVC fit together, and how to use Zend_Auth. Let&#039;s take a look.
&lt;/p&gt;
 &lt;br /&gt;&lt;a href=&quot;http://weierophinney.net/matthew/archives/165-Login-and-Authentication-with-Zend-Framework.html#extended&quot;&gt;Continue reading &quot;Login and Authentication with Zend Framework&quot;&lt;/a&gt;
    </description>
</item>
<item>
    <title>Vim Productivity Tips for PHP Developers</title>
    <link>http://weierophinney.net/matthew/archives/164-Vim-Productivity-Tips-for-PHP-Developers.html</link>

    <description>
        &lt;p&gt;
    I use &lt;a href=&quot;http://www.vim.org/&quot;&gt;Vim&lt;/a&gt; for all my editing needs -- TODO
    lists, email, presentation outlines, coding in any language... everything.
    So, I thought I&#039;d start sharing some of my vim habits and tools with others,
    particularly those that pertain to using Vim with PHP.
&lt;/p&gt; &lt;br /&gt;&lt;a href=&quot;http://weierophinney.net/matthew/archives/164-Vim-Productivity-Tips-for-PHP-Developers.html#extended&quot;&gt;Continue reading &quot;Vim Productivity Tips for PHP Developers&quot;&lt;/a&gt;
    </description>
</item>
<item>
    <title>Using Zend_View Placeholders to Your Advantage</title>
    <link>http://weierophinney.net/matthew/archives/163-Using-Zend_View-Placeholders-to-Your-Advantage.html</link>

    <description>
        &lt;p&gt;
    Somebody asked for some examples of how I use the &lt;code&gt;headLink()&lt;/code&gt;,
    &lt;code&gt;headScript()&lt;/code&gt;, and other placeholder helpers, so I thought I&#039;d
    take a crack at that today.
&lt;/p&gt;

&lt;p&gt;
    First off, let&#039;s look at what these helpers do. Each are concrete instances
    of a &lt;em&gt;placeholder&lt;/em&gt;. In Zend Framework, placeholders are used for a
    number of purposes:
&lt;/p&gt;

&lt;ul&gt;
    &lt;li&gt;Doctype awareness&lt;/li&gt;
    &lt;li&gt;Aggregation and formatting of aggregated content&lt;/li&gt;
    &lt;li&gt;Capturing content&lt;/li&gt;
    &lt;li&gt;Persistence of content between view scripts and layout scripts&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
    Let&#039;s look at these in detail.
&lt;/p&gt;

 &lt;br /&gt;&lt;a href=&quot;http://weierophinney.net/matthew/archives/163-Using-Zend_View-Placeholders-to-Your-Advantage.html#extended&quot;&gt;Continue reading &quot;Using Zend_View Placeholders to Your Advantage&quot;&lt;/a&gt;
    </description>
</item>
<item>
    <title>Zend Framework 1.5 is on its way!</title>
    <link>http://weierophinney.net/matthew/archives/162-Zend-Framework-1.5-is-on-its-way!.html</link>

    <description>
        &lt;p&gt;
    As many know, &lt;a href=&quot;http://framework.zend.com/&quot;&gt;Zend Framework&lt;/a&gt; 1.5.0
    is almost ready for release... heck, it might even be released by the time
    you read this. There are a ton of new features worth looking into, but I&#039;ll
    list some of my own favorites here - the ones I&#039;ve been either working on or
    using.
&lt;/p&gt;
 &lt;br /&gt;&lt;a href=&quot;http://weierophinney.net/matthew/archives/162-Zend-Framework-1.5-is-on-its-way!.html#extended&quot;&gt;Continue reading &quot;Zend Framework 1.5 is on its way!&quot;&lt;/a&gt;
    </description>
</item>
<item>
    <title>Submitting Bug Reports</title>
    <link>http://weierophinney.net/matthew/archives/161-Submitting-Bug-Reports.html</link>

    <description>
        &lt;p&gt;
    Full disclosure: I am employed by &lt;a href=&quot;http://www.zend.com/&quot;&gt;Zend&lt;/a&gt; to
    program &lt;a href=&quot;http://framework.zend.com/&quot;&gt;Zend Framework&lt;/a&gt;. That said,
    the following is all my opinion, and is based on my experiences with Zend
    Framework, as well as answering questions on a variety of mailing lists and
    with other OSS projects (PEAR, Solar, and Cgiapp in particular).
&lt;/p&gt;

&lt;p&gt;
    One of my biggest pet peeves in the OSS world is vague bug/issue reports and feature requests. I
    cannot count the number of times I&#039;ve seen a report similar to the following:
&lt;/p&gt;

&lt;blockquote&gt;
    &amp;lt;Feature X&amp;gt; doesn&#039;t work; you need to fix it &lt;b&gt;now!&lt;/b&gt;
&lt;/blockquote&gt;

&lt;p&gt;
    If such a report comes in on an issue tracker, it&#039;s invariably marked
    critical and high priority.
&lt;/p&gt;

&lt;p&gt;
    What bothers me about it? Simply this: it gives those responsible for
    maintaining Feature X absolutely no information to work on: what result they
    received, what was expected, or how exactly they were using the feature. The
    reviewer now has to go into one or more cycles with the reporter fishing for
    that information -- wasting everyone&#039;s time and energy.
&lt;/p&gt;

&lt;p&gt;
    Only slightly better are these reports:
&lt;/p&gt;

&lt;blockquote&gt;
    &amp;lt;Feature X&amp;gt; doesn&#039;t work -- I keep getting &amp;lt;Result X&amp;gt; from it,
    which is incorrect.
&lt;/blockquote&gt;

&lt;p&gt;
    At least this tells the reviewers what they reporter is receiving... but it
    doesn&#039;t tell them how they got there, or what they&#039;re expecting.
&lt;/p&gt;

&lt;p&gt;
    So, the following should be your mantra when reporting issues or making feature requests:
&lt;/p&gt;

&lt;ul&gt;
    &lt;li&gt;What is the minimum code necessary to reproduce the issue or show the desired API?&lt;/li&gt;
    &lt;li&gt;What is the expected result?&lt;/li&gt;
    &lt;li&gt;What is the actual result?&lt;/li&gt;
&lt;/ul&gt;
 &lt;br /&gt;&lt;a href=&quot;http://weierophinney.net/matthew/archives/161-Submitting-Bug-Reports.html#extended&quot;&gt;Continue reading &quot;Submitting Bug Reports&quot;&lt;/a&gt;
    </description>
</item>
<item>
    <title>Zend_Form Webinar Wednesday</title>
    <link>http://weierophinney.net/matthew/archives/160-Zend_Form-Webinar-Wednesday.html</link>

    <description>
        &lt;p&gt;
    Just an FYI for anyone interested: I&#039;ll be performing a webinar for this
    week&#039;s Zend Wednesday Webinar series on 
    &lt;a href=&quot;http://framework.zend.com/manual/en/zend.form.html&quot;&gt;Zend_Form&lt;/a&gt;.
    You can get details on the webinar and how to register for it at 
    &lt;a href=&quot;http://www.zend.com/en/company/news/event/webinar-zend-framework-forms&quot;&gt;the Zend_Form webinar information page&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
    I&#039;ll be covering the design of Zend_Form, the basic usage and 
    various classes and plugins available, and internationalization of your
    forms. Please join me Wednesday at noon EST!
&lt;/p&gt;
 
    </description>
</item>
<item>
    <title>Zend_Form Advanced Features</title>
    <link>http://weierophinney.net/matthew/archives/159-Zend_Form-Advanced-Features.html</link>

    <description>
        &lt;p&gt;
    I&#039;ve been working on &lt;a href=&quot;http://framework.zend.com/wiki/display/ZFPROP/Zend_Form&quot;&gt;&lt;/a&gt;
    for the past few weeks, and it&#039;s nearing release readiness. There are a
    number of features that Cal didn&#039;t cover in his 
    &lt;a href=&quot;http://devzone.zend.com/article/3030-Lifting-the-Skirt-on-Zend-Framework-1.5---Zend_Form&quot;&gt;DevZone coverage&lt;/a&gt; 
    (in part because some of them weren&#039;t yet complete) that I&#039;d like to
    showcase, including:
&lt;/p&gt;

&lt;ul&gt;
    &lt;li&gt;Internationalization&lt;/li&gt;
    &lt;li&gt;Element grouping for display and logistical purposes&lt;/li&gt;
    &lt;li&gt;Array support&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
    This post will serve primarily as a high-level overview of some of these
    features; if you&#039;re looking for more in-depth coverage, please review the
    unit tests. &lt;img src=&quot;http://weierophinney.net/matthew/templates/matthew/img/emoticons/smile.png&quot; alt=&quot;:-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt;
&lt;/p&gt;
 &lt;br /&gt;&lt;a href=&quot;http://weierophinney.net/matthew/archives/159-Zend_Form-Advanced-Features.html#extended&quot;&gt;Continue reading &quot;Zend_Form Advanced Features&quot;&lt;/a&gt;
    </description>
</item>

</channel>
</rss>
