Resource class is mainly used for importing static files through previously specified urls.
It is also capable of storing urls as groups which can be imported later using the resource
import() method or the @res() directive. While a group can be easily
created for static urls, in cases where a file is required in different groups, it might be become harder
to manage a single url. A new addition makes this easier by setting unique names for each file which can be
required later. Learn more from here
The integerated live server has been massively improved. Previously to version 2.0, live server uses a great amout of resources from the cpu. The effect of this is that the performace level of the device being used reduces in a very short period of time and browsers could crash often. Version 2.0 addresses this issue and the live server is now very efficient within the framework. With this new improvement, developers will now be able to run the live server for a longer period of time with lesser worries about performance issue.
Spoova has improved its window urls to support dotted strings which was not supported by the shutter methods in the previous updates because dots were treated as slashes. The window function used by shutter methods have also been improved reflect these changes. The effect of these updates results in an improved url structure and management. It also helps to reduce visual noise when when working with shutter methods. Learn more from here
In the previous updates, passing dependencies as arguments into window methods through shutters requires a more difficult approach. However, spoova has updated its window methods to allow for automatic dependency injection. This new feature is added in order to reduce lines of code and to help sanitize the entire code structure. More details are available here
The compiler function was handled as a detached component from the compiler engine in the previous versions of the frameworks. The effect of this detachment is the function can only be used once within the application. However, this effect was greatly felt with the introduction of bond components which requires a multiple use case for the compiler. In spoova version 2.0, the compiler function has been improved to allow for more use cases. The 2.0 version also introduces more compiler functions that determines how templates are rendered. More details are provided here
Bond components are components that helps to render template engines on a live state. They are entirely different from the live server used in development. These components are build upon existing template engine but they are injected as separate live templates into template files using live template directives. The entire requests are handled with event handlers which determines how the template files are requested, rendered and managed. Bond components are still on a beta phase and more information is provided here.
New methods have been added to Model and Form classes to help improve database communication.
These methods are Model->id(), Model->insertID(), Model->connection(),
Form::id() and Form::connection(). Details of these methods and their functions are provided
here.
Some classes and helper functions have been remodified. You can learn more about this from here.