3) include into the sorting and display of the list a fall back which shows the origin of duplicate modules. ex: KJC (King James Clarified) KJV (King James with Sword -- from Crosswire) KJV (King James Bible -- from ebible) KJV (King James Bible with maps and corrected crossreferences --from Xiphos) ... This would probably also require a warning screen after selection that version x is going to overwrite and delete from your device version y, unless someone's figured a way to have multiple trees for conf and text files by originating server.
On Fri, Jul 31, 2015 at 8:59 AM, Peter von Kaehne <ref...@gmx.net> wrote: > A user on sword-support asked this for unified module lists once again > and I do think he is right: > > Right now we lists with modules per repository. If you happen to have a > first language only served in Xiphos or IBT (or now hopefully soon the > new eBible repo) you will think on starting an application that there > are no modules available for you. > > The only application which has this solved is And Bible. > > The argument used in previous discussions was that different repos > might use the same module identifier as other repos and clashes can > cause grief. Yes they could. But there are also several good mechanisms > we could use to make this a non-issue. > > 1) Choice of sane defaults > 2) user-pinnable preferences > > re 1) > > a) A simple decent default could be CrossWire has always preference - > unless the user overrules this > b) Another simple default could be that the highest versionnumber > always wins out. > > Suggestions, ideas? > > Peter > > _______________________________________________ > 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 >
_______________________________________________ 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