Can you describe the specific lay out requirements and why they are as they are, aside from the namespace?

Sent from my mobile. Please forgive shortness, typos and weird autocorrects.


-------- Original Message --------
Subject: [sword-devel] About PreferredCSSXHTML
From: Tuomas Airaksinen
To: SWORD Developers' Collaboration Forum
CC:


Hi,

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.

Current draft of how And Bible implements this, can be read here:

How are other frontends implementing PreferredCSSXHTML? 
Is there something similar implemented elsewhere too, as what I am doing? 
Are there any modules using this configuration key in Crosswire or other public repositories? 
Any other thoughts related to my approach?

Best regards,
Tuomas
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Reply via email to