I'm a simple-minded guy. The way I see it, we have data that we are interested in, and we have ways that we want to view that data. My (current) proposal is just to allow a user to specify what data they care to record. Initially, this will be a global specification, but I will probably try to localize it later (or sooner).
> Yes, I'm proposing to have the current viewers so that they no longer do > logging (I can't understand the reason to mix these two different > functionalities). Currently, we don't have Viewers in our documentation or on our "Add" menu. We have Listeners. Most, if not all of the current Listeners (viewers) have multiple personalities - they listen to data, record data, display data, and load data. This might not be how I would have designed them, but it doesn't bother me too much. Listeners listen to data. After that, they can do whatever they want. Each Listener needs to be able to deal with the data in its own way. At some point, I may choose to write a Listener that is a CSV Writer. This CSV Writer may listen to data and record data, but not display or load data. Is this bad? I don't think so. I'll rely on something else to view my data, a database perhaps. > Then, have one Logger component which does the logging, and put all > these configuration parameters in the GUI for those Logger components. In my way of thinking, this would be just another Listener, let's call it a ReallyVerboseDataSaverUsingXML. It's just another tool in the toolbox. > In this way, you could define loggers with different configurations for > different branches of the tree. I like the idea of being able to configure each Listener separately. But I'm not tackling that just yet. > There's one difficulty to this approach I'm proposing: to get the > functionality you have now, you'd need to find a way to load the results > back so that you can view them in your Viewers. But I'm guessing your > proposal breaks this functionality too... As far as I am concerned, a Listener does with its data what it will. If it wants to be a viewer of stored data, it can be. Should all Listeners be able to use every other Listeners stored data? I think not. Currently, they all happen to share the same (XML) format, but I don't think we should insist on that. > I'd propose to work on creating that Logger component first. Then we > could think on how to solve the save/load test results problem (if we > think we need to solve it -- I've never used that capability anyway). I > guess the best option is to have each viewer save its digested (not raw) > data in some XML format. If I understand you correctly, one could conceptualize your "Logger" component as a superclass of our current Listeners. These Listeners write data as XML and load that XML data. They can be inserted in various places in the component tree. Your Logger would just be a variation of the Listener that does not allow viewing of the data. I like your idea and think that we should implement it, but I don't think that we need to rewrite the existing Listeners. > Salut, > > Jordi. Thanks for your ideas. Keith --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
