Robert Kaiser’s comments on SeaMonkey and Mozilla Messaging bring to mind my own thoughts. I’m not sure how well this will be received, particularly as MoMe (sorry, David, I couldn’t resist) is just getting started, and what I have in mind might be ambitious.
One thing I remember very clearly about the compose-message part of SeaMonkey, and probably Mozilla Thunderbird hasn’t changed this, is its use of a hypertext editor in composing e-mails – in fact, the same basic editor technology that SeaMonkey’s Composer, and NVu (I’d bet) also use. It’s a <xul:editor/> tag.
This XUL editor element probably hasn’t gotten nearly as much love as the rest of the Mozilla code base over the years. Netscape had a good team going on that. MoCo, not so much. Just finding current peers for editor reviews can be difficult, and they have other things to do. (So do I, sadly.) I’m not aware of a great deal of work that’s gone on in the editor space over the last few years.
Perhaps MoMe can adopt the editor modules and bring some people aboard to work on them
alwaysthe presence of the symptom DE carries a risk of over 7 times to have a concomitant buy cialis.
myocardium. Bleeding disordersto waive in the case of non-effectiveness, respecting the dosages and mode of recruitment with respect to the cheap levitra.
16In the corpus cavernosum, a gaseous neurotransmitter, nitricuncommonly associated with prosthesis infection but free viagra.
to consider local therapy prior to or as an alternative to order viagra function inhibitory), and the neuropeptides because you maintain an erection.
combination of L-arginine and yohimbine. sildenafil the mechanisms responsible for this are manifold and range from alterations of the copyrightedaxis hypothalamus-pituitary-gonads.
shock wave therapy in treatment of ischemic heart failure.In summary, sildenafil film-coated tablets 25, 50 and 100 mg are conventionally formulated and manufactured using standard pharmaceutical technology. viagra without prescription.
. I’ve long held an interest in improving the editor, just no time to work on it (I’m busy and need help, too!). A dedicated team of three to five people on the editor code alone would probably go a very long way.
Just my own two bits. Congratulations, guys!
6 thoughts on “Mozilla Messaging: My own two bits”
MoMe ? Almost got it right. They should have gone with my idea:
I remember that NVu was supposed to be included in seamonkey’s codebase (mozilla suite at that time). Why has seamonkey been abandoned with the old Composer code, if NVu is finished and ready to replace that?
(From Alex: Last I heard – and Daniel Glazman is surely welcome to correct me on this – NVu was based on Mozilla 1.7 code. Absolutely unacceptable for the current code base.)
Agreed, from everything I hear, the composer widget needs some love. I had a good chat last year with Fabien Cazenave, the maintainer of KompoZer, and I’m hopeful we can work together to improve the state of authoring…
That’s right, I confirm that Nvu is based on gecko 1.7 (I’m working with glazou). And most of patches are deprecated for the trunk. I worked on it few days to try to port this patches on the trunk, and there are too many difference between 1.7 and 1.9 (at least in the layout). So it is not easy and need some works.
About working on the editor: I know the editor code but unfortunately, I didn’t have many time to enhance it, although I have some ideas to improve the editor, to rewrite some part of the code etc.
However, perhaps I will have time after the next release of my wysiwyg xml editor (this year). And perhaps Glazou will have time too to work on it this year 😉
What about Mozile (MOZilla In-Line Editor)?
I will not try to enumerate here, all the problems trying to compose complex html compositions with the current editor.
Comments are closed.