|
From: Bruce M. <br...@mc...> - 2003-06-07 22:05:14
|
All, With all the work on the GUI that I have been doing (review the latest cvs snapshot with the command: "babeldoc pipelinebuilder" and go ahead and create a few pipelines) I am going to have to change the configuration of pipelines. This will roll to the scanner too, but lets get the pipelines working nicely. At the moment we have this IConfigOptions object for each pipeline stage. This (should) provide information about the configuration of the pipeline stage. I want to tie the actual configuration data to this object so that we can enforce things like isMandatory and isValid on the actual configuration values. This will mean that the pipeline factory can actually check that the configuration is good before running the pipeline. This should mean that running a system will get easier. So to recap - the underlying configuration of the pipelines from the PipelineStageResolver code to the PipelineStage code will be changing. No more nested Maps nonsense - the data will be structured. Lets talk about how this will affect you. At the moment I do not see that the actual pipelinestage code will change - its just that the implementation will change. Email the list for questions / concerns. regards, Bruce. |