microsoft / microsoft/microsoft-ui-xaml
Proposal: Request more RichEditBox capabilities to support a complex text editor
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.4k
- Forks
- 942
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 105
Description
Goal: To develop a complete text editor application(like "word" or "note")
In wpf, we are used to use RichTextBox with FlowDocument for height customisation.
But in uwp and winui3, it is split into RichEditBox and RichTextBlock.
RichTextBlock can display full custom content, but can't be edited.
RichEditBox can be edited, but can't display full custom content. (or hard)
"Full customisation" = "Regular text style" + InlineUIContainer +...
RichEditBox richEditBox = new RichEditBox();
richEditBox.Document.Selection.InsertImage(); //only image
RichTextBlock richTextBlock = new RichTextBlock();
Paragraph paragraph = new Paragraph();
InlineUIContainer inlineUIContainer = new InlineUIContainer();
paragraph.Inlines.Add(inlineUIContainer);
richTextBlock.Blocks.Add(paragraph);
In addition to this, wpf's flow document supports full xaml writing. And winui3 doesn't support it.
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.
Research direction
Start by reviewing the RichEditBox and RichTextBlock APIs and the sample code in the issue, focusing on the requested custom content and XAML-writing capabilities. Done requires defining a concrete, implementable scope for the proposed RichEditBox improvements rather than only comparing WPF, UWP, and WinUI 3 behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100