A couple of things that initially spring to mind:
1. If the XML data stores the titles and text of the tips, how will they
be localised?
2. Why use XML? You could use YAML or JSON, two formats that are
infinitely more human-readable and human-writable than XML, and easier
to parse to boot. And if the tips won't be updated outside of the
add-on code itself, you could just store the tips in a localised,
separate Python module, in a dict or similar.
Don't make it any more complicated than it needs to be. Focus on
implementing your idea in a way which works, and then
optomising/refactoring it later. For instance, when will the tips be
shown? Generally, they appear at application startup, but many NVDA
users will leave the program running 24/7. Considerations like this
are, IMO, far more important than creating an XML-based schema for data
which can't be used yet.
--
James Scholes
http://twitter.com/JamesScholes
----------------------------------------------------------------
NVDA add-ons: A list to discuss add-on code enhancements and for reporting
bugs.
Community addons are available from: http://addons.nvda-project.org
To send a message to the list: nvda-addons@xxxxxxxxxxxxx
To change your list settings/unsubscribe:
//www.freelists.org/list/nvda-addons
To contact list moderators: nvda-addons-moderators@xxxxxxxxxxxxx
