On Tue, 28 Dec 2010, Carsten Haitzler (The Rasterman) wrote:
> On Tue, 28 Dec 2010 09:59:54 +0100 (CET) Vincent Torri <vto...@univ-evry.fr> > said: > >>> that leads to #1. as such developers do hate having to fire up OO to >>> document things. but as such the things they document are in text anyway - >>> in the source in javadoc. what i want to know is.. how will these api docs >>> and such a larger "efl collective" doc work together? do we perhaps want a >>> way to be able to import the output of doxygen into such a document nicely? >>> if so.. what about links? doxygen does generate nice linked documentation >>> where you just mention api_call() and it's a link to the docs for that call >>> immediately. >> >> doxygen can export xml output. So with some xsl scripts, we can do almost >> what we want. I already did some stuff about that: >> >> http://trac.enlightenment.org/e/browser/trunk/DOCS/api/ecrin?rev=44200 >> >> Vincent > > oh indeed. i know doxy output xml - i was thinking that... but "then what?". > how would/could we combine/merge such a thing with OO odt (also xml based.. > tho > not that that is a lot of use here as we'd need to add formatting and all > sorts > of other "odt" inherent information i suspect. well, with an xsl script, you can transform the xml output of doxygen to a valid odt file, no ? Vincent ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
