External Editor question
I was able to get External Editor working on a Solaris box and W2K Client. I used Python-2.2.1.exe, win32all-148.exe, and zopeedit-win32-0.5.exe on W2K client. I only had to add an editor path to the ZopeEdit.ini to get it to work on the client (Product already installed on ZServer) Works great with one (1) editor path but how do I get it to differentiate from a text editor (or html editor) and an image editor? Read your doc's and it should have worked because file types are already config'ed. # C:\ZopeExternalEditor\ZopeEdit.ini # Zope External Editor helper application configuration [general] # General configuration options # Uncomment and specify an editor value to override the editor # specified by the operating system # editor = "C:\Program Files\TextPad 4\TextPad.exe" # editor = "C:\Program Files\Adobe\Photoshop 7.0\Photoshop.exe" "%1" editor = "C:\Program Files\Macromedia\Dreamweaver UltraDev 4\UltraDev.exe" "%1" # Automatic save interval, in seconds. Set to zero for # no auto save (save to Zope only on exit). save_interval = 0 # Temporary file cleanup. Set to false for debugging or # to waste disk space. Note: setting this to false is a # security risk to the zope server cleanup_files = 1 # Use WebDAV locking to prevent concurrent editing by # different users. Disable for single user use or for # better performance use_locks = 1 # To suppress warnings about borrowing locks on objects # locked by you before you began editing you can # set this flag. This is useful for applications that # use server-side locking, like CMFStaging always_borrow_locks = 0 # Specific settings by content-type or meta-type. Specific # settings override general options above. Content-type settings # override meta-type settings for the same option. [meta-type:DTML Document] extension=.dtml [meta-type:DTML Method] extension=.dtml [meta-type:Script (Python)] extension=.py [meta-type:Page Template] extension=.pt [meta-type:Z SQL Method] extension=.sql [content-type:text/*] extension=.txt [content-type:text/html] extension=.html [content-type:text/xml] extension=.xml [content-type:image/gif] extension=.gif [content-type:image/jpeg] extension=.jpg [content-type:image/png] extension=.png
On Thursday 12 September 2002 12:52 pm, eric.n.dunn@bankofamerica.com wrote:
I was able to get External Editor working on a Solaris box and W2K Client. I used Python-2.2.1.exe, win32all-148.exe, and zopeedit-win32-0.5.exe on W2K client.
Actually the zopeedit-win32-0.5.exe binary already contains Python and win32all.
I only had to add an editor path to the ZopeEdit.ini to get it to work on the client (Product already installed on ZServer)
Works great with one (1) editor path but how do I get it to differentiate from a text editor (or html editor) and an image editor?
[content-type:text/html] editor = <path to dreamweaver> [content-type:text/*] editor = <path to general text editor> [content-type:image/*] editor = <path to iamge editor> etc, etc
Read your doc's and it should have worked because file types are already config'ed.
Yes, but the general editor setting overrides the os setting. Try omitting the general editor setting entirely and just put dreamweaver under the text/html content type and DTML meta types (assuming you want to use dreamweaver to edit dtml): [content-type:text/html] extension = .html editor = <path to dreamweaver> [meta-type:DTML Method] extension = .html editor = <path to dreamweaver> [meta-type:DTML Document] extension = .html editor = <path to dreamweaver> If your other editors are already configured through Windows, then you probably don't need to add anything else to your config file. hth, -Casey
participants (2)
-
Casey Duncan -
eric.n.dunn@bankofamerica.com