It turns out Zope has a method to use an external editor, triggered from the web. It requires a helper app on the client because browsers don't have this built in. It seems to have problems with Netscape Composer, though.
http://www.zope.org/Members/Caseman/ExternalEditor --John Boris Zbarsky wrote: > fantasai wrote: > >> Are you saying that FTP and <textarea> form inputs present for these >> others >> a higher barrier to entry than CVS? > > > As someone who once had to extensively use Zope for development of a > Zope-based web interface, I must say that this statement is precisely > true. Briefly: > > 1) The FTP interface is clunky and much harder to use than CVS since > you have to keep cd-ing to the right directory. > 2) Attempting to circumvent this by keeping the FTP connection open as > you edit so you can periodically checkpoint your document fail > because Zope is very agressive about closing the FTP connection. > 3) Typing anything longer than about 5 lines of text in a <textarea> > and keeping track of what's going on is quite difficult. Editing an > existing document, as opposed to creating a new one is well-nigh > impossible. If I were to use <textarea>s to edit documentation, I > would need to basically copy all the text in the <textarea> to a > real editor, edit, copy it back, then submit. And hope that all > that works without losing data (by no means guaranteed, in my > experience with <textarea>s). Note that once I am at the "edit it > in my text editor" point, checking it into CVS requires pressing 2 > keys, entering a checkin comment for the changelog, and pressing a > third key. This is much, much simpler and less error-prone than the > <textarea> approach. >
