Hi Peter, > The package looks neat, thankx !
No thanks, it was laying on the selves already for some time. If you are going to use it, please make sure to download the latest version *WARNING* the question and the answer builder extended from object, but also contained a number and owner field themselves, in the editwizards it still works fine, but in the editors you get a "you're not allowed to change field number" *WARNING* And yes, no money back guarantee! > As for the postprocessing, I intend to store the form entries in a denormalized way in database table/mmbase node. We can set a > restriction to e.g. max 15 fields per form and then store each form-entry in a record, each answer in a column (field). > I think I have a good case for denormalisation here because storing the form entries into a two node structure with a posrel (e.g. > formresults and formanswers) will have a negative impact on the performance of the back-end function where editors > want a quick overview and speedy filter functionality on the results which are expected nto run into the thousands > and more for some forms (better not have triple joins dish up these results) Yes, yes, this makes it all very generic ;-) Maybe, you could cache the triple joins in memory or in an additional table? You could update the join in memory / table on a regular base by using the crontab developed by Kees/Michiel > solution with the picture with a code on it that the end-user has to type over in a form field ? > Like Yahoo and Hotmail registration do, that looks pretty neat to me. I like the solution offered by Johannes, it's clean and functional. Did anybody already implement it? If not i'll do it myself. Kind regards, Henk.
