|
Databases can have computed fields in most implementations. Why not display it so that it all looks like one field, but when you go to edit, it breaks it out into two separate columns as in #2. When user clicks to edit, it should be relatively simple to figure out whether he clicked in the heading or the text and put the cursor/selection into the proper field.
What I'd probably do is z-order the two fields with the heading on top. When user goes to edit mode, I'd insert enough spaces in front of the text so it appears to start to the right of the heading. If the user edits the text and tries to delete these justification spaces, I'd force them back in. Kind of code-kludgey, but it should work.
When we get styles we can apply to things, the program should remember what the default style is for a heading and for the text and use those unless user overrides.
|