It has been a while since I wrote a word about the next-gen Chevereto. Today I want to show and tell the actual work-in-progress behind Chevereto 4 and all the new business that I'm building here.
Spoiler alert: I don't have any dates yet, but I want to show you the work in progress.
Update 2019-09-19
You can follow the work in progress in the Chevere + Chevere V4 Trello board. I'm showcasing the new stuff and confirming the new system features.
Chevere Framework
The framework behind Chevereto 4 is Chevere. I've been working in this framework since May 2018, and a few weeks ago I started to publish its work-in-progress at GitHub.
Most of you won't have to mind about this framework thing at all, but for developers is a huge step forward which should bring more ease for development purposes.
Modernized
Chevere uses tools like composer, phpstan, scrutinizer and phpdoc. The code follows the PSR-12 formatting standard, it embraces strong typing and strict types. It includes console commands and works so neat that most of my development process is now "server-less". I can't recommend highly enough how great it feels to work with PHP like that. Here is what looks like:
At this time I've commands for forge a HTTP request, inspect and run callables. Later I will add cache, dump and other most-wanted developer tools.
APIs built with Chevereto\Core use the json:api standard and are self-exposed: The API communicates what it does and how you have to use it. No documentation needed, no manual routing.
Current development state and release dates
The framework development is still ongoing and is reaching the point when I will have to start to migrate V3 codebase into it. Even for me, it is unknown how much time it will take me to achieve that migration because V3 has code that I haven't touched in years.
As some may know, I'm a one-man-army developer, and I ship my code soon as is shippable. Not a surprise that I'm slow, but that's because I'm doing way more than just coding like, for example, actually running the business or its software support (bugs). Don't get me wrong, I love to learn new stuff and push myself to the limit but I still have just two hands and, I don't have the manpower that others have.
Here, check how my GitHub activity changed when I made my development public (March 8):
I will like to take the opportunity to thank @tomsit for helping me out with the forum and the Discord server. From December to March I was in a cave re-factoring the framework and the help that I got by not having to worry that much about support was like day and night for my development goals.
Questions welcome
I assume that there could be questions related to how to understand the framework code, its documentation, which template system is going to use, how it runs middleware, which components I'm using or why I'm not using a certain component, etc.
Feel free to ask anything, I will love to know what you want to build with Chevereto, how you want to integrate it with your existing system or what kind of customization you want to achieve.
Note: In some post "Chevere" is named as "Chevereto\Core". Is the same thing and "Chevere" is the current name.
Spoiler alert: I don't have any dates yet, but I want to show you the work in progress.
Update 2019-09-19
You can follow the work in progress in the Chevere + Chevere V4 Trello board. I'm showcasing the new stuff and confirming the new system features.
Chevere Framework
The framework behind Chevereto 4 is Chevere. I've been working in this framework since May 2018, and a few weeks ago I started to publish its work-in-progress at GitHub.
Most of you won't have to mind about this framework thing at all, but for developers is a huge step forward which should bring more ease for development purposes.
Modernized
Chevere uses tools like composer, phpstan, scrutinizer and phpdoc. The code follows the PSR-12 formatting standard, it embraces strong typing and strict types. It includes console commands and works so neat that most of my development process is now "server-less". I can't recommend highly enough how great it feels to work with PHP like that. Here is what looks like:
At this time I've commands for forge a HTTP request, inspect and run callables. Later I will add cache, dump and other most-wanted developer tools.
APIs built with Chevereto\Core use the json:api standard and are self-exposed: The API communicates what it does and how you have to use it. No documentation needed, no manual routing.
Current development state and release dates
The framework development is still ongoing and is reaching the point when I will have to start to migrate V3 codebase into it. Even for me, it is unknown how much time it will take me to achieve that migration because V3 has code that I haven't touched in years.
As some may know, I'm a one-man-army developer, and I ship my code soon as is shippable. Not a surprise that I'm slow, but that's because I'm doing way more than just coding like, for example, actually running the business or its software support (bugs). Don't get me wrong, I love to learn new stuff and push myself to the limit but I still have just two hands and, I don't have the manpower that others have.
Here, check how my GitHub activity changed when I made my development public (March 8):
I will like to take the opportunity to thank @tomsit for helping me out with the forum and the Discord server. From December to March I was in a cave re-factoring the framework and the help that I got by not having to worry that much about support was like day and night for my development goals.
Questions welcome
I assume that there could be questions related to how to understand the framework code, its documentation, which template system is going to use, how it runs middleware, which components I'm using or why I'm not using a certain component, etc.
Feel free to ask anything, I will love to know what you want to build with Chevereto, how you want to integrate it with your existing system or what kind of customization you want to achieve.
Note: In some post "Chevere" is named as "Chevereto\Core". Is the same thing and "Chevere" is the current name.