For larger packages the doc generated "Index" section is most unhelpful.
See for example, the Go FLTK bindings.
There are two separate ways this could be improved:
-
For types with methods, show, e.g., "▶ type BmpImage" with no methods, unless the user clicks the triangle in which case it becomes "▼ type BmpImage" with all the methods shown (as now).
-
When there are more than some threshold number of functions (or methods) — say 7, where the first word is the same (e.g., func Draw(), func DrawArc(...), ..., func DrawYxLine3(...)), use the same technique as decribed above in 1.
These changes would make navigation much easier.
For larger packages the doc generated "Index" section is most unhelpful.
See for example, the Go FLTK bindings.
There are two separate ways this could be improved:
For types with methods, show, e.g., "
▶type BmpImage" with no methods, unless the user clicks the triangle in which case it becomes "▼ type BmpImage" with all the methods shown (as now).When there are more than some threshold number of functions (or methods) — say 7, where the first word is the same (e.g., func Draw(), func DrawArc(...), ..., func DrawYxLine3(...)), use the same technique as decribed above in 1.
These changes would make navigation much easier.