Who ever has watched Star-Trek, might know “Q”? In terms of it being an omnipotent being, whom bosses everyone around……

Yet in terms of Xoops….
It is something added to XOOPS and is explained on the XOOPS dev; if you search Google, you can find these pages still exist…..it sort of like “Q” in Star-Trek, there and not….

Anyways enough about Star-Trek and how by adding one letter “Q” to our Smarty calls, speeds things up in XOOPS and not just the Enterprise.
Just like that…. as in what we use to have is:
foreach<-----include something….(from Smarty’s own complier foreach and include)…..
we now have:
foreachq<---includeq something and that eliminates unwanted background tasks for rendering in Xoops, that it doesn’t need ( please tell me if this is all correct, it seems so).

As these where introduced in the new Smarty compiler files for Xoops, for this purpose to reduce rendering times….

So on calling items, we can also reduce task…by calling it from foreachq and then includeq…..

So then For “Q” XOOPS and save time…….

Seriously though, by adding just one letter “Q” to your XOOPS themes, makes allot of difference to rendering times (it appears)….

Quote:

Interesting - seems like it's me going to ask the obvious question..........

Xoops themes? Which files? Just theme.html or is there more to it than this?

Many thanks in advance

The foreachq, doesn't appear to work that well on the XOOPS themes blocks, its slower on finding the items, when including multiple blocks…… seems to be sluggish on swapping modules, as it doesn’t keep a record....

On finding item to begin with it is slower; there is slight caching on foreach normally, that isn’t there on foreachq...
yet it does include any individual items faster......
So when our user-section, multimenu are js and included, these are now foreachq and our main blocks foreach normal.
As then theme and module swapping is faster, as then it can find the files once, and continue with that.

includeq is for all items that need including quicker.
foreachq is when it is for end result to be rendered quicker.

You can edit like Snows new theme.html, using includeq for blocks of Xoops....
You can includeq any single files that have foreach and use foreachq in theme.html instead; this will mean no background tasks, or these can be used in any of XOOPS Smarty systems

Just upgraded everything in our module templates to includeq and foreachq…
Article uses this already and saves end call rendering…..
So remade templates for mylinks and mydownloads and then after added Q to it and these modules also….
Xml-line, Systems templates of 2.2.5rc2, profiles, Xoopspolls, wiwimod ….basically all module we use…..result seems faster….………