[jsword-devel] How to check for GlobalOptionFilter=OSISStrongs in .conf file

[Peter von Kaehne]

Thanks, Troy, I guess it did make sense at the time - and still does, somewhat.

'Past tense'/'somewhat' for 4 reasons: 

1) The development has not been sustained - many other similarly desirable features did not get their own "feature" tag. I would suggest at the least: xrefs, morphology as further features which could get usefully their own tag in bibles, "devotional' vs 'expository' in commentaries etc.

2) We have moved so decisively towards OSIS in Bibles that the "filter come, filter go, features stay" theory is probably becoming irrelevant.

3) It is essentially undocumented

4) I think most frontends apart from BibleCS do not use a universal feature on/off toggle, but use individual toggles for individual modules. So, the "user switches on Strongs, programme jumps to next module which has strongs" can not happen outside of BibleCS (AFAIK)

I guess to make it reliably useful in the sense you described we need some info re intention and difference to GlobalOptionFilter in the wiki and probably in the source. We need to fix the module Martin found. And, we should think which other features would benefit similarly from such a filter independent marker.

Peter


-------- Original-Nachricht --------
> Datum: Thu, 09 Jun 2011 00:26:21 +0100
> Von: "scribe777 at gmail.com" <scribe at crosswire.org>
> An: JSword Developers Mailing List <jsword-devel at crosswire.org>
> Betreff: Re: [jsword-devel]	How to check for GlobalOptionFilter=OSISStrongs	in	.conf file

> The purpose for features was not to enumerate every attribute about a
> module; as you suggest, there are a million attributes a module can have which
> usually is evident by some combination of filters.
> 
> Features are intended to note that a modules can supply some generally
> desirable feature: "I need a strongs greek definition," "I need to a Bible
> with strongs numbers," "I need a daily devotional," (I think devo is a
> feature) etc. These all came out of use cases over time: I need to let my user
> pick their preferred strongs greek dictionary, the user turned on strongs
> numbers so I'd like to jump to a Bible which actually has strongs numbers, etc.
> 
> Hope this gives a better explaination for the purpose and some background.
> 
> Troy
> -- 
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
> 
> Peter von Kaehne <refdoc at gmx.net> wrote:
> 
> > Von: "scribe777 at gmail.com" <scribe at crosswire.org>
> 
> > I believe this is a bug in the module. If the text provides a Strong's
> > marked translation, then feature should be set. The filter list to
> handle
> > these things can grow, shrink, be renamed, whatever.
> 
> I believe you. But it somehow makes no sense - there is a million items
> long list of features modules can have and yet only images and strongs got
> their own "feature" tag. The other "features" change the way the module as a
> whole is interpreted, rather than toggling something.
> 
> Peter 
> 
> -- 
> NEU: FreePhone - kostenlos mobil telefonieren!			
> Jetzt informieren: http://www.gmx.net/de/go/freephone
> 
> _____________________________________________
> 
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel
> 

-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de