Hi Luca,<br><br>This is excellent news!<br><br>Some thoughts:<br>1. The extended tooltips should not be dependent upon internet connection. (they should work offline too)<br><br>2. The automatically generated GUI description should include the location of the control (expressed like a path).<br>
This will allow a reader to read the wiki like a book.<br><br>***<br><br>Your proposal mentions an important approach: <b>"Let's design the Manual as a book"</b><br>I didn't see any targets in that direction (at least for this phase of your effort.).<br>
<br>To me, it means being able to export an OFFLINE version of this book, for end-users and contributors.<br><br>The use-cases could be as follows:<br>1. Allow the user to export the wiki as pdf (print-on demand). <br> This is for the end-users who are cut off from internet for most of the day (or cannot afford the bill).<br>
<br>2. Also allow "Export to odt".<br> This is mainly for contributors who want to edit the book to create their own flavors and share it.<br> (If you see the various published books on Blender, they differ in presentation; not core facts.<br>
So it is good if the platform allows authors to make use of the reference material and author their own books.)<br> <br> Blender foundation should make it clear whether commercial books can be produced using this content.<br>
Or ask commercial authors to contact BF to fix the revenue-sharing formula on a case-to-case basis. <br><br>3. While exporting to pdf/odt, auto-format the pages properly (e.g. how to fit large images); <br><br>4. Convert the links in the exported pdf/odt file to refer within the pdf book.<br>
<br>Regards,<br>Narayan<br>