Is IFormComponent interface intended to be used also for form "chunks" meaning for components representing certain input fields aggregation? Imagine we have a ContactForm component used in different pages to gather phone numbers, emails etc (just simple a simple TextField components aggregate) using a simple xml component definition and an html template. I thought the advantage of having it implement IFormComponent would be to possibly have at the end common validation and access to including form (the ValidationDelegate etc. etc.) am I right or is IFormComponent just thought
Another thing I don't understand is which method one MUST implement by extending AbstractFormComponent (which might not be a good idea in my case because we actually "render" the component with a template): e.g. there are many abstract methods that are not implemented by TExtField (getForm()) but still used. I guess AbstractFormComponent are then enhanced at runtime (by whom?) but sometime is quite difficult to understand what MUST be enhanced and what not. All in all: would you consider a general good idea to implement the IFormComponent interface for all components that are in fact part of a Form?
