2970
Quote:
It as already has been made clear from Smart factory that they do not intend on keep compatibility with XOOPS 2.3 and the move of all their modules is a big indication that that they are moving further away from Xoops.
I have the understanding that it is the other way around. They are still compatible with 2.0.18, but 2.3.x isn't any longer. So, XOOPS is moving away from itself.
Quote:
We wouldn’t expect every new program to run on Windows 95 or Windows NT would we? Same has to be said with Xoops.
No, and I don't either. When I am talking about compatibility is that when a module runs perfect with 2.0.18, it should still run with 2.3.3.
For newer modules which use the extended features of 2.3.3, it is normal that they will not and don't have to run with 2.0.18.
If one follows the API of XOOPS this should not be a problem. New features has to be added with respect for the old. So, we get an evolution.
We don't want a revolution, where things are trown overboard or are changed for the changement.
Quote:
Also I notice a method like get_objs or something that performs two queries, one to get a count of all available objects and other to get just a limited number of objects. I think it would be better to use just one query, count the resulting array, and then unset the not need objects according to the criteria.
I think it is a question of scalabillity. If only a limited objects, say less then 100 are expected, your method isn't bad and simpler, but when there are 10 000 items, you run into trouble. I know one, who as that much articles in News and they count also the records.
Quote:
Goal is not to make a better module, is to make a functional module that others can work on and improve.
OK, the module is targetted for developers and not for users. I missed that point.