https://bugs.kde.org/show_bug.cgi?id=86423
--- Comment #124 from Jason Keirstead <jason keirstead org> 2009-12-12 22:52:17 --- (In reply to comment #110) > Also, the composer wouldn't use the WebKit editor, that is too much work. > Instead if would use QTextEdit, which means same HTML format preserving as > Mailody has, nothing fancy. Porting the whole composer to a WebKit editor > would really be much work. ... I have to disgaree with this approach. Like I said in many comments, QTextEdit is just *FAR* too limited to offer proper HTML support. I mean, we are talking about a widget that is basically almost 10 years old here, it has hardly changed since QT 3.0, how can it possibly be expected to compete with the editors of Thunderbird and Outlook, which use modern web browser rendering engines? The idea that it is "too much work" to move to Webkit for editing, is solely because of the horrible API design of the KMail composer - no other reason. I know this because I have tried to do this port myself. The Komposer API is a huge mess, none of it is properly abstracted - this is why it is nearly impossible to move outside of QTextEdit. The editor widget should have absolutely no knowledge or care about the widget that is being used for the editing. Spending any amount of time further working on adding features using the QTextEdit engine as a base, is a complete waste of effort IMO. If it was made a priority to do, Komposer could be re-done from scratch in a month or two, I have absolutely no doubt. It is really *NOT* that difficult a component to make - heck you can implement these Webkit based composers IN JAVASCRIPT in a couple of hours of work! Heck I could (and probably would) do it myself, if I thought my change would be approved and checked into SVN. But for some reason everyone on the KMail team is stuck in the past and insisting on QTextEdit instead of Webkit. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
