My bad. In the generated API documentation, there is a page on the
connection library, but it is generated under "Related Pages". Further
documentation can be found under "File List" -> "Ecore_Con.h".
BTW, in case you don't know how to build the API docs for Ecore:
1. Do a normal build, i.e. ".
Can someone please apply my three week old ecore docs patch??
Regards,
Nicholas
---
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top techni
This is really a mixed bag of stuff for the Ecore docs. Mainly, docs
have been added to the Ecore_Con sources and some Ecore_X sources.
The Ecore_Con page needs more work though.
Patch:
http://home.bigblue.net.au/quasar/ecore-18-06-2004.diff
New examples to go with patch:
http://home.bigblue.net
Here is some more doc work, with some other things:
- All Ecore_Config functions have docs. Still work to do on them
though, still refinements to make.
- Changes to documentation for Ecore_Jobs, Ecore_X and functions
involving the Ecore_List abstract data type. Mainly cleaning up
syntax,
I noticed that some help with documentation is needed, so I started
poking around the documentation generation code in Ecore. I have been
able to make doxygen generate a proper file list for the Ecore
documentation. Instead of attributing all functions to the file
ecore.c, functions can now be at
Patch to add some examples and modules to the documentation. Or rather,
add specific sections for the two. Most examples pulled from
pre-existing documentation, but made to work on their own.
Also removes all tags that were giving warnings. Fixes up some doxygen
syntax.
This is not at all comp
Docs for Ecore_Config. If I've deduced/done anything wrong, tell me and
I'll fix it.
Note that things that are going to be removed from the user's API soon
have (e.g. Ecore_Config_Server) may not have been docced, or may have
not had their original docs changed.
Regards,
Nicholas
ecore-config-
I wish to make the following contributions:
- The Doxygen syntax in some files in src/libs/ecore in the Ecore module
was wrong. The result was that the generated documentation for some
functions (esp. ecore_path_group_*, ecore_plugin_* and ecore_sheap_*)
looked weird. The patch should fi
I noticed that some help with documentation is needed, so I started
poking around the documentation generation code in Ecore. I have been
able to make doxygen generate a proper file list for the Ecore
documentation. Instead of attributing all functions to the file
ecore.c, functions can now be at
