152649 - Modularize editor code: factor out type-specific code from generic code

Status: VERIFIED INVALID

(Core :: DOM: Editor, defect)

Description

[Håkan Waara]

We need to factor out specific htmleditor code from the `generic' editor code.
That way, it will be much easier to just plug in new formats, if we have generic
code that doesn't know about the format, and that interacts with the format
through a generic architecture.

This is the tracking bug to track this work, as it will probably involve big
changes.

Comment 1

[Håkan Waara]

Before this can start, there needs to be a consensus of exactly how a "plug-in",
or a format should interact with the generic editor structure. Can anyone fill
me in here, or is it up for discussion? Right now the plaintext format and html
format is so tightly integrated that at least *I* cannot see a simple way for a
new format - say XUL - to be hooked up.

Comment 2

[Akkana Peck]

Mike Judge has been working on something to do with editor embedding interfaces
-- perhaps he or Saari can point us to the documentation or an example of how
the editor should be initialized in the new world.

Comment 3

[Kathleen :Brade]

This sounds like a core issue and not Composer-specific

Comment 4

[kinmoz]

--> jfrancis

Comment 5

[Joe Francis]

We already have this modularization.  It's called nsEditor.  That's where the
base functionality lives.  html-specific is in nsHTMLEditor.

Comment 6

[sujay]

verified.

Comment 7

[SathyaRam]

(In reply to Håkan Waara from comment #0)

We need to factor out specific htmleditor code from the `generic' editor
code.
That way, it will be much easier to just plug in new formats, if we have
generic
code that doesn't know about the format, and that interacts with the format
through a generic architecture.

This is the tracking bug to track this work, as it will probably involve big
changes.