WordPress.org

1. nyoungman
   Member
   Posted 1 year ago #

   Thanks for your work on the Scripturizer plugin. It's working quite well, though the ESV tooltips could use a few tweaks, being fairly new.

   One is to have uniform behavior when the verse references another translation. With my default as NASB, the ESV tooltip comes up still, unless I actually specify NASB on the end of a verse, in which case it doesn't. I think there should be an additional option in administration, to "Show ESV tooltips for other translations".

   Prototype is rather heavy-weight for a simple tooltip, even the significantly smaller jQuery is a little much if it's not being used elsewhere. It would be nice to optimize that. The book "CSS Mastery" has details on how to do styled tooltips without any JavaScript at all. Ask, and I'll post those details.

   Performance is definitely an issue when pulling a large number of requests from the web service. Personally, I think it's better to rely on a page caching layer than add another level of complexity, so it's more of something for the FAQ.

   Thanks a lot, Nathan.

2. petervcook
   Member
   Posted 1 year ago #

   Hi Nathan,

   About the Tool Tip coming up when you use NASB or other translations: You can easily turn off the tool tip in the plug-in options (Settings -> Scripturizer) Look for Rollover Tool Tip. The ESV provides a service that makes it easy to dynamically pull in the verse text. Until a similar service is available for other translations there is not easy way to have the NASB text come up in the tool tip. Because of this limitation it seemed best to give the options to keep tool tips on, even if the author preferred other translations for the links.

   I would be very interested in a way to do the tool tip using only CSS. If you could post the details that would be great.

   Thanks for your feedback!

3. nyoungman
   Member
   Posted 1 year ago #

   Hi Peter,
   Yah, I have the tooltips off right now... I'm fine with displaying them for verses of other translations, but it is inconsistent. They display no matter what the default translation is. But if I specify "2 Timothy 3:15 NASB", then it decides not to display them. I think it always should. Or, have an option to only display them for ESV if some people prefer that behavior.

   For pure CSS tooltips, from page 81-83 of CSS Mastery (I hope this comes through):

   «a href="http://biblegateway.com" class="tooltip"»Genesis 1:1«span» In the beginning... «/span»«/a»

   a.tooltip {
   position: relative;
   }

   a.tooltip span {
   display: none;
   }

   a.tooltip:hover span {
   display: block;
   position: absolute;
   top: 1em;
   left 2em;
   padding: 0.2em 0.6em;
   border: 1px solid #996633;
   background-color: #FFFF66;
   color: #000;
   }

   a.tooltip:hover {
   font-size: 100%; /* Fixes bug in IE5.x/Win */
   }

   It may need a bit of tweaking and browser testing, but you get the idea. Absolute positioning, and display on hover.

   Best, Nathan.

4. petervcook
   Member
   Posted 1 year ago #

   Hi Nathan,

   Here is the reasoning behind the inconsistent behavior as to when tool tips appear or not. At many churches they have a translation that is the church's standard, we'll use NRSV as the example. Equivalent to the "default translation" in Scripturizer. But the ESV tool tips are a nice feature so why not enable them too. Back to our example, most of the time verses are quoted from the NRSV, but there may be occasion where a preacher wants to use the NASB or The Message Paraphrase to emphasize a particular word in that verse. If they are talking about that verse on their blog, and they are specifically using the NASB by putting "NASB" after the reference, then the ESV version probably won't suffice. Showing it could prevent the writer from conveying his or her point clearly. So we opt not to show it, if the verse is referencing a particular translation. However, your suggestion to have the behavior be optional may be a good compromise.

   Thanks for the CSS, that will go a long way to streamline things.

5. nyoungman
   Member
   Posted 1 year ago #

   I guess I can understand that. :-)

   Thanks Peter.

Topic Closed

This topic has been closed to new replies.