This page shows an evaluation of the documentation of splattael/libnotify.
Each class, module, method, etc. is given a grade based on how complete the docs are.
The bar above shows the distribution of these grades.
Seems really good | ||
---|---|---|
A
|
Libnotify::API#show! | |
A
|
Libnotify | |
A
|
Libnotify::API | |
A
|
Libnotify::FFI | |
A
|
Libnotify.new | |
Show 6 more ... | ||
A
|
Libnotify::API.icon_dirs= | |
A
|
Libnotify::API.icon_dirs | |
A
|
Libnotify::API#close | |
A
|
Libnotify::API.show | |
A
|
Libnotify.show | |
A
|
Libnotify::API#icon_path= |
Proper documentation present | ||
---|---|---|
B
|
Libnotify::API#update | |
B
|
Libnotify::API#initialize |
Needs work | ||
---|---|---|
C
|
Libnotify::API#timeout= |
Undocumented | ||
---|---|---|
U
|
Libnotify::FFI.attach_functions! | |
U
|
Libnotify::FFI#method_missing | |
U
|
Libnotify::IconFinder::Icon#initialize | |
U
|
Libnotify::IconFinder::Icon#resolution | |
U
|
Libnotify::IconFinder::Icon#fullpath | |
Show 20 more ... | ||
U
|
Libnotify::IconFinder::Icon#to_s | |
U
|
Libnotify::IconFinder#initialize | |
U
|
Libnotify::IconFinder::Icon#<=> | |
U
|
Libnotify::IconFinder#icon_path | |
U
|
Libnotify::FFI#lookup_urgency | |
U
|
Libnotify::IconFinder::Icon | |
U
|
Libnotify::API#transient= | |
U
|
Libnotify::FFI.load_libs | |
U
|
Libnotify::API#transient | |
U
|
Libnotify::API#icon_path | |
U
|
Libnotify::API#urgency= | |
U
|
Libnotify::API#summary= | |
U
|
Libnotify::API#summary | |
U
|
Libnotify::API#urgency | |
U
|
Libnotify::API#timeout | |
U
|
Libnotify::API#append= | |
U
|
Libnotify::IconFinder | |
U
|
Libnotify::API#append | |
U
|
Libnotify::API#body= | |
U
|
Libnotify::API#body |
This page is for splattael/libnotify
and is part of a project called "Inch Pages", showing documentation measurements provided by Inch.
Inch Pages also provides a badge:
(not counting low priority objects)
I really think that posting badges for documentation in READMEs will benefit you (because people can see that your project is well documented) and our community in general by improving the visibility of documentation.
Let's start a discussion, let's raise the visibility of documentation, let's talk.
Suggestions, feedback, critique: Hit me up on Twitter or via issue.