mirror of
https://gitlab.freedesktop.org/emersion/libdisplay-info.git
synced 2024-11-16 19:48:30 +01:00
readme: add Using section
I believe this is what we intended, and it is what I want. It could lead to duplicating low-level API in high-level API at first, but once we start seeing DisplayID in the wild, the high-level functions need to start looking into both EDID and DisplayID APIs to deliver the desired information. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
This commit is contained in:
parent
6d7ce6dbd8
commit
cda99a0913
1 changed files with 13 additions and 0 deletions
13
README.md
13
README.md
|
@ -11,6 +11,19 @@ Goals:
|
|||
|
||||
Documentation is available on the [website].
|
||||
|
||||
## Using
|
||||
|
||||
The public API headers are categorised as either high-level or low-level API
|
||||
as per the comments in the header files. Users of libdisplay-info should prefer
|
||||
high-level API over low-level API when possible.
|
||||
|
||||
If high-level API lacks needed features, please propose additions to the
|
||||
high-level API upstream before using low-level API to get what you need.
|
||||
If the additions are rejected, you are welcome to use the low-level API.
|
||||
|
||||
This policy is aimed to propagate best practises when interpreting EDID
|
||||
and DisplayID information which can often be cryptic or even inconsistent.
|
||||
|
||||
## Contributing
|
||||
|
||||
Open issues and merge requests on the [GitLab project].
|
||||
|
|
Loading…
Reference in a new issue