Matthew, Well that's going to be the case anyway. Each SWORD (or JSword) front-end application would need to implement a media player for playing the ancillary resource when the user wishes.
The total amount of work may turn out to be less, especially if the OSIS files do not have to be changed for the modules. Ancillary resources can then be developed independently, and added as and when they become ready to release. Moreover, if the ancillary resources are kept separate from the main module that they are designed for, then part of the challenge is also pushed to module/resource management. Example: The ancillary audio files for MK (xulsword) can be installed optionally (even by drag'n'drop). I'm just trying to promote discussion on the way forward, given the fact that we have a programmer friend who has already successfully integrated using linked audio files. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Linked-in-audio-files-tp2336755p2340231.html Sent from the SWORD Dev mailing list archive at Nabble.com. _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
