Archive from May 2011
Using Tippy with an image
May 28th, 2011
|
Tippy WordPress Plugin
|
12 Comments

If you want to have a Tippy tooltip pop up over an image, you will have to manually format your link. Here’s how:

<a id="tippy_tipSample0"
   class="tippy_link"
   title="Your Tooltip Title"
   href="http://croberts.me/wp-content/uploads/2011/05/giraffe.jpg"
   onmouseover="Tippy.loadTipInfo('Your Tooltip Text', 0, 0, 'tippy_tipSample0', event);"
   onmouseout="Tippy.fadeTippyOut();">

   <img border="0" src="http://croberts.me/wp-content/uploads/2011/05/giraffe.jpg" />
</a>

Continue reading »

WordPress ESV Plugin Options: 3.6.x
May 28th, 2011
|
WordPress ESV Plugin
|
2 Comments

The ESV plugin has a lot of options. You can safely use the default settings and everything will work fine, but if you want to change any settings you can find information about them below.

ESV Web Key
Passage Retrieval Options
Format Option
When to Process References
Backward Compatibility
Manage Database/Settings

ESV Web Key

A web key is required to use the ESV plugin. The default key of IP will work for most users, but if you get an error that you have exceeded the limit for daily passage retrievals, you may want to apply for a personal ESV Web Key. You can get one at the ESV Bible Web Service. If you have a personal key, enter it in the ESV Web Key input field.

Continue reading »

P2R Text Collections
May 28th, 2011
|
P2R App
|
2 Comments

Text collections are at the heart of P2R. They contain the text that you see, broken down into weeks and formatted with titles, headers, and footers. Text collections are simply XML files with special tags understood by P2R.

There are two ways to add new collections to the P2R app. The first way is to add through an online list:

Continue reading »

Dealing with cross-browser issues in CSS3
May 19th, 2011
|
CSS3
|
0 Comments

One challenge when trying to implement HTML5 and CSS3 is that not all browsers are yet on board, particularly when designing a site with older browsers in mind. Since new browsers are doing so much to enhance their support of web standards, it is quite tempting to ignore older browsers in an attempt to push users to update. There are a few reasons why this will not work:

  • Some users, particularly those with Windows XP or those on managed networks, will not have the option to update their browser.
  • Most clients will (rightly) want to create a web space that works for all visitors, regardless of browser type or version.
  • Many users will simply ignore a site that doesn’t work in their browser. Instead of you helping them update, you have shown them the door.

That said, there does come a time when older browsers must go. For this site, I gave no consideration to Internet Explorer 6. It may work semi decently with this site, it may not. I have no idea. But I have tried to make the site compatible with IE 7 and higher Firefox 3 and higher, Chrome 9 and higher, and Safari 4 and higher. Doing that required a few tools and a few compromises.

Continue reading »