From: Carsten Haitzler (The Rasterman) <raster@ra...> - 2004-10-29 01:50:15
On Thu, 28 Oct 2004 15:13:05 -0400 Jeremy West <jkwest@...> babbled:
> I realize you may not need much help, but I would love to volunteer my
> time to help with any documentation you might need done. I'm not sure
> what needs done, so I thought I would ask first.
Well all the libraries need documenting. primarily api docs (every function call
the library offers to applications in its .h file) needs documented as to what
that function does, why, assumptions, conditions, exceptions etc. we don't seem
to be able to write the docs as fast as we write the functions :) basically we
keep the docs in the .c files alongside the code they document, and we document
all "public" functions. the libraries needing this most would be (from bottom to
top) eet (though i think this is fully done EXCEPT for describing the data
format layout of how eet encodes/decodes data structs), evas, ecore, edje as
priorities. then i'd say ewl would be a close second. there are other things
like emotion, esmart, epsilon, even epeg (thats documented though). take your
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) raster@...
Tokyo, Japan (東京 日本)
Get latest updates about Open Source Projects, Conferences and News.