7
Hi
There is a certain runtime overhead in using the XoopsForms which would be still worse is they were implemented as smarty templates. So xoopsforms are quite as they should be. Remember that smarty tends to be slow because every template has to be loaded from the file cache, checked it if need compilation, a lot of smarty logic, the plugin loader.... I don't start to talk about what a <{section}> tag does and how plugins are executed if they are not compile-time plugins.
I think the code/presentation separation arguments from McNaz are more like "I am a programmer and I do it my way" than what is really necessary. Generally, it is a good style to get HTML out of the php files and encapsulate your business logic into classes, but to not using xoopsforms because of some misunderstood rules...nonono. Use them, they allow you a good programming style.
The XOOPS core is not always consistent, this is quite ugly but usual if code has grown over the time. The most important rule I learned from 3 years of XOOPS programming: Try to understand XOOPS and try to understand the concepts, but stay pragratically.
greetings
birdseed
