posted by chriskapp on
We are really proud to announce version 0.3 of Fusio. With this post we want to explain the changes of this release and the upcoming plans for the project.
We have moved the consumer implementation to AngularJS. Thereby we extended the functionality. Most notable we added a registration option where you can configure a remote login provider like GitHub and Facebook
It is now possible to manage tables from the provided connections through the backend
This is an internal change so that APIs which are in production mode never change even if the referenced schema or action changes
A new configuration panel was added to the backend where the user can configure various system settings
We have added a new action which simplifies building a response from multiple SQL queries
The help docs were improved. But this topic is still on our list to further on improve the documentation of this project
The user object can be now used in various actions
We have upgraded angular to the currect 1.5 version. The next step would be to move to angular 2 but this may take some time since all other depending projects like angular-bootstrap need to support version 2
It is now possible to add arbitrary parameters to an app. Theses parameters can be used in an action
With the 2.0 release the PSX framework moved to a component based architecture. We have updated the complete code base to work with the new 2.0 version
With this release we move a great step forward to a stable release. There are
some technical topics which we want to address in a 0.x release. The biggest
topic is probably to build an adapter marketplace. The adapter system is a great
way to simply provide an REST API for another system or to extend the
functionality of Fusio. We want to add a section to the website where all
adapters are listed and new developers can add an adapter by simply setting the
keyword fusio-adapter
into the composer.json
file.
Another great topic is to add a forms point to the backend where a user can build
a form which uses a specific route. These forms can then be embedded into an app.
You can checkout the TODO
for a complete list of ideas.
Besides these technical issues we also want to work on the marketing part of the project. As first step we have created a twitter account where we want to share mostly new releases of Fusio. We want to approach this in a grater way if we think that Fusio has reached a stable enough state.