On Tue, 22 Feb 2011 20:13:19 +0100 Yassin frechdes...@gmail.com said:
Hello,
what about this manual,please?
nothng much has happened. basically it's hard to do a good manual as long as
all the documentation is in the .c files of libs - ie we have to trawl all
sources to get doxygen info out
Hello,
what about this manual,please?
On 17/12/2010 18:11, Kim Lester wrote:
All,
A few notes and two requests (marked *** )
1)
Attached is a 0th order draft of a proposed EFL manual to replace all the
other manuals.
Or more accurately here is a half written manual to replace the
On Tue, 28 Dec 2010 12:44:06 +0100 Lionel Orry lionel.o...@gmail.com said:
On Tue, Dec 28, 2010 at 11:03 AM, Carsten Haitzler ras...@rasterman.com
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
On Tue, 28 Dec 2010, Carsten Haitzler (The Rasterman) wrote:
On Mon, 20 Dec 2010 22:19:23 +0100 Lionel Orry lionel.o...@gmail.com said:
Hmmm... ok - time to chime in.
1. i'm kind of worried how any such efl manual and doxygen docs will work
together. as such doxy is pretty much the
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
On Mon, 20 Dec 2010 22:19:23 +0100 Lionel Orry lionel.o...@gmail.com said:
Hmmm... ok - time to chime in.
1. i'm kind of worried how any such efl manual and doxygen docs will work
together. as such doxy is pretty much the best/only way to document an API (we
dont use it for documenting the code
On Fri, Dec 17, 2010 at 22:13, Lionel Orry lionel.o...@gmail.com wrote:
Kim Lester kim at dfusion.com.au writes:
All,
A few notes and two requests (marked *** )
[...]
Incidentally I wrote this in OO simply because writing either doxygen or xml
is not a good way to evolve a
large complex
On Mon, Dec 20, 2010 at 2:16 PM, Thomas Gstädtner tho...@gstaedtner.net wrote:
On Fri, Dec 17, 2010 at 22:13, Lionel Orry lionel.o...@gmail.com wrote:
Kim Lester kim at dfusion.com.au writes:
All,
A few notes and two requests (marked *** )
[...]
Incidentally I wrote this in OO simply
On Sat, 18 Dec 2010 04:11:28 +1100
Kim Lester k...@dfusion.com.au wrote:
All,
A few notes and two requests (marked *** )
1)
Attached is a 0th order draft of a proposed EFL manual to replace all the
other manuals. Or more accurately here is a half written manual to replace
the other half
Kim Lester kim at dfusion.com.au writes:
All,
A few notes and two requests (marked *** )
[...]
Incidentally I wrote this in OO simply because writing either doxygen or xml
is not a good way to evolve a
large complex document. I've written large docs in TeX with vi before and
whilst
héhé that's cool
2010/12/17 Lionel Orry lionel.o...@gmail.com
Kim Lester kim at dfusion.com.au writes:
All,
A few notes and two requests (marked *** )
[...]
Incidentally I wrote this in OO simply because writing either doxygen or
xml
is not a good way to evolve a
large
11 matches
Mail list logo
