GNOME Bugzilla – Bug 522153
Evolution 2.24 New Composer Tracker
Last modified: 2013-09-13 01:00:56 UTC
This bug tracks Phase 1 of my composer rewrite for Evolution 2.24. See [1] for more details. I believe the new GtkHTML editor component is far enough along to be included in trunk for Evolution 2.23.1. Evolution integration is progressing, and I hope to have it ready as well in time for 2.23.1 or 2.23.2. Details: - The primary goal of the composer rewrite is to eliminate GtkHTML's dependence on libbonobo and libbonoboui by providing an HTML editor in the form of a GtkWindow rather than a BonoboComponent. - Although Phase 1 is a /complete rewrite/ of the HTML editor, the new editor should look and behave like the old editor as much as possible. Ideally, users should not notice any difference. - The new editor eliminates GtkHTML's dependence on GnomeSpell (another BonoboComponent), opting instead to interface directly with libenchant with help from iso-codes for translated language names. It implements GnomeSpell's spell checking UI natively. - The new editor's menus and toolbars can be extended using GtkUIManager. This is critical for Evolution's mail composer. - The new editor can be installed in parallel with the current Bonobo-based editor. - A new "--with-bonobo-editor" configure option determines whether to build the older Bonobo-based editor. For now it defaults to "yes". Once the Evolution integration is complete and committed to trunk, I plan to change the default to "no". (Evolution is the only known consumer of GtkHTML's editor component.) [1] http://www.go-evolution.org/New_Composer
Created attachment 107199 [details] [review] Merge of revision 8785 This 16K-line patch is a merge of revision 8785 from my "mbarnes-composer" branch into Subversion trunk. It's just here to attract peer review. I'm still tweaking and testing this code. To try out the latest revision: 1. Check out the "mbarnes-composer" branch of the gtkhtml Subversion repo. 2. Build as usual. 3. Run the "gtkhtml-editor-test" program under components/editor.
Matt, I dont think we can review this :). At the max, we can have a test. I would say that complete everything, and post a mail with what you have done and just commit for 2.23.1, so that it gets tested adequately. So, Im rejecting your patch ;-)
That's fine. I just meant for the bug to track merging the branch for 2.23.1. I'm mostly done with Evolution integration -- just testing and bugfixing now and trying to use the new composer for in my daily work. I think I'll hold off until I'm satisfied with it, then merge both GtkHTML and Evolution branches at once and post an announcement. I'll let you know when I'm ready to merge. Hopefully next week.
Srini gave his approval for merging the Evolution and GtkHTML branches to trunk once I'm satisfied with my own testing. Also filed bug #525241 about the plugin breakage this will cause. Rescoping this bug to track phases 1 and 2 of the composer rewrite.
Branches are now merged and an announcement was sent to evolution-list and evolution-hackers. I'll use this bug to track regressions and other stuff I want to fix for 2.24.
Closing this since the new composer seems pretty stable now. There's a few outstanding issues here but I don't need a tracker bug for them.