Eh? This is semantics that's not shown to the user. Do you really care 
what we call the text below a form field?



Anyway, try what I just committed.
Patches and UI help are always welcome...

I think "description" is more straight forward. "note" seems a bit ambiguous.



I do agree with the configuration name being "title" however. I think 
I mentioned this in my first post.
I think you should pride yourself with having good HCI throughout 
Horde. At the moment, it leaves something to be desired, and has been 
the cause of many modifications to my installation of Horde.

What about having the configuration variable name be the "title", and 
setting the longer description to the form "note"?

I don't care much about HCI in the configuration screen, the admins 
should be happy that they have an admin interface at all. And most 
people are using it once and never again. But I agree that for people 
who change settings often (like developers), it's sometimes hard to 
find the option that you know that must be there. But is that worth it?

At the moment, the conf.xml dictates how the configuration pages are 
currently laid out within the horde options.



Currently, the configuration options have a description which 
obviously describes the option, but there is no title displayed with 
the option. With every single option, you have to read a rather 
lengthily description in order to ascertain what that configuration 
option actually does.



From an HCI point of view, it is likely that titles for options would 
make it a lot quicker to sift through configuration options, because 
less text needs to be read.



For example, there is a configuration option in the mnemo application 
to display a print icon in the header. At the moment, this 
configuration option is a checkbox, with this text besides it:



"Should we display a Print link in the Horde application menus?"



I suggest that a title element would read:



"Display Print Link"



Or at least something to that effect, with the description AS WELL 
below the title.



Also from a HCI point of view, it would be a good idea to have the 
title in bold, because it is important, and should be easy to pick 
out. The description is less important, but needed if the user does 
not understand the title. I suggest that there is a linebreak in 
between the title and the description.



A suggested patch to a configuration option may look like this:



<configboolean name = "print" title = "Display Print Icon" desc = 
"Should we display a print icon in the application 
menus?">true</configboolean>



Thanks for your time in reading this submission.