That is basically I am working on processing the api docs in perlmod mode to produce python classes this could also be used for other things as well. I would volunteer for that just need some time because of my tight schedule.
On Wed, Sep 11, 2013 at 10:54 AM, bjoern <bjoern.michael...@canonical.com>wrote: > Hi, > > On Wed, Sep 11, 2013 at 05:04:01PM +0200, Michael Stahl wrote: > > On 09/09/13 10:38, Lionel Elie Mamane wrote: > > > Actually, it could make sense to document the API available in each > > > version, that is, have something like: > > > > > > http://api.libreoffice.org/docs/3.3/idl/ > > > http://api.libreoffice.org/docs/3.6/idl/ > > > http://api.libreoffice.org/docs/4.0/idl/ > > > http://api.libreoffice.org/docs/4.1/idl/ > > > http://api.libreoffice.org/docs/4.2/idl/ > > > http://api.libreoffice.org/docs/current/idl/ > > Well, properly packaged versions come with their own api-docs, so IMHO no > need > to keep docs for unsupported releases around. > > > but maybe putting in a link somewhere to the API Changes section of the > > release notes would help? > > Might be a EasyHack, if somebody volunteers as a mentor: Generate XML from > doxygen, diff that and generate some fancy "API changes" report from that. > > Best, > > Bjoern > _______________________________________________ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice >
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
