Follow up on past Editor API review meeting from 1/30

We'll cover as many of the APIs listed below as possible on Thursday the 20th
starting at 1:00pm, Pacific time. If you're in Mountain View, we'll be in the
Ironsides (B21-1) conference room. Dial in info:

Local: 703-265-4200
Toll free: (866) 477-9620

Scheduled Meeting ID: 3333

--disclaimer--
The list is a simple enumeration of the APIs that we know are being
used by some of our clients. It does not intend to imply that freezing
of that API is the motivation, but rather that we need to understand why
its use was necessary and whether other interfaces exist now/should be
created to handle the needs, where necessary.
--disclaimer--

If you're on the 'to' list of this mail, your attendance is requested
(though anyone is always welcome). Handouts will not be provided, so if
you're not familiar w/ the interfaces being discussed, please bring your
own printout via printing the idl links below. The living notes document
for the API Review is available at
http://www.mozilla.org/projects/embedding/apiReviewNotes.html

Agenda:
nsISelectionDisplay (Mike Judge)
-
http://lxr.mozilla.org/seamonkey/source/content/base/public/nsISelectionDisplay.idl

nsISelectionController (Mike Judge)
-
http://lxr.mozilla.org/seamonkey/source/content/base/public/nsISelectionController.idl

nsIEditingSession <http://www.mozilla.org/projects/embedding/apiReviewNotes.html#nsIEditingSession> (Mike Judge/Simon Fraser)
-
http://lxr.mozilla.org/seamonkey/source/editor/composer/public/nsIEditingSession.idl

nsICommandManager <http://www.mozilla.org/projects/embedding/apiReviewNotes.html#nsICommandManager> (Mike Judge/Simon Fraser)
-
http://lxr.mozilla.org/seamonkey/source/embedding/components/commandhandler/public/nsICommandManager.idl

nsICommandParams <http://www.mozilla.org/projects/embedding/apiReviewNotes.html#nsICommandParams> (Mike Judge/Simon Fraser)
-
http://lxr.mozilla.org/seamonkey/source/embedding/components/commandhandler/public/nsICommandParams.idl

nsIEditor, nsIHTMLEditor, nsIPlaintextEditor usage alternatives.


Reply via email to