including *.latte templates without caring the directory structure

So you want all templates that you include somewhere in one directory? It's sounds like very bad joke, projects with folders like Includes or Utils are considered as those with design flaws where author didn't make effort to make better project structure, but it's not always true, usually it's better use something like Article/@Common to have common templates that have to do something with articles.

But on the other hand, it would be cool to define template root, for instance my template root would be here https://github.com/…%40Templates so I could use {embed '/@Layout/Embeds/menu.latte'} anywhere, but until now I didn't have problem with paths, it's very rare when I move latte file to other directory.

Last edited by Rick Strafy (2020-11-06 23:13)

IMHO it's not the nette-way.

Why not a menu component that render its own latte placed in the same folder?

Then:

{control menu}

Maybe it's overkilling for just a static menu, but one day you would need more control over it (such as ACL, database stuff, etc…)

You can actually define a constant in app/bootstrap.php

define('TEMPLATE_ROOT', __DIR__ . '/templates/@common');

and then in any template use

{include TEMPLATE_ROOT . '/subdir/someRepeatingWidget.latte'}

You can set your own root for the Latte and then all “absolute” paths will be relative to this root:

		$this->template->getLatte()->setLoader(
			new Latte\Loaders\FileLoader(__DIR__ . '/templates')
		);

The problem is that Presenter is not ready for this and use absolute paths in methods like formatTemplateFiles(). The easiest solution is therefore to use a variable $root or as he wrote @filsedla define constant.

This is ugly:

{include '../../../menu.latte'}
{* or *}
{embed '../../../menu.latte'}{/embed}

I had this problem with a layout shared by multiple modules and I have found a way to hide this (not ideal but at least it hides this ugliness).

In your case just create a menu.latte in the same folder with {include ‘../../../menu.latte’}. Then in your latte files you can just use {include menu.latte}.

Last edited by dsar (2021-03-13 09:21)

sometimes i am away from site code for months.
so i forget, get rusty ..

today i am thinking, to maximize code reuse,
have directory structure:

→ LayoutModule (nothing but @layout.latte and children all imported…no Presenters…)
-->→ @layout.latte
-->-->→ child 1
-->-->→ child n+1 …
-->-->FrontModule
-->-->→ @layout.front.latte (imports @layout.latte above)
-->-->XYZModule
-->-->→ @layout.xyz.latte (imports @layout.latte above)
-->-->N+1…Module
-->-->→ @layout.N+1....latte (imports @layout.latte above)

then i would install ALL children, ALL blocks, ALL defines into LayoutModule and
use existing Latte tools to do so.

my objective is to minimize the number of layout children
and keep them all in one directory.
makes sense without new Loader code or Constant code?
thanks very much,
James

minor adjustment. left real @layout.latte in each module…
only children symlinked…

I see it roughly like this: https://www.youtube.com/watch?…

I agree that writing so much of ../ is error-prone. I have problem with it on every refactoring of directory structure as neither PhpStorm nor static analysis catch it so I end up with error in UI in the end.

Having alias like in node world or in sass is clever solution, but I vote for ~ component resolution only – it's just one char away and we don't want global space pollution again I think. So:

// something => 'src/whatever'

include '~something/template.latte' -> src/whatever/template.latte
include 'something/template.latte' -> ./something/template.latte

Last edited by dakur (2021-05-06 09:24)

In my humble opinion, the most elegant solution would be to specify the namespace using a colon:

{include 'widgets:social.latte'}

And adding namespaces via FileLoader:

$this->template->getLatte()->getLoader()->addDirectories(['widgets' => '.../templates/widgets']);

Or in config.neon with the help of LatteExtension:

latte:
	scanDirs: #or baseDirs, namespaces, templateDirs , etc.
		root: %appDir%/templates
		widgets: %appDir%/templates/widgets

Last edited by Slava.Aurim (2021-09-15 19:44)

I prefer using a function that returns a path, for example, to components. I can add the function to Latte via an extension:

namespace App\UI\Accessory;

use Latte\Extension;

final class LatteExtension extends Extension
{
    public function getFunctions(): array
    {
        return [
            'component' => fn(string $path) => $this->root . '/components/' . $path,
        ];
    }
}

which I will register in the configuration file:

latte:
    extensions:
        - App\UI\Accessory\LatteExtension

Then, in the template, just use:

{include component('menu.latte')}

Would be nice if at least English section of board is on English…