<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="http://www.hiveminds.co.uk/feed.xsl" ?>
<?xml-stylesheet type="text/css" href="http://www.hiveminds.co.uk/feed.css" ?>
<rss version="2.0" xml:base="http://www.hiveminds.co.uk">
<channel>
 <title>Hiveminds Magazine - More on Drupal Forms API and why I don't like it. - Comments</title>
 <link>http://www.hiveminds.co.uk/content/more-on-drupal-forms-api-and-why-i-dont-like-it.html</link>
 <description>Comments for "More on Drupal Forms API and why I don't like it."</description>
 <language>en</language>
 <copyright>Hiveminds Magazine</copyright>
 <pubDate>Fri, 21 Nov 2008 05:51:25 -0800</pubDate>
 <lastBuildDate>Fri, 21 Nov 2008 05:39:20 -0800</lastBuildDate>
<item>
 <title>Isn't the author...</title>
 <link>http://www.hiveminds.co.uk/node/923#comment-736</link>
 <description>Isn't the author contributing by writing this post?

I found the post because I'm ready to freak out after spending countless hours digging through drupal's internals - including such craptastic wonders as the form api.

This is a message that needs to get heard.
</description>
 <pubDate>Wed, 08 Aug 2007 08:04:27 -0700</pubDate>
 <guid>http://www.hiveminds.co.uk/content/more-on-drupal-forms-api-and-why-i-dont-like-it.html#comment-736</guid>
 <category domain="/taxonomy/term/180/Drupal">Drupal</category>
 <category domain="/taxonomy/term/184/Web Developer">Web Developer</category>
</item>
<item>
 <title>Anyone can post feedback </title>
 <link>http://www.hiveminds.co.uk/node/923#comment-731</link>
 <description>Anyone can post feedback by making a comment just as you did. But there is a contact us link under the home link for those that want to make more personal contact.

There are no dates on the articles because they are not really necessary. In cases of anything deemed out of date the readership usually posts that the information contained has been updated in a new version or that improvements have been made. All articles should contain the version and or build of the software involved.</description>
 <pubDate>Sun, 05 Aug 2007 02:19:34 -0700</pubDate>
 <guid>http://www.hiveminds.co.uk/content/more-on-drupal-forms-api-and-why-i-dont-like-it.html#comment-731</guid>
 <category domain="/taxonomy/term/180/Drupal">Drupal</category>
 <category domain="/taxonomy/term/184/Web Developer">Web Developer</category>
</item>
<item>
 <title>archive.org</title>
 <link>http://www.hiveminds.co.uk/node/923#comment-730</link>
 <description>This post shows up in the Internet Wayback Machine as far back as March, 2006. Things have changed a lot since then.

Sorry to say that at first glance I'm not terribly impressed with this site. There's no feedback form (I did find a link to hivemindz.com/hm/?q=feedback but there's nothing there). Articles need date information for when they are posted.</description>
 <pubDate>Sat, 04 Aug 2007 13:32:53 -0700</pubDate>
 <guid>http://www.hiveminds.co.uk/content/more-on-drupal-forms-api-and-why-i-dont-like-it.html#comment-730</guid>
 <category domain="/taxonomy/term/180/Drupal">Drupal</category>
 <category domain="/taxonomy/term/184/Web Developer">Web Developer</category>
</item>
<item>
 <title>Venting</title>
 <link>http://www.hiveminds.co.uk/node/923#comment-696</link>
 <description>I don't think this is anything to get worked up about.  Obviously  the reference to 4.7 puts this post as older though the theme doesn't show any date information so I can't tell. Its also obviously venting over having trouble figuring out form.inc which has improved greatly through the 5 and 6 development.

As far as themeing checkboxes go for people that might come across this you're better of taking a look at the form array passed to the form theme function.  The devel module has a dpr function which is very handy for this and I think you'll find themeing it into a table fairly straight forward at that point. If that doesn't make sense take a glance at the Drupal documentation of the FAPI for the code flow or ask around the Drupal places and someone can help you get on the right track.



</description>
 <pubDate>Wed, 06 Jun 2007 15:47:38 -0700</pubDate>
 <guid>http://www.hiveminds.co.uk/content/more-on-drupal-forms-api-and-why-i-dont-like-it.html#comment-696</guid>
 <category domain="/taxonomy/term/180/Drupal">Drupal</category>
 <category domain="/taxonomy/term/184/Web Developer">Web Developer</category>
</item>
<item>
 <title>Why don't you come up with patches?</title>
 <link>http://www.hiveminds.co.uk/node/923#comment-694</link>
 <description>If you are so damn good, and you think you can make drupal easier for developers and end users, why don't you contribute back to the community?</description>
 <pubDate>Wed, 06 Jun 2007 15:18:08 -0700</pubDate>
 <guid>http://www.hiveminds.co.uk/content/more-on-drupal-forms-api-and-why-i-dont-like-it.html#comment-694</guid>
 <category domain="/taxonomy/term/180/Drupal">Drupal</category>
 <category domain="/taxonomy/term/184/Web Developer">Web Developer</category>
</item>
<item>
 <title>More on Drupal Forms API and why I don't like it.</title>
 <link>http://www.hiveminds.co.uk/content/more-on-drupal-forms-api-and-why-i-dont-like-it.html</link>
 <description>If there is one failing that I have it is a compulsive need to improve on something that I see is not working as simply as it should. This has follwed me around from job job causing me to have to do things like redisign inventory systems and pull the entire wiring harness from a boat or automobile. In my mind complicated things should look simple even when the underlying design is so complicated most will not understand it. But if someone decides to peel back the layers each layer should be as easy to understand as the first. This is the secret. Complication should come in layers of simplicity.

</description>
 <pubDate>Thu, 11 May 2006 13:42:15 -0700</pubDate>
 <category domain="/taxonomy/term/180/Drupal">Drupal</category>
 <category domain="/taxonomy/term/184/Web Developer">Web Developer</category>
</item>
</channel>
</rss>
