We're in the midst of revising the editor directory structure.
This is a heads-up to let people know our plans for the new structure.
Current thought is that the editor directory will look like this:
editor
|
+-----------------------------------------------+
| | | |
libeditor composer txtsvc txmgr
| |
| +--------+ (unchanged) (unchanged)
| | |
| ui src
|
|
+------------------------------------------+
| | | |
base text html build
| \ | \ | \
src public src public src public
Builds inside libeditor will be typical of other mozilla directories
-- you have to build the subdirectory where you've modified files to
generate a static library, then build in the "build" directory to
combine all the static libs into one dynamic lib. That's the
disadvantage.
The advantage is: better modularity, so that it will be easier
to keep plaintext-only functions separate from html functions,
or build a plaintext-only library, the whole editor, or both,
and to keep functions needed for the composer app separate from
functions needed for embedded editors.
IDL and .h files which currently live in editor/public will move
to appropriate subdirectories, e.g. editor/libeditor/text/public.
The tree currently under editor/ui moves to composer/ui, on the
theory that UI is all composer specific and doesn't apply to
the editor. (Is this true -- none of the editor javascript
is used in text controls or embedded editors?)
Text Services and the Transaction Manager are already self-contained,
so they remain unchanged.
I hope we'll be able to do this by moving files on the CVS server,
rather than creating new files and losing all the existing CVS history
(and, incidentally, making me the owner of every file in the editor. :-)
Comments, problems, suggestions?
...Akkana
