Suppose that you wrote a complex template...
It has a header, footer, sidebars, h1, site logo...
when visiting any page that relates, let's say, the user profile.
Supposingthat you're using some standard MVC stack you'd probably have
something like a site.xml template and a user.xml:
<!-- add your JS here! -->
<!-- add your CSS here -->
The big advantage I personally see in this way of developing is that your
template doesn't need to be aware of every variable that could be injected
in it. If you have specialized views, then those views should handle
variables and replace slots.
This makes your template independent from your app and also reusable, and
also less fragile and subject to bugs or VariableNotFound exceptions :)
I often define dozens of slots and macros... Also if I don't use them, like:
<!-- stuff -->
This makes me life easier when I want to place a banner in that position in
future... I just have to generate the content somewhere else and then stuff
it in there with metal:fill-slot. No logic needed in the template. The final
view can handle that :)
On 11 July 2011 09:40, Anton Andriyevskyy <x.meg...@gmail.com> wrote:
> Ok, Marco, so actually we are still continuing to use macro, but we make
> them more dynamic
> by defining slots, correct?
> Then still I have question how it's better then defining macro (instead of
> fill-slot) and call it
> with variable macro name inside template?
> Any thoughts?
> Anton Andriyevskyy
> Business Automation & Web Development
> On Mon, Jul 11, 2011 at 10:26 AM, Marco Pivetta <ocram...@gmail.com>wrote:
> PHPTAL mailing list
PHPTAL mailing list