Walrus class, used to monitor Walrus framework process, handle all developer tools like the Walrus development toolbar and the custom error and exception handler
A simple class that extend the PHP exception class, used to be handled by WalrusMonitoring
Walrus class, used as a tool for model, just like the WalrusController class
Walrus class, used to parse all configuration from YAML to PHP
Helpers are the package equivalent in Walrus, you can register them into the WalrusHelpers Class to use them in your backend or frontend script
Walrus Helpers are in the Helpers directory, for now only two helpers:
Some unit test have been written on PHPUnit, essentialy to cover the WalrusRouter and WalrusFiler class
WalrusFrontController give methods to help you handling front end development and as also method to help controller development. So we decided to rename it WalrusController
The router can now handle default page for 403 and 404 http error code, know the router call the controller class constructor when it execute it. As a part of the Walrus v1.0.0 update the router now use PHP compiled route instead of user's YAML.
You can now create an API controller using tusk, the Walrus CLI tool. A new "deploy" command as been created to create a testing project and compile all your configuration files to a single one in plain PHP
The getContent method can now return only a part of the file, the OS directory separator is now used everywhere instead of "/", Also two new methods had been added:
Walrus templates as been moved from the www/ directory to the project's root
Config as a new field "base_url" useful when you use walrus on a sub url. The config form also have a new design and some new test features. All the configuration files are now parsed to PHP for a better performance.
Smarty cache is configurated to be written on the cache/ directory at the Walrus root