Download
Hello,
this topic is old, but I didn't want to open the same topic again.
I agree with the above comments, that a Template Engine for the Frontend Templates is not needed, as the Templates of GetSimple CMS are easy in structure and straight forward without the need of a Template Engine (TE).
But there are benefits of working with a TE when you deal with Modules (Plugins).
I am currently working with the Blog Plugin and frankly, for a standard user, new to PHP at al it is a very dificult thing to deal with the php based template.
Another benefit is, you as Developer can provide your template and the user/designer could make a simple override of it (for example in the directory data/other or another place where it won't be overwritten once your Module is upgraded).
Another benefit is, you don't need to use the eval-function to get your template displayed.
I know that there are many different Template Engines on the Open Source Market.
Many of them are too big for a CMS like this one.
And yes, you can say PHP can be used as TE as well.
But ask yourself this question: is it easy enough for non-developers to customize the layout?
There is just a little more work for the developer in the first stage, but later on even the developer will benefit from the logic/layout separation as he has no need to handle all the HTML inside his PHP code.
If there is no future plan to implement such a Template Engine into the core, how could it be implemented as a plugin so developers could "hook" into it if wanted?
I am new to this CMS but I am willing to share my (limited) skills and knowledge regarding Template Engines. I used dozens of them and there are lots of different Engines with a different focus.
My own focus lies on simplicity.
Interestingly I used RainTPL this time, without any know of this thread.
The Thread was started by someone suggesting the same TE.
And it's true that it is very lightweight (35kB only) and easy to use.
The Templates are cached so there they are even faster than the use of EVAL.
Generally I use the TWIG TE, but this one is bigger and I didn't want to overwhelm anyone with its size (and lots of different files whereas RainTPL uses ONE File and ONE Class only to handle all the work).
And yes, I agree with all of you that there is no or little use of a TE for the GetEasy Templates itself, but lots of benefits in its use for Plugin Layouts.
Kind Regards,
Serenado
this topic is old, but I didn't want to open the same topic again.
I agree with the above comments, that a Template Engine for the Frontend Templates is not needed, as the Templates of GetSimple CMS are easy in structure and straight forward without the need of a Template Engine (TE).
But there are benefits of working with a TE when you deal with Modules (Plugins).
I am currently working with the Blog Plugin and frankly, for a standard user, new to PHP at al it is a very dificult thing to deal with the php based template.
Another benefit is, you as Developer can provide your template and the user/designer could make a simple override of it (for example in the directory data/other or another place where it won't be overwritten once your Module is upgraded).
Another benefit is, you don't need to use the eval-function to get your template displayed.
I know that there are many different Template Engines on the Open Source Market.
Many of them are too big for a CMS like this one.
And yes, you can say PHP can be used as TE as well.
But ask yourself this question: is it easy enough for non-developers to customize the layout?
There is just a little more work for the developer in the first stage, but later on even the developer will benefit from the logic/layout separation as he has no need to handle all the HTML inside his PHP code.
If there is no future plan to implement such a Template Engine into the core, how could it be implemented as a plugin so developers could "hook" into it if wanted?
I am new to this CMS but I am willing to share my (limited) skills and knowledge regarding Template Engines. I used dozens of them and there are lots of different Engines with a different focus.
My own focus lies on simplicity.
Interestingly I used RainTPL this time, without any know of this thread.
The Thread was started by someone suggesting the same TE.
And it's true that it is very lightweight (35kB only) and easy to use.
The Templates are cached so there they are even faster than the use of EVAL.
Generally I use the TWIG TE, but this one is bigger and I didn't want to overwhelm anyone with its size (and lots of different files whereas RainTPL uses ONE File and ONE Class only to handle all the work).
And yes, I agree with all of you that there is no or little use of a TE for the GetEasy Templates itself, but lots of benefits in its use for Plugin Layouts.
Kind Regards,
Serenado
