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

VERIFIED INVALID

Status

()

Core
Editor
VERIFIED INVALID
16 years ago
15 years ago

People

(Reporter: Håkan Waara, Assigned: Joe Francis)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
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.
(Reporter)

Comment 1

16 years ago
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

16 years ago
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.

Updated

16 years ago
Hardware: PC → All

Comment 3

16 years ago
This sounds like a core issue and not Composer-specific
Assignee: syd → kin
Component: Editor: Composer → Editor: Core

Updated

16 years ago
Assignee: kin → jfrancis

Comment 4

16 years ago
--> jfrancis
(Assignee)

Comment 5

15 years ago
We already have this modularization.  It's called nsEditor.  That's where the
base functionality lives.  html-specific is in nsHTMLEditor.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID

Comment 6

15 years ago
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.