- Events have been moved and are now loaded through autoloading.
- FuzeWorks\Configurator now supports a setDebugEmail() method which will pass an email address to Tracy.
- The FuzeWorks Module system has been removed
- FuzeWorks\Layout is no longer a static class
- Fixed multiple bugs where paths were case-sensitive and did not work under Linux
- Latte engine is now able to return layouts and not only view them
The Last Merge for 1.0.0
This will be the last merge request with actual functional changes before 1.0.0.
After this a last MR will follow which sets every license header right and prepares for release.
> Closes#108
See merge request !52
Implemented a PSR-4 compliant scheme.
##### FuzeWorks can now be properly loaded by Composer, without any lost functionality.
> Closes#97
See merge request !50
Resolve "Make FuzeWorks Composer Compatible"
###### We want to make FuzeWorks Composer compatible so FuzeWorks can be loaded as a dependency.
This will allow us to load FuzeWorks/Core into FuzeWorks/Application, and possibly use FuzeWorks in other projects as well.
FuzeWorks will need to be trimmed down a lot, and directories should be determined in a different way. All tasks are still to be determined and put in here as a list.
> Closes#100
See merge request !49
The index file has been removed as well. This file has been replaced with the FuzeWorks\Configurator class. The configurator prepares FuzeWorks and loads it when requested. This allows for more flexible startups.
Implemented Nette/Latte engine.
This Engine allows for really neat ways to handle templates. It is an optional dependency which will be installed if composer is used.
See merge request !48
Implemented renewed Routing and Output system.
Everything is in accordance with issue #89 and #90.
> Closes#89
> Closes#90
> Closes#98
See merge request !47
This debugger allows for advanced debugging for both development and production environments.
This did however require the implementation of an ENVIRONMENT constant. This has been put in the index file. If no constant is set it will be set by the core class and the default is PRODUCTION.
Chances are that the location for this constant will move in the future.
There is also a proper way now that fatal errors will lead to a 500 error on the screen. This is either done by Tracy or FuzeWorks, depending on if Tracy is available.
