Version 3 should be the speed version you mean - it is now beta.Maybe a .2 speed release would be in order?
Caching and menus
Re: Caching and menus
Re: Caching and menus
where is 3?Piratos wrote:Version 3 should be the speed version you mean - it is now beta.Maybe a .2 speed release would be in order?
Re: Caching and menus
I'm talking about the CMSMs CORE, not the PIMENU. Sorry for the confusion.Piratos wrote:Version 3 should be the speed version you mean - it is now beta.Maybe a .2 speed release would be in order?
Re: Caching and menus
No problem , i'm talking about pimenu version 3.
I'm developer and betatester by myself. it works on my playing meadow (see downloadlink below).
i need some days to release it.
it uses only smarty and didn't write files by itself.
I'm developer and betatester by myself. it works on my playing meadow (see downloadlink below).
i need some days to release it.
it uses only smarty and didn't write files by itself.
Re: Caching and menus
Just looking at pimenu, no english instructions, so back to square one
Re: Caching and menus
tmp/templates is corrcet. tmp/templates is a standardfolder in the cms.
If pimenu is a module the complete smarty handbook must be a a part of this, because pimenu delivers ony data and the designer must use smarty.
The german doc has 12 pages , what a nonsens to put it in a help function - 10 kb script , 33 kb german doc plu s 33 kb english doc plus module overhead - i want spare execution time and memory and not grow them all up.
i'm not interesting at this .
Pimenu isn't a menu , because it makes no menu, that is the work of smarty.
And - i can change license every time (but i will not do this).
a module pimenu is absolutly nonsens . why the same in a module that is bigger and cost more memory .your menu would have been cms standard if it had been a module, and have the templates in the module subfolder, and the doc in the help function, with a lang folder in it, with de_DE.php for the module strings, including help strings (like this we could translate it for other languages in "cms standards").
If pimenu is a module the complete smarty handbook must be a a part of this, because pimenu delivers ony data and the designer must use smarty.
The german doc has 12 pages , what a nonsens to put it in a help function - 10 kb script , 33 kb german doc plu s 33 kb english doc plus module overhead - i want spare execution time and memory and not grow them all up.
i'm not interesting at this .
Code: Select all
your menu
plugins ... tags are standard too.would have been cms standard if it had been a module
And - i can change license every time (but i will not do this).
Last edited by Piratos on Sun Nov 20, 2005 10:18 am, edited 1 time in total.