Re: [Evolution-hackers] WebKit based Evolution composer status and future
On Mon, 2014-06-09 at 16:57 +0200, Tomas Popela wrote: Hi, the WebKit based composer was commited into master with [0]. Awesome! Congrats on landing that - that's a pretty major feature and I'll start testing it immediately. Also I have to say I'm thrilled to finally see GtkHTML die for good! Matt ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] WebKit based Evolution composer status and future
Hi, the WebKit based composer was commited into master with [0]. Tomas [0] - https://git.gnome.org/browse/evolution/commit/?id=8650fb139a9143f04615de74ff569bce3e0c4ce3 On Po, 2014-03-17 at 09:25 +0100, Tomas Popela wrote: Hi Evolution hackers, as some of you probably know, I'm continuing with work on new Evolution composer based on WebKit (WebKit1) and I want to share with you the current status and the future of new composer. Right now, the composer takes place in wip/webkit-composer branch in Evolution git repository [0]. For compiling it you need just the evolution-data-server from master. What the composer really needs right now is testing. It needs a lots of testing. The currently opened bugs against WebKit based composer can be found in [1]. If you will open a new bug against new composer (and I really hope you will) please prefix its summary with [webkit-composer]. In the time of creation of this mail (03/16/2014) the new composer lacks the support for Undo and Redo and broken plain text part in multipart/alternative when sending HTML mail (working on this right now). These are the major issues that we know about and if there are more issues I really hope that you will help me hunting them. One tip for spotting bugs, if you will see red star somewhere in composer and you will be able to reproduce process to show it in the composer please report it as something went wrong during save and restore of the caret position. Regarding the future of WebKit based Evolution composer I'm proposing this: merge webkit-composer branch into master when the 3.12 release will be branched and continue to work on it in master branch. This will hopefully bring more testers for the new composer. When the code will be in master I will continue to develop it and also porting it to WebKit2 with the rest of Evolution. Thank you Tom [0] - https://git.gnome.org/browse/evolution/log/?h=wip/webkit-composer [1] - http://ur1.ca/gvb12 ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] WebKit based Evolution composer status and future
Hi everyone, after talk with Milan we decided to merge webkit-composer branch into master on Monday, June 9, 2014. Best regards Tomas On Po, 2014-03-17 at 09:25 +0100, Tomas Popela wrote: Hi Evolution hackers, as some of you probably know, I'm continuing with work on new Evolution composer based on WebKit (WebKit1) and I want to share with you the current status and the future of new composer. Right now, the composer takes place in wip/webkit-composer branch in Evolution git repository [0]. For compiling it you need just the evolution-data-server from master. What the composer really needs right now is testing. It needs a lots of testing. The currently opened bugs against WebKit based composer can be found in [1]. If you will open a new bug against new composer (and I really hope you will) please prefix its summary with [webkit-composer]. In the time of creation of this mail (03/16/2014) the new composer lacks the support for Undo and Redo and broken plain text part in multipart/alternative when sending HTML mail (working on this right now). These are the major issues that we know about and if there are more issues I really hope that you will help me hunting them. One tip for spotting bugs, if you will see red star somewhere in composer and you will be able to reproduce process to show it in the composer please report it as something went wrong during save and restore of the caret position. Regarding the future of WebKit based Evolution composer I'm proposing this: merge webkit-composer branch into master when the 3.12 release will be branched and continue to work on it in master branch. This will hopefully bring more testers for the new composer. When the code will be in master I will continue to develop it and also porting it to WebKit2 with the rest of Evolution. Thank you Tom [0] - https://git.gnome.org/browse/evolution/log/?h=wip/webkit-composer [1] - http://ur1.ca/gvb12 ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] WebKit based Evolution composer status and future
On May 30, 2014 9:28 AM, Tomas Popela tpop...@redhat.com wrote: Hi everyone, after talk with Milan we decided to merge webkit-composer branch into master on Monday, June 9, 2014. Great news! Thanks guys for all the work you've been doing! I'll compile it first thing on Monday :) ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] WebKit based Evolution composer status and future
On Fri, 2014-05-30 at 08:28 +0200, Tomas Popela wrote: Hi everyone, after talk with Milan we decided to merge webkit-composer branch into master on Monday, June 9, 2014. Woo Hooo! I guess it is time to remember how to build Evo. On Po, 2014-03-17 at 09:25 +0100, Tomas Popela wrote: What the composer really needs right now is testing. It needs a lots of testing. The currently opened bugs against WebKit based composer can be found in [1]. If you will open a new bug against new composer (and I really hope you will) please prefix its summary with [webkit-composer]. [0] - https://git.gnome.org/browse/evolution/log/?h=wip/webkit-composer [1] - http://ur1.ca/gvb12 -- Adam Tauno Williams mailto:awill...@whitemice.org GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] WebKit based Evolution composer status and future
On Tue, 2014-05-20 at 16:34 +0400, Emre Erenoglu wrote: ping... Hi, do not be afraid, it is not forgotten, there was only involved some other work which interrupted the webkit-composer work. It's mostly over now and the expected development version with the webkit composer branch merged is 3.13.4. I'm sorry for the delay. Bye, Milan ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] WebKit based Evolution composer status and future
On Tue, May 20, 2014 at 6:27 PM, Milan Crha mc...@redhat.com wrote: On Tue, 2014-05-20 at 16:34 +0400, Emre Erenoglu wrote: ping... Hi, do not be afraid, it is not forgotten, there was only involved some other work which interrupted the webkit-composer work. It's mostly over now and the expected development version with the webkit composer branch merged is 3.13.4. I'm sorry for the delay. Thanks Milan for the info. I got impatient and started to compile the master hoping that the webkit-composer branch is merged. I did not see any commits to the webkit-composer branch from Tomas since April 24th, but saw some from him to the master. So I thought it's already merged :) thanks for the info, Emre ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] WebKit based Evolution composer status and future
On Tue, Mar 18, 2014 at 12:21 AM, Matthew Barnes mbar...@redhat.com wrote: The next release following 3.12 will happen in March, 2015. So we have an entire year to stabilize the WebKit composer. Also the HTML library that the composer is currently based on has been dead several years now, and I personally would like to wash my hands of it as soon as possible. I haven't tested the branch in awhile, but I've seen numerous recent bug reports from Milan and Tomas seems pretty responsive in fixing them. As long as that continues after merging, and we have a handle on the major remaining regressions, I think it's a reasonable risk to finish the work directly on the master branch. Dear Tomas Matthew, I see that Evolution 3.12 has been released. Any news on merging the webkit-composer to the master? I checked today but it seems it's not there yet. Sorry for my impatience ;) Thanks, -- Emre ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] WebKit based Evolution composer status and future
On Mon, Mar 17, 2014 at 12:25 PM, Tomas Popela tpop...@redhat.com wrote: Hi Evolution hackers, as some of you probably know, I'm continuing with work on new Evolution composer based on WebKit (WebKit1) and I want to share with you the current status and the future of new composer. Hi Tomas, first of all, I would like to personally thank you for your efforts on webkit-composer. What the composer really needs right now is testing. It needs a lots of testing. The currently opened bugs against WebKit based composer can be found in [1]. If you will open a new bug against new composer (and I really hope you will) please prefix its summary with [webkit-composer]. In the time of creation of this mail (03/16/2014) the new composer lacks the support for Undo and Redo and broken plain text part in multipart/alternative when sending HTML mail (working on this right now). These are the major issues that we know about and if there are more issues I really hope that you will help me hunting them. One tip for spotting bugs, if you will see red star somewhere in composer and you will be able to reproduce process to show it in the composer please report it as something went wrong during save and restore of the caret position. I think it's in a very usable state except some annoyances which I have already filed as bug report. I'm a bit busy with family and work travel these days so could not get to more bug finding. I'll be back to daily use and bug reporting asap. Regarding the future of WebKit based Evolution composer I'm proposing this: merge webkit-composer branch into master when the 3.12 release will be branched and continue to work on it in master branch. If this is merged to master after 3.12, it would be great! Br, Emre ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] WebKit based Evolution composer status and future
On Mon, 2014-03-17 at 20:05 +0100, Patrick Ohly wrote: While I have no say in how Evolution gets developed, I nonetheless would like to warn against merging unstable and known buggy code into master. What if it turns out that the code can't be stabilized in time for the next release? Can it be reverted or will Evolution have to go out with known regressions? The next release following 3.12 will happen in March, 2015. So we have an entire year to stabilize the WebKit composer. Also the HTML library that the composer is currently based on has been dead several years now, and I personally would like to wash my hands of it as soon as possible. I haven't tested the branch in awhile, but I've seen numerous recent bug reports from Milan and Tomas seems pretty responsive in fixing them. As long as that continues after merging, and we have a handle on the major remaining regressions, I think it's a reasonable risk to finish the work directly on the master branch. If things still haven't stabilized by... let's say this year's GUADEC... then we can start discussing a contingency plan for Evolution 3.14. Matt ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
