Sorry not a fan of this one. I'd be happy if you wanted to make it a class property in the HtmlView class (you can init it in the constructor). But I think that's the limit I'm happy with.

I also not very like this approach, was a first idea I got :)

class property in the HtmlView

This not much helpful,
example in the fields layout it will not be available, or when layout rendered with LayoutHelper::render()

hm hm, need a class with shortkut methods ?

I mean in theory you can do the same class property in the layout class I guess. But feels a lot more grim - like layouts aren't really designed for this stuff.

yeap, then we have to do it in plugins, modules, that even worse :)

Dunno. But there's literally no point in having it in a JHtml helper. The intended goal for the container is to facilitate DI - not have more magic helpers :)

The intended goal for the container is to facilitate DI - not have more magic helpers :)

It not really about magic, more about make it shorter to work faster (some kind of proxy)
like in Laravel with helpers https://laravel.com/docs/5.8/helpers#method-url , I know exactly like this are not possible, but I like the idea

What george wanted to say is that the Factory should not be called in the future.

Laravel's global functions and facades are the equivalent in Joomla to Factory::getContainer()->get('foo')->doSomething(). The entire point of introducing a dependency injection system is to favor explicit dependencies over magical calls like HTMLHelper::_() or calls to global static/singleton resources like Factory::getFoo().

While Laravel's features might make a developer's life easier, they aren't necessarily an architecturally correct thing. You might as well stick to the 3.x API design if the use of dependency injection in Joomla is such a problem.

okay, we have 3 places where we often use an assets:

• view
• module
• layout

(I ignore plugin, it different kind)

In view there already $this->document
In module can use $app->getDocument(), or can add one more variable $document
In layout we have nothing.

Do you think "injecting" Document instance in to FileLayout is a good idea?