<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 18 Jun 2013 02:21:07 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Agile Toolkit News: Yin and Yang of modern PHP UI Frameworks]]></title>
      <guid>http://www.phpdeveloper.org/news/15367</guid>
      <link>http://www.phpdeveloper.org/news/15367</link>
      <description><![CDATA[<p>
On the Agile Toolkit News site today there's <a href="http://blog.atk4.com/php-ui-frameworks/">a recent post</a> looking at a specific part of several of the different PHP-based frameworks out there - the UI or view layer. He wonders why, with UI-specific PHP frameworks out there, why the two can't just play nice together.
</p>
<blockquote>
I came over this old question on <a href="http://stackoverflow.com/questions/20709/which-php-framework-will-get-me-to-a-usable-ui-the-fastest">StackOverflow</a>: "Which PHP Framework will get me to a usable UI the fastest?" I couldn't help but wonder, why people are not aware of all those other PHP UI frameworks? There are few, right? If you google for "php ui" you can find them. Those are more generally referred to as UI toolkits. But why those toolkits are not known in the mainstream?
</blockquote>
<p>
He notes that most of the major frameworks leave you out to dry when it comes to presentation. They don't include much in the way of interface helpers in the name of modularity and backend focus. He suggests a few reasons why this happens and why the UI frameworks out there haven't made it to the mainstream. He gives three rules that could help this situation: view and object handling, giving developers a way to extend things easily and knowing the limitations of what the framework can do.
</p>]]></description>
      <pubDate>Tue, 02 Nov 2010 09:16:06 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Justin Ireland's Blog: Real-Time Embedded User Interfaces Using HTML/CSS/js and Websockets]]></title>
      <guid>http://www.phpdeveloper.org/news/14966</guid>
      <link>http://www.phpdeveloper.org/news/14966</link>
      <description><![CDATA[<p>
<i>Justin Ireland</i> has <a href="http://justinireland.com/real-time-embedded-user-interfaces-using-html-css-js-and-websockets/">posted an article</a> to his blog about creating real-time interfaces for your sites using the combination of HTML, CSS and Javascript to connect to a physical interface on the backend.
</p>
<blockquote>
Physical interfaces such as button panels or remote controls have many disadvantages. Panel controls require a dedicated display for feedback and physical access to a fixed location. IR remote controls offer only one-way communication with limited feedback and can become difficult to manage for multiple devices. [...] We propose a new type of solution to address these issues and bring simplified management and control to a broader market through embedded virtual interfaces.
</blockquote>
<p>
He lays out <a href="http://justinireland.com/wp-content/uploads/2010/08/Real-TimeEmbeddedVirtualUserInterfaces2.png">the structure of the application</a>, some of the issues that could come up in the connection (using <a href="http://en.wikipedia.org/wiki/Comet_(programming)">COMET</a> and <a href="http://en.wikipedia.org/wiki/Websockets">Websockets</a>). His <a href="http://justinireland.com/real-time-embedded-user-interfaces-using-html-css-js-and-websockets/3/">proof of concept</a> is a connection to <a href="http://www.hallresearch.com/page/Products/SW-HDMI-4">a HDMI switch</a> that can be talked to through an <a href="http://www.lantronix.com/device-networking/embedded-device-servers/matchport-ar.html">embedded controller</a> via a <a href="http://justinireland.com/wp-content/uploads/2010/08/SW-HDMI-4-demo.jpg">simple interface</a>.
</p>]]></description>
      <pubDate>Mon, 16 Aug 2010 13:17:41 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Raphael Stolt's Blog: PHP in Action book review]]></title>
      <guid>http://www.phpdeveloper.org/news/7898</guid>
      <link>http://www.phpdeveloper.org/news/7898</link>
      <description><![CDATA[<p>
<i>Raphael Stolt</i> has <a href="http://raphaelstolt.blogspot.com/2007/03/php-in-action-book-review.html">posted a book review</a> of one of Manning Publishing's PHP-related books, "PHP in Action: Modern Software Practices for PHP".
</p>
<blockquote>
Over the last few days I got the chance to skim through the upcoming Manning release "<a href="http://manning.com/reiersol/">PHP in Action: Modern Software Practices for PHP</a>" by Dagfinn Reiersøl et al. The reviewed book is seperated into four main parts, covering lots of interesting topics in a good and fluent writing style.
</blockquote>
<p>
<i>Raphael</i> outlines the book, mentioning the four parts the book is divided up into:
<ul>
<li>Basic PHP tools and concepts
<li>Developing applications via Test Driven Development
<li>Web presentation and user interfaces
<li>Object-oriented development including things like database abstraction
</ul>
<i>Raphael</i> gives the book a positive rating and recommends it for anyone that has the basics down and is looking to extend their knowledge that much more.
</p>]]></description>
      <pubDate>Wed, 23 May 2007 07:54:00 -0500</pubDate>
    </item>
  </channel>
</rss>
