Posted on: 2005/7/21 22:16
Re: smarty plugins generate much overhead!
First of all, thanks for your long and detailed replies. It must be one the strange rules of online forums that we discuss now about one small "by-the-way" sentence, but I´m familiar with that from my own portal ;)
I know about the difference between echoing html an using templates. I have developed two modules for xoops, one of them quite complex, so I am familiar with the XOOPS concepts and the core.
If you use the xoopsObject as a database abstraction layer, why was it implemented in xoops1, but will not really be used before xoosphere? without all that initvar/getVar/setVar stuff, things could be so easy for me. Even in xoops2, i see:
echo "<TD>" . $myvar . "</TD>"; (...)
On the other hand, I see many abstraction layers. So this doesn´t fit together for me. Why write an database abstraction for the 5% (guessed?) postgre Users (does postgre work with xoops? never tried...) instead of concentrating on mysql.
The XOOPS core is not clean. Everyone knows it. It is easy to find duplicate code. It is easy to find sql statements in the core where there should be criteria objects and criteriaobjects where there should be sql statements. it is easy to find notice errors and warnings.
Please don´t misunderstand me. I like xoops, i like the XOOPS community. But I´m a bit afraid that in the whole "abstraction layer movement", the small and dirty work - preserving a clean and consistent, fast and error free core - which means optimizing at a low level - is pushed aside.
I´m using XOOPS because I have a - compared to big web companies - a small site. The size and user traffic is comparable to www.xoops.org
. If my site was bigger, I wouldn´t use xoops, i wouldn´t use php. Instead, I would use a compiled language like java or .NET, i would not be using MySQL but MSSQL Server, Ingres or even oracle. I would be using a cms without any predefined layout. So I wonder if the road(map) that you decided to go is the right one. I´d rather see a xoops2.6 ;)