One of the things that always frustrates me with technical manuals, is when they give you the syntax for everything that you can possibly do, and then explain each option completely apart for the others. 
This isn't about 'us and them', it's about recognising and acknowleding that there is a fundamental flaw in the way that the process is working.
Hi,
This is exactly my point about the way the manuals are written. When I buy a so called "Dynamic Suite" I expect a manual that is explaining the interaction between the different extensions including the "Form Builder" extension. What seems clear for the developer of the soft-ware doesn't have to ring a bell in my head. Not a dry summing of all possibilities but a clear step by step example of setting up a Dynamic Website with the "Dynamic Suite" and Form-builder to learn how to use the soft-ware. I don't think there is something strange about that. Fact is that I can do it in code and I know my way around in Dream Weaver (SPRY) but don't really understand the way the extensions have to be used, just because of the way it is "explained" in the manual.
