You are not logged in.
I’d like to share an interesting AI-generated podcast (created using Google’s NotebookLM) that summarizes the **mORMot 1.18 SAD document**. You can listen to it here:
https://notebooklm.google.com/notebook/ … c8f9/audio
I found it really helpful as a beginner-friendly introduction before diving into the full document. NotebookLM also does a great job answering questions about the content—think of it as a handy complement to tools like DeepWiki!
Happy learning!
Last edited by zen010101 (2025-05-10 10:52:13)
Offline
Lol
Perhaps worth generating a mORMot 2 pdf, to meet the AI beast.
yes! I did a try last month with Gemini, to generate a full project based on mormot2. I packed almost the whole mormot source and test folder with repomix, added some custom corrections I was used to and thrown a prompt of 900,000 tokens to Gemini. It has ended with a project of multiple REST servers, all the interfaces and services implementations and an openapi definition file.
I then could generate the whole JsonClient and DTOs with mormot tool. I just had to make some minors corrections - impressed as f**.
Offline
yes! I did a try last month with Gemini, to generate a full project based on mormot2. I packed almost the whole mormot source and test folder with repomix, added some custom corrections I was used to and thrown a prompt of 900,000 tokens to Gemini. It has ended with a project of multiple REST servers, all the interfaces and services implementations and an openapi definition file.
I then could generate the whole JsonClient and DTOs with mormot tool.
Sounds truly inspiring.
Could you elaborate on what's included in your "900,000 tokens" and which motmot tool you used to generate the JsonClient and DTOs? Also, when packaging with repomix, did you include the implementation parts of all unit files? (I always thought AI finds that part useless.)
Offline
Hi @zen, yes I can - let me create a repo for that.
did you include the implementation parts of all unit files? (I always thought AI finds that part useless.)
Yes because of two things. The first is that the frameworks is complex and I know models are subject to hallucinations while working with mormot; For example you can get GPT working on v2 only after corrections and sending to the models samples.
The second, I had the sentiment that Gemini had a lot of power, and with 1 million of tokens context (like GPT 4.1 now) I tested to throw the full source code. And it worked like a charm
And as the tests are written by @ab and show the right way of implementing things, then I through it was the best idea to pack the tests. FYI, packing the WHOLE framework don't work as you will get too much tokens, like 2 or 3 millions - so you must choose the best parts based on what you are trying to achieve.
Last edited by flydev (Today 07:44:09)
Offline
I posted a small readme there, sorry I had to do it fast as I am at work, feel free to ask.
Offline
I posted a small readme there, sorry I had to do it fast as I am at work, feel free to ask.
Thanks a lot! I was really troubled by GPT's hallucination issues and the fact that the mORMot framework is too large. Thanks to your guidance, I finally understand the right direction.
Also, sorry to bother you while you're working. Please go ahead with your tasks :-) I need to digest the information you've shared as it's a brand new area for me. :-)
Offline
My pleasure
I forgot to talk about the tool. To get the mopenapi tool, just compile it from there src/tools/mopenapi (blog post) and then you will be able to get a JsonClient and DTOs defintions in a second and ready to work with your API, then just throw the DTOs code on Gemini if you want them on your interfaces or whatever.
To get the JSON file from YAML, just use any YAML <> JSON converter - I will send a PR to handle YAML on mopenapi tool directly if ab accept it
Last edited by flydev (Today 08:52:04)
Offline
My pleasure
I forgot to talk about the tool. To get the mopenapi tool, just compile it from there src/tools/mopenapi (blog post) and then you will be able to get a JsonClient and DTOs defintions in a second and ready to work with your API, then just throw the DTOs code on Gemini if you want them on your interfaces or whatever.
To get the JSON file from YAML, just use any YAML <> JSON converter - I will send a PR to handle YAML on mopenapi tool directly if ab accept it
1. Regarding "the tool": Understood, thanks for the heads up.
2. As for your PR, it's another handy addition to the mORMot "arsenal"
Offline