Feature Request/Question: QTextCursor and QTextDocumentFragment
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
No file or test is named. Start by locating the existing QTextEdit bindings and related Qt type wrappers, then determine how QTextCursor and QTextDocumentFragment should be exposed. Done means both types are available and QTextEdit methods returning them work through NodeGui.
Written by the indexing model from the issue text.
Description
Currently there are no implementations of QTextCursor and of QTextDocumentFragment. Both types are super helpful when working with `QTextEdit and would be a great addition to nodegui.
Question: Should this be a plugin? Not so sure since QTextEdit API does expose methods returning these useful types, they're just not exposed at the moment.
- Dominant language
- C++
- Stars
- 9.2k
- Forks
- 315
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from nodegui/nodegui
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Support QTransform Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
Similar issues
-
Website Doc Typo Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
autowarefoundation/autoware_universe#13413 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
automated-analysis bug memory-safety
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100