No hurry over here.

This should probably wait for after the feature freeze since it didn't 
get started - yes?

Seems like a good system to me, though requires a bit more work to 
determine which are which. I'll work on it.

How about showing the composite field (but not the component fields) 
on the display tab.. and showing the component fields (but not the 
composite fields) on the edit tab?

It is now. Unfortunately that doesn't completely solve the problem 
since the updating field is initialized onload, so even if you give 
'name' a default value, it gets immediately wiped to '' once the form 
loads, since 'firstname' and 'lastname' are empty.



What about the idea of using CSS to make it not look like a form field?

Is it possible to define a default field value for new contacts?



The root of the problem is that the user does not really see that the 
form field is disabled as it's empty by default. If the field would 
contain something like "firstname lastname" and then gets cleared the 
first time a user types something in the firstname field, all would be 
fine.

If you use the optional 'tabs' entry in cfgSources, you can omit the 
'name' attribute from any of the tabs so it will not display.  I know 
it's not the best solution, but was offered as another option if 
nothing else would work. :)

Not sure what tabs have to do with it?



I modified Horde_Form_Renderer so that disabled variables are wrapped 
in a class="form-disabled". Can we work with that and CSS to make it 
look like text?

Yea, that makes sense, my bad :)



The idea about removing it from the display if your using a tabbed 
display is still an option though.

I think the idea is to make it not a text field, right?

Wouldn't it be more confusing for users to be able to type into a text 
field and have the value ignored or overwritten when the last/first 
name fields are edited?



You could always remove the 'name' field from display if it's really 
bothersome for your users.

Hello together,



when you create a new contact, the first thing the user will try is to 
type in the "name" field, which is a composite of firstname, lastname 
and others.

The control is disabled and dynamically updated via Javascript.



Would it be possible to replace the disabled widget by text only

and still update it via Javascript? Other ideas?



Thomas