Oct 8 2020
Lots and lots of documentation missing...
Mar 23 2020
Dec 21 2019
Aug 30 2019
That looks wonderfull.
Jul 25 2019
OK, I think I got everything right. Please take a look at:
https://enlightenment.github.io/www-content/gh-pages/api/csharp/api
Jul 24 2019
Some public elements, unfortunately, are also for internal use only, and can be completely hidden from docs.
You probably have a track of those already. I would list:
- IWrapper and implementations of its properties NativeHandle and NativeClass, (both in EoWrapper and generated code),
- internal NativeMethods classes and their public method GetEoOps (both in EoWrapper and generated code).
Apparently, from protected elements only the constructor protected EoWrapper(ConstructingHandle ch) could be of interest to the user, and consequently the struct ConstructingHandle.
Every other protected element can be hidden.
There is also a generated version of this constructor for each class, like protected <ClassName>(ConstructingHandle ch).
OK, @lauromoura @vitor.sousa I am doing a (hopefully) last cleanup of internal classes and fields from the docs (via blacklist).
Jun 26 2019
Well, making these constructors private would mean that we would have to add empty default constructors above in the inheritance tree, and these constructors wold have to be visible somehow. So, the current protected constructors with the remark of being only for internal use seems to be enough.
Jun 19 2019
May 1 2019
Apr 23 2019
Apr 18 2019
After D8550, Concrete classes constructors are private and regular classes intptrs constructors are protected.
Apr 17 2019
Apr 15 2019
After playing a bit with grep I found:
- 974 unique ingroups
- 484 unique defgroups
- 501 ingroups without matching defgroup (Full list here P284)
Apr 4 2019
Awesome, thanks, I updated the list in the task description. This task is almost done!
Right now these classes are hidden from DocFX via blacklist: 8fc4e948778f
Apr 1 2019
Resolved in D8470
Mar 17 2019
Mar 15 2019
- _StructConversion classes: Do they need to be public?
I'll create a task for it.
Thanks!
Mar 14 2019
- _StructConversion classes: Do they need to be public?
Mar 4 2019
@felipealmeida @lauromoura I updated the task description with a list of issues. Can you please comment on each of them so we can decide if they can be made private or internal, or I need to blacklist them in the doc generation?
Feb 22 2019
Yes, there are a lot of these. @lauromoura and @felipealmeida were already looking at making these classes private or internal so they don't show up in the docs, right?