@odan yes, i see them, but i simply cannot understand. I’d like an update of the “slim framework” section that works with slim 4 (or a more detailed basic start).
Maybe im the stupidest programmer on the earth, or i am not alone with these questions . Someone has to ask the first question :).
Awesome! Thanks for understanding!
I’d like to put either my CSS/JS under /public , or even under …/templates (outside of public), and use functions like “assets({files: [‘Login/login.css’]})” to get them into the .html files. So everything is neat and pretty. That would be fun to learn!
Probably , when i understand it more. I’d laugh at even asking this… I dont know.
Thanks for the updated manual! It clarified some things.
$settings[‘public’] is not set, i guess this points to the /public-dir, but still, may confuse someone
Since im using the slim-skeleton with PHP-DI, i am using the “addDefinitions”-function to add Twig::class, i am failing at “->get(App::class)->getBasePath()” since its not instantiated here. What do i do here?
This is just optional. I replaced this part from the documentation with a simplified approach.
How to setup Twig with PHP-DI is already documented in the Twig-View documentation.
Thanks alot! I’ve actually got it all working! Although i do not know if its 100% properly setup, but it does generate cached css/js and i do receive the styles and js in the html with assets(), so … i am happy for now