26
Hi,
I have been doing a lot of module coding the last few months and find myself spending a lot of time trying to sidestep, extend or sometimes even totally ignore the XOOPS forms due to some (as far as i can see) shortcomings. I have a few questions regarding XOOPS forms as they are implemented in the lastest 2.0 release and about potential extentions put there.
1) When using XoopsForms with template files a LOT of undocumented tags seem to get passed to Smarty that need to be wrapped in HTML forms. This hardly seems like a time saver. Am I missing some system that automatically does this wrapping?
Presently I often use output buffering to capture the rendered HTML by the forms to pass that to my templates but that hardly seems like the intended way to use the XOOPS forms.
2) Are there some third party XOOPS form extentions out there that provide any or all of the following?
- Client and server side validation that goes further than just checking wether a textbox contains an empty string.
- Date/time control that accepts and displays date/time according to local settings instead of the default Unix yyyy-mm-dd
- Custom validation message instead of using the control label in validation output.
Any pointers would be much appreciated.
/Dirk
