- From: Wendell Piez <wapiez@mulberrytech.com>
- Date: Fri, 16 Apr 2010 11:36:08 -0400
- To: xproc-dev@w3.org
Jim, At 11:18 AM 4/16/2010, James Fuller wrote: >p:log should help > >http://www.w3.org/TR/xproc/#p.log Yes, thanks, and I was also pointed (off-list) to the very interesting thread at http://markmail.org/thread/a4vmdkmbagah4ydf#query:+page:1+mid:gajyfhhx5pcnftbi+state:results. In particular, and partly since I'm using oXygen (with its excellent support for allowing me to see stuff without writing it to disk), I'm intrigued by Geert's suggestion in this thread that simply declaring extra ports does the job: I expect that will be so for me. In that case (lightbulb moment), I can simply use two different oXygen scenarios on the same pipeline: one that shows me intermediate results, another that doesn't. (And if I really want, a third can serialize things.) This is interesting stuff. I guess it makes sense that when designing in XProc, the features of the calling environment bear largely on the tradeoffs in the available approaches. Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
Received on Friday, 16 April 2010 15:36:56 UTC