Re: Documentation hard time

[Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>]

Le 15/10/2025 à 14:38, Fabien Bodard a écrit :
> Le mer. 15 oct. 2025 à 13:52, Benoît Minisini <benoit.minisini@gambas- 
> basic.org <mailto:benoit.minisini@xxxxxxxxxxxxxxxx>> a écrit :
>
>     Le 15/10/2025 à 11:31, Fabien Bodard a écrit :
>      > Hi,
>      > One of my biggest problems with gambas was creating the
>     documentation.
>      > But I just played around with Gemini by providing it with source
>     code
>      > and letting it do the documentation... it's amazing.
>      >
>      > https://gitlab.com/gambix/gb.gbx.data <https://gitlab.com/gambix/
>     gb.gbx.data> <https://gitlab.com/gambix/ <https://gitlab.com/gambix/>
>      > gb.gbx.data>
>      >
>      > The Markdown file is generated directly in standard Markdown format.
>      >
>      > I use collections to pass parameters, and even that, it managed to
>      > document it for me :-).
>      >
>      > I saved a lot of time there.
>      > --
>      > Fabien Bodard
>
>     As soon as you verify everything, rewrite the expressions that do not
>     use the right computer-related vocabulary, remove the useless text that
>     is sometimes generated, the documentation generated by AI shit may be
>     usable.
>
>     What is generated from Gemini exactly in the 'README.md' file?
>
>
> all :-)
>
> Yes, I still need to verify everything. But with a good prompt many 
> errors can be avoided
> Sometimes gemini confuse things between different close langage. So I 
> need to prevent it by beginning "with the Gambas Syntax you can found at 
> http://gambaswiki.org <http://gambaswiki.org>"
>
> In the case of RichTable the IA forgot also some Keys (collection 
> parameters) so I need to tell it about this missing... and it 
> automatically does the job.
>
> It also misses the fact about the button entry that can take or just a 
> name for the icon from stock or a full path for an internal icon.

And it talks about a TableView class that is not present in the source 
code...

It's still always the same shit: you save time in generating something 
that is not a documentation actually, but something that looks like it.

You should better write a real documentation in French, and just use it 
for translating it into English.

Regards,

--
Benoît Minisini.