OpenTabletDriver / OpenTabletDriver/opentabletdriver.github.io
Document OTD, USB & OS related findings
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 36
- Forks
- 10
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 9
Description
The Current Status of the Project
I think that we have come from a long way, but we are at a point where the lack of knowledge is the current bottleneck for all parties involved, being normal users, helpers, Contributors, maintainers and even devs themselves.
It's also important as this project won't live forever and therefore it's important to leave a trace of our work that others will be able to make use of to maybe create something greater.
A solution has been proposed
I proposed in the Discord Server that we start documenting every single bit of informations we currently have.
This include the following Domain:
OTD
-
Daemon
- Plugin System
- Output Modes
- Input Handling
- Plugins
- Transformations
- Input Handling
-
UX
- Framework
- Forms
- Dialogs
- Drawables
- Framework
-
Plugins
- Report Parsers
- Auxiliary Report
- Tablet Report Report
- Touch Report
- Others...
- Filters
- Interpolators
- Tools
- Bindings
- Report Parsers
-
Configurations
USB
-
Interfaces
- Endpoints
- HID Report Descriptors
- Collections
-
Top Level Collection
- Vendor
-
Non-Vendor
- PNP
- HVAN
- Sublevel Collections
-
Top Level Collection
- Collections
-
Initialization
- Huion
- Initialization Strings
- XP-Pen
- Output initialization
- Wacom
- Feature initialization
- Huion
-
Involvement of firmwares
OS
-
Windows
-
Device Exclusivity
- WinUSB
- Link to vendor interfaces
-
Kernel Level Drivers
- VMulti
- Broken by Windows Update
- VMulti
-
Windows Ink
- Workspace
- Core
-
-
Linux
- Display Servers
- Wayland
- Xorg
- libinput
- Smoothing
- Inconsistencies between setups
- Kernel level Drivers
- libwacom
- uc_logic
- Udevs
- link to Kernel level Drivers
- Display Servers
-
MacOS (that one is going to be the hardest to deal with)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified. Start by reviewing the listed OTD, USB, Windows, Linux, and macOS topics alongside the existing Jekyll site structure; done means producing an organized, maintainable record of the project's current findings and unknowns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, jekyll, linux, macos
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100