we should also figure out how to integrate the doxygen docs and the dokuwiki, because having two separate systems is just bad...

currently i have two possibilities in mind

1. parse doxygen comment thingys ourselves and generate dokuwiki pages out of it, similarly to how eo docs are generated... this is somewhat difficult as it needs reimplementation of doxygen markup/commands as well as basic parsing of C and integrate that with the dokuwiki docs by doing some kind of reverse-lookup from C name to Eo stuff (could be done by adding reverse-lookup APIs to libeolian...), the need to parse Doxygen markup could possibly be alleviated by transitioning our Doxygen-style docs to Markdown, which Doxygen supports since some versions ago - then an existing Markdown parser could be used...

2. use doxygen to process existing docs into XML output (doxygen has that) and parse the XML output and do the same reverse lookups to match things accordingly...

We'll also need to figure out how to properly integrate our Eo docs with C docs so that the UX is good and it's intuitive. That's a whole separate problem and will also need to be addressed...

@q66, I fully agree with you. I am leaning toward 2. strongly and created a subtask separately: T6126 .

This task is mostly to fill time when waiting for answer on other topics. So in priority order what need to be looked at is :

src/lib/eo/efl*.eo
src/lib/efl/interfaces/efl*.eo
src/lib/ecore/efl*.eo
src/lib/evas/canvas/efl*.eo
src/lib/ecore_con/efl*.eo
src/lib/edje/efl*.eo
src/lib/elementary/efl*.eo

With an exception for everything related to *model* and *view* at the moment.