I've just committed the first public code for Nexus Development Framework.
You can find it on GitHub: https://github.com/jfilby/nexus
You can write console apps, web apps and web-services with this framework. It's major strength is the ORM where you define models in YAML and then get generated SQL (create code only) and Nim code (data access and object types). The ORM is PostgreSQL only right now, but it shouldn't be too hard too add other DBs, especially since the Nim standard libs for PostgreSQL/MySQL/SQLite are quite similar.
The view part of Nexus still needs a lot of work. Right now it's mainly plain Jester routes and whatever HTML rendering library you want to use. I want to simplify how routes are created, probably via a YAML-based generator in the same way the ORM works.
I still plan on adding:
So take a look if you're interested in the idea. More improvements will follow soon.
There's an example repo available now: https://github.com/jfilby/online_store_example
This still needs some work, but it should help get you started. It covers the basics of setting up an app.
Heyho, as somebody currently writing a medium-sized webapplication in prologue there was one feature I would have absolutely loved to have since it removes so much work: Generic REST API Endpoints. Think Django-REST-Framework Viewsets (https://www.django-rest-framework.org/api-guide/viewsets/). Since you have an ORM do you plan on having something similar?
If yes, I'd be super interested in your approach to the problem! I had to build that exact thing myself and I'm always curious on how to solve this sort of problem better. My approach was having a set of builder-procs that take in procs for the sub jobs (such as fetching an entry by id, checking if the user has permission for the requested action, updating the entry in the database, serializing the entry into json etc.), and then provide generic procs for the standard stuff (Such as reading an entry from the DB with its id).