From editor/ui to mozilla/editor
By Kazé on Wednesday, July 27 2011, 11:50 - Permalink
Finally! After a one year contract with INRIA working on SMIL Timesheets I’m getting back to what I’ve been doing as a Mozilla community member: working on the wysiwyg HTML editor.
The difference is, with Kompozer I’ve been dealing with the XUL/JS front-end (editor/ui), trying to find workarounds to the bugs in the core editor, whereas now I’m working on the C++ back-end (mozilla/editor), trying to fix bugs at the source. As the HTML editor component is used in Firefox (contentEditable elements), Thunderbird, SeaMonkey and Kompozer, I hope my work on this back-end will improve the user experience on all these apps.
The other difference is that instead of working on the editor on my free time, I have an official contract now. Yay!
I’ve just spent a week in Toronto working with Ehsan, who got me started with the editor codebase and the development tools. I’ve already addressed a couple bugs and I’ll do my best to make the editor better for everyone in the next few months.
Comments
It's great for editor. Congratulations!
So happy to see that, congrats!
Also, could you and ehsan please convince our dev tools people that it's better to get our in-house editor to work as they like instead of importing a whole chunk of third-party Orion editor code into Firefox? ;-)
And maybe similar convincing on the Thunderbird side?
Robert > I completely agree with you on this, but I guess the editor is in such a bad shape at the moment that we’d better solve the most irritating bugs first. I’m still worried about the situation of editor/ui, though.
As for the built-in code editor to come, note that Orion has been preferred to Ace precisely because Orion relies on our editor (contentEditable) and Ace does not.
I am a faithful user of Kompozer. I have noticed it seems to have lost steam with no updates in more than a year. Has the focus shifted to another development? Where should my focus be to get the latest Kopozer-like HTML editor?