|
From: Dejan K. <dej...@nb...> - 2003-02-25 15:29:52
|
What about having one xml file for configuration stuff for all aspects of Babeldoc? So instead of many properties file in many folders we could have one large xml file with all configuration. Just like in ant's build xml. What should be changes? I guess we should have new class for that implements IConfigService or extends ConfigService class, right? The problem is probably with some module specific functionality. For examples scanner is separeted module from core. Anyway, I would like to have scanner configuration in the same file as other stuff. But what if one day we create some new cool stuff like scanners are? Then we should change shema for xml configuration file and that is not good. Maybe we could handle this by introducing some kind of plugin api for scanners and other possible extrensions to core babeldoc. Or we could just leave scanner configuration out of the core babeldoc config. Any toughts?! Best regards, Dejan |