https://bugs.kde.org/show_bug.cgi?id=86423
--- Comment #170 from John A. Sullivan III <jsullivan opensourcedevel com> 2010-09-05 03:58:25 --- On Tue, 2010-08-31 at 08:12 +0200, Tin Blaskovic wrote: > https://bugs.kde.org/show_bug.cgi?id=86423 > <snip> Sorry to take so long to get back to this. Several of you have emailed me privately as requested to pledge toward the bounty. Here is where we stand. Tim is subscribing to the bug so he can respond directly. I'm not sure if he has done that yet. Tim has suggested that we finalize the spec before starting to collect pledges in case something in the spec has a significant impact on the bounty. He has set up a page to record the spec as well as the pledges at http://trinity.pearsoncomputing.net/ - click on Requests for Enhancement. Speaking of impacting the bounty, Tim's environment is specifically KDE3 as Trinity is a maintained fork of KDE3. He does not have a KDE4 build environment and building one just for this project would add significantly to the cost. Does anyone have a KDE4 build environment that could be used for this project? Regarding forward usability, Tim proposed the following design which, in my programming ignorance, would seem to facilitate forward compatibility: "My initial thought was to create a widget that accepts HTML input from the parent program, allows the user to edit the HTML/insert images/etc., then outputs the edited HTML to the parent program. It would probably also have to pass some (QImage?) pointers to any inline image files via a QPtrList or similar to the parent program. This should ensure that the KMail changes needed are trivial, with most of the code contained within the new editor widget. I was planning to include some doxygen commenting in the external API of the new widget" Once the spec is finalized, we can use Chipin to collect the pledges. Thanks - John -- 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 Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs