Source code for script that produce static web pages can be found on github
In addition, for whom need an easy access to full Krita’s source code documentation (C++ reference), a documentation build with Doxygen is available here: https://srcdoc.krita.maou-maou.fr
@scottyp , if grumm is okay can we do something like officially? This is okay too may be we can share the link. I do not know I am just putting forth ideas
The script that build HTML documentation is published under GPL v3 license, so it can be used officially if needed without asking me permission
I have no idea about licence for produced HTML pages: as they’re built by a script under GPL v3 license, analyzing a code under GPL v3 license, I suppose produced pages are under a GPL v3 compatible license
After I have some change to implement, so I prefer for now to keep my script under my own repository.
Currently for example, the list of classes/methods matches the selected release but the description matches the one from master: ideally, description should match the description from the selected version.
I am ok if we wanted to start a process of thinking about the Python API site. I don’t remember all of the things involved to make Krita - Krita Class Reference work though. I imagine there is something fancy going on with pulling the source code down from Krita to build out this website. The current API site is more than just Krita, so it is probably some KDE wide thing going on…I am not involved with any of that.
What kind of update is it? Should we assume that the just lines of code were changed by some commit, or is it drastic change that Scripter should take into account? Maybe behavior is different.
If you’re on a computer, you should have a tooltip on the icon, but yes it indicates the last version from which something has been modified in code
I can’t tell the nature of change without taking a look on source code, it can be a space that has been added in a comment, the description has been updated, or a complete rewrite of mehod
Also you have to keep in mind the change here only concerns the public Python API.
Behind, there’s call to internal Krita methods: if an internal method called by API has been modified and not the API, you won’t be notified there’s a change within Krita unless this is explicitly indicated in description for example.
My point of view is, if there’s a change that have an impact on existing scripts, it should described within the description of method (it’s what I try to do when update something on API)
If the change have no impact, then it doesn’t really matters.
