Well, it's not even just about workspace, we had in kde4 times kdeedu, kdegames, etc. etc. all on api.kde.org. Not all of it was api per se (I don't know anyone that would want to read the apidocs for kanagram for example, except to know how it's internals work or used to work when hacking on it). Currently we only show frameworks and other. This misses a lot of useful documentation, nothing is there about libkomparediff2, libkeduvocdocument, libkdegames, etc. since those aren't generated anymore for some reason.
A good idea that Ben suggested when the gardening project started was having the apidocs generate on commit, rather than regenerating everything every night at a specified time. A lot of the sources don't actually change very often, so rebuilding part of the apidocs when the code or it's doxygen comments change would make a lot of sense. BR, Jeremy On Thu, Sep 10, 2015 at 11:05 AM, Adriaan de Groot <gr...@kde.org> wrote: > On Thursday 10 September 2015 06:07:40 Jeremy Whiting wrote: >> It would be awesome to have what used to be in KDE SC on api.kde.org >> again. We have many libraries that aren't frameworks that are Qt5/KF5 >> based which would be good to show on there imo. > > Perhaps half of this is figuring out what actually constitutes the "Workspace > API" that would be interesting here and how to subsequently pull information > out of the metadata-services that we have (src-build? projects.kde.org? I > don't know, I haven't followed very closely what lives where now). > > > > [ade] (who is now reminded that the original ebn domain is expiring and needs > renewal, yeah) _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel