- From: Michael Sokolov <sokolov@ifactory.com>
- Date: Mon, 12 Oct 2009 17:01:56 -0400
- To: "'Florent Georges'" <fgeorges@fgeorges.org>, "'XProc Dev'" <xproc-dev@w3.org>
I agree - spent a little while trying to integrate Calabash into our processing framework by doing just what Florent is proposing. I got sidetracked before any useful result, but count this as another vote for modularizing the runtime API so it can be invoked as a library module. On the other hand, if you're lazy enough, you might get a patch from him (or me), though - you never know :) -Mike > -----Original Message----- > From: xproc-dev-request@w3.org > [mailto:xproc-dev-request@w3.org] On Behalf Of Florent Georges > Sent: Sunday, October 11, 2009 4:49 PM > To: XProc Dev > Subject: Calabash: main driver extensibility > > Hi, > > It seems the main Calabash's driver for the command line > suffers the same problem than Saxon's drivers: it is not > really extensible through derivation, because the whole > processing is done in one single, monolithic method. > > It would be nice to have Main.run() cut down into smaller > pieces, so one could extend the class and plug his own > processing by overriding the existing methods. At very > least, it would be nice to be able to deal with the > XProcRuntime object right after its creation. Something like > replacing the following line at the middle of the file: > > runtime = new XProcRuntime(config); > > by: > > runtime = makeRuntime(config); > > and adding the following protected method: > > /** > * Create a new runtime object from a configuration object. > * > * Override this method if you want to set the runtime object up > * in any particular way. > */ > protected XProcRuntime makeRuntime(XProcConfiguration conf) > throws XProcException > { > return new XProcRuntime(conf); > } > > Regards, > > -- > Florent Georges > http://www.fgeorges.org/ > >
Received on Monday, 12 October 2009 21:02:28 UTC