<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="http://bugs.horde.org/themes/feed-rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>Move the Version column to be an attribute</title>
  <pubDate>Sun, 07 Sep 2008 18:57:51 -0400</pubDate>
  <link>http://bugs.horde.org/ticket/4577</link>
  <atom:link rel="self" type="application/rss+xml" title="Move the Version column to be an attribute" href="http://bugs.horde.org/ticket/4577/rss" />
  <description>Move the Version column to be an attribute</description>

  
  
  <item>
   <title>Once full attribute support is done, Version can just be an </title>
   <description>Once full attribute support is done, Version can just be an attribute instead of a special case.</description>
   <pubDate>Sat, 28 Oct 2006 23:49:42 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/4577#t25405</link>
  </item>
  <item>
   <title>See ticket 1078 for some additional requirements.</title>
   <description>See ticket 1078 for some additional requirements.</description>
   <pubDate>Wed, 15 Nov 2006 15:51:51 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/4577#t26117</link>
  </item>
  <item>
   <title>&gt; Once full attribute support is done, Version can just be a</title>
   <description>&gt; Once full attribute support is done, Version can just be an attribute 
&gt; instead of a special case.

Chuck, can you comment on &quot;full attribute support&quot;: what will be included, when will it be available, other tickets that relate to this support, etc?

This ticket seems to relate to one need we have, which is to have more robust attributes: enum, multi-select, radio, etc.  Extrapolating from this, and looking a little further down the road, we'd really like to see Whups more strongly integrated with other key tools in Horde:
* nag -- so that tickets can be quantized
* wicked -- so that better formatting can be applied
* hermes -- so that better effort estimates may be tracked/computed
* agora -- so more creative &amp; collaborative communication can occur

If there were a little more documentation on how to make framework elements speak to each other, and if we knew where the Horde system was moving as a whole, and if we knew the status of this particular request as a whole, we could tackle these independently and provide patches.</description>
   <pubDate>Tue, 01 Apr 2008 18:10:58 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/4577#t44307</link>
  </item>
  <item>
   <title>&gt; This ticket seems to relate to one need we have, which is </title>
   <description>&gt; This ticket seems to relate to one need we have, which is to have 
&gt; more robust attributes: enum, multi-select, radio, etc.

I think that's the most important thing that's left missing. Attribute support has otherwise matured a lot recently. We actually already have support for arbitrary Horde_Form fields for attributes, but only through the attributes hook. All that would need to be done is to extend the attributes table to include the Horde_Form field type and the interface to include a drop down list of available form fields (take ulaform as an example).

&gt; Extrapolating from this, and looking a little further down the road, 
&gt; we'd really like to see Whups more strongly integrated with other key 
&gt; tools in Horde:

This doesn't belong to this ticket and is actually something we would like to approach with a developer bundle.</description>
   <pubDate>Fri, 04 Apr 2008 07:53:41 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/4577#t44391</link>
  </item>
  

 </channel>
</rss>
