history of changes

...sorry, no history. db-schema just stores when entry is made and by whom.

Thanks for your fast reply. How difficult is it to write a complete changelog? Can you point me to some interesting code lines in your sources? Must the database tables changed for such enhancement?

The problem is, such an form here should contain severe data that changes from time to time, and if several people overwrites the value several times we need to know who and when and what at a certain time.

The question is if any Trac plugin supports such feature. We thought that's a major advantage of an eform compared to real paper forms.

...should not be too difficult.

Current db schema:

  db_schema = [Table('wikiforms_fields',key=('field'))[ 					
						       Column('field'			  ),	  
						       Column('value'			  ),	  
						       Column('updated_by'		  ),	  
						       Column('updated_on', type='INTEGER')		
						      ] 						
	      ]

Extended db schema has to have the 'updated_on' column as additional key to allow separate values for each field/updated_on combination.

How several values are to be represented in the form is not clear to me.

Replying to anonymous:

How several values are to be represented in the form is not clear to me.

At the moment it's not clear to me how the changelog is represented on the form web page. First, I need to get your plugin running (see #10775) for being able to see something and to answer this question.

I supose, what people expect here is something like a special click on a form element to get to the changelog of it, or a global time-sorted changelog of the whole form.

Replying to falkb:

I supose, what people expect here is something like a special click on a form element to get to the changelog of it, or a global time-sorted changelog of the whole form.

1. The tooltip on each form element could tell the latest change.
2. The form could provide a link to a page where a changelog list is displayed. Although it should list in a readable style since the people who look at that are not programmers. A name in such changelog should not be cryptic but should give an easy accociation to the related form element.