The design became so different of 3.80.70, that it was merged and released as series 4.0.x
Modules and Themes
The Modules and Themes was moved from the app folder and namespace to the root, in their own directories: modules and themes
Every Module now lives in the namespace Modules\ instead of App\Modules\, and a Theme in the namespace Themes\ instead of App\Themes\
Views and Layouts
In the previous implementation, the Themes used to have a specific Layouts and Overrides folders, where was hosted the Layouts and Views overrides.
Now, a Theme use standard Views, hosted in the sub-folder Views, while contains also the Overrides directory, hosting the (optional) Views which are overridden by.
For example, a View instance creation was made using something like:
The design became so different of 3.80.70, that it was merged and released as series 4.0.x
Modules and Themes
The Modules and Themes was moved from the
app
folder and namespace to the root, in their own directories:modules
andthemes
Every Module now lives in the namespace
Modules\
instead ofApp\Modules\
, and a Theme in the namespaceThemes\
instead ofApp\Themes\
Views and Layouts
In the previous implementation, the Themes used to have a specific
Layouts
andOverrides
folders, where was hosted the Layouts and Views overrides.Now, a Theme use standard Views, hosted in the sub-folder
Views
, while contains also theOverrides
directory, hosting the (optional) Views which are overridden by.For example, a View instance creation was made using something like:
In the new design, a View instance creation is made specifying namespaced Views:
In a similar way, for creating a Layout instance, was used something like:
In the new design there is no distinct logic for Layouts, as they are just Views, then can be used: