<html><head></head><body> <div>Front-ends generally ignore config keys that are not documented in our wiki for SWORD based front-ends.</div><div><br></div><div>So the fact that most of the modules in the IBT repository contain keys that work primarily with xulsword doesn’t have any [negative] consequences when these modules are installed to other front-ends. It simply means that the particular features they are intended for are not [yet] <caret></caret>supported.</div><div><br></div><div>FWIW, JSword treats some keys slightly differently than SWORD.</div><div><br></div><div>cf. Some config keys are required at and/or operate at the back-end API level.</div><div><br></div><div>Best regards,</div><div><br></div><div>David</div><div><br></div><div id="protonmail_mobile_signature_block"><div>Sent from ProtonMail Mobile</div></div> <div><br></div><div><br></div>On Thu, Mar 4, 2021 at 07:23, refdoc@gmx.net <<a href="mailto:refdoc@gmx.net" class="">refdoc@gmx.net</a>> wrote:<blockquote class="protonmail_quote" type="cite"> My main thoughts are, unsorted and without conclusion<br><br>1) the conf file is a shared and joint space and we really do not want to introduce per-front-end special values there. <br>2) You have clearly thought deeper about the matter than so far anyone of us as far as I can tell from previous discussions on here. <br>3) As far as I can tell not many (any?) modules make specific use of the facility just yet, so we are at a place where we can still just change tack if need be without creating a compatibility gap. <br>4) users of course might have created their own CSS sheets, seeing the opportunity - and those who did might get hurt if we do something which breaks things. We need to think about that. Though chances are these are very knowledgeable people who probably only need a hint. <br>5) I am wondering if the name spaces can be created dynamically? <br><br>Sent from my mobile. Please forgive shortness, typos and weird autocorrects.<div class="quote" style="line-height: 1.5"><br><br>-------- Original Message --------<br>Subject: [sword-devel] About PreferredCSSXHTML<br>From: Tuomas Airaksinen <br>To: SWORD Developers' Collaboration Forum <br>CC: <br><br><br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>I have implemented support for per-module custom CSS for And Bible (to be in And Bible 3.4, which is planned to be released later this year). I noticed that there's PreferredCSSXHTML config key for this purpose. However, CSS for And Bible need to be formatted in a specific way and plain CSS would mess up things -- I need per-module namespacing because the same WebView instance can show multiple module content simultaneously in some contexts (compare view, multi doc view, my notes, study pads etc). In addition, I also support specifying separate settings for dark night mode. Thus, I ended up, for now, using a custom AndBibleCSS key instead.</div><div><br></div><div>Current draft of how And Bible implements this, can be read here:</div><div><a href="https://github.com/AndBible/and-bible/wiki/Custom-CSS-for-modules-for-And-Bible">https://github.com/AndBible/and-bible/wiki/Custom-CSS-for-modules-for-And-Bible</a><br></div><div><br></div><div>How are other frontends implementing PreferredCSSXHTML? </div><div>Is there something similar implemented elsewhere too, as what I am doing? </div><div>Are there any modules using this configuration key in Crosswire or other public repositories? </div><div>Any other thoughts related to my approach?</div><div><div><br></div>Best regards,<br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Tuomas</div></div></div>
</blockquote></div></blockquote><div><br></div><div><br></div></body></html>