I don't think all the relevant options are on the editor or I wouldn't have searched the session and renderer for anything.

If the API gets cleaned up I suggest adding an object called `ui` or something similar which would have properties and methods mapped to it which should show up on menus for end users. That would simplify everything. If something is meant to be user configurable at runtime it could expose itself on the `ui` object in a manner which is consumable by templating systems. Then webmasters could grab the `ui` object and connect it to their jQuery, ext, or whatever. Not having to filter out properties, methods, and options that are meant for developers would help out a great deal because honestly, users aren't that interested in a command line interface for the text editor on the web. They want to drag, drop, and click stuff to reduce keystrokes and get things done super fast. For things that can't be done with the mouse they want keyboard shortcuts, again so they don't have to use a command line interface. :D