<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59"> <TITLE>RE: [plt-scheme] Editor Canvas as Output Port</TITLE> </HEAD> <BODY>  Actually, open-output-text-editor was exactly what I was looking to do.  Thanks. -----Original Message----- From: Matthew Flatt [<A HREF="mailto:mflatt@cs.utah.edu">mailto:mflatt@cs.utah.edu</A>] Sent: Sun 4/29/2007 2:30 AM To: Williams, M. Douglas Cc: plt-scheme@list.cs.brown.edu Subject: Re: [plt-scheme] Editor Canvas as Output Port At Sat, 28 Apr 2007 21:27:27 -0700, "Williams, M. Douglas" wrote: > For one thing, it > only works for text, while, for example, DrScheme lets me write graphic > elements (e.g., an image snip) using print (or printf even).  Am I correct in > that I need to supply an optional-write-special-proc to handle these? Probably. DrScheme installs some write and print handlers to make things like `fprintf' work, but adding a write-special handler is a good starting point. > There seem to be similar things in the Application Framework, but I've only > skimmed over them so far.  They seem to be overkill for simple MrEd > applications, but that may well be a learning curve issue more than anything. `open-output-text-editor' is provided by plain MrEd. Matthew </BODY> </HTML>