Does anyone have any suggestions?
I would have to know a good bit more about the details to know whether
this is better or not, or simply different, but here is at least one
different way to approach it. It does sound like an odd way of using
XMLReader.
I would consider using just an XMLDocument to load the prefs and store
that somewhere and "notify" the various prefs classes that it is loaded
and ready and they can use some XPath queries to extract the nodes that
they care about.
When i have done an app with a dense enough prefs structure to merit a
bit of extra effort like this, I have created a little
Broadcaster/Listener model where any class that cared could register
itself to be notified any time prefs change (whether it be by the user
during the app running, or just the first time they are loaded off
disk). In my case they simply turn around and re-query the global prefs
XML document for their nodes and away they go.
Again, not knowing the details, I have no idea whether this would be
applicable in your case. But there it is nonetheless! ;-)
-stephen
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
