[Development] Assistant WebKit/WebEngine support
mwoehlke.floss at gmail.com
Mon Jul 8 19:22:43 CEST 2019
On 25/06/2019 17.53, Konrad Rosenbaum wrote:
> Option 2: put some elbow grease into QTextBrowser and make it understand
> some more tags and more CSS.
> Pros: documentation becomes visually more pleasing; minimal dependencies
> by assistant - easy to build and easy to bundle with applications;
> embedding in Creator or KDevelop etc. stays easy to do
> Positive side effect: users will love it, since it becomes much easier
> and flexible to use QTextBrowser in their own applications
> Con: someone actually has to put in the work
Incidentally, does this help rich text rendering *everywhere*? Such as
in tool tips, for example?
More information about the Development