Hey again, My mind is racing ;)
I'm thinking if we're about to build all sorts of config UI for the aliases, preferences, etc, shouldn't we change the file format altogether? It'll be a lot easier to work against the files programmatically if they are XML-based. The only loss I see is that there's a segment of users who have no problem editing text files, but don't recognize XML. They will be forced to use the UI. For the aliases it should be simple, but for prefs I'm not sure if it's possible - at least not without changing a lot. I think it'll be much easier to persist prefs if we work through the XML DOM, but then not as straight-forward to use them (now it's just a matter of variable access). I'm thinking maybe we should build some component support for preferences, so we can query and save them through a unified API. I'm just throwing out ideas here -- let me know what you think. - Kim ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel
