Re: [Babeldoc-devel] Babeldoc is (going to be) going through changes!

[Dejan K. <dej...@nb...>]

I even thing this code could be generalized so it can be used not only with
pipeline stages but with scanners, etc.
We could have one common interface that would be implemented by components
like pipeline stages, scanner workers. I did started working on
this by creating IConfigurable iterface but have never finished it. Anyway,
as a first step we can make this pipeline specific. Later we can
decouple this code from pipeline stages and move it to some more general
class....

Dejan

----- Original Message -----
From: "Ken Geis" <kg...@sp...>
To: "Babeldoc Developer List" <bab...@li...>
Sent: Monday, June 09, 2003 9:57 AM
Subject: Re: [Babeldoc-devel] Babeldoc is (going to be) going through
changes!


> Dejan Krsmanovic wrote:
> > I agree that we need better control over configuration parameters. We
> > already have meta info object for each pipeline stage, so we just should
use
> > it!
>
> This is a better way to address the problems than I have in recent
> commits.  If the factories checked the configuration, the code I wrote
> to check options would not be necessary, and the metadata fixes I made
> would have been caught sooner.
>
> We may have to remove some code if we make this change!  ;)
>
>
> Ken
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel