FireBible 1.3 Released

I released FireBible 1.3 last weekend, with the following key fixes. If you already have FireBible installed, you can check for updates, or head on to the FireBible page to get it.

Changes in 1.3:

  • Will automatically download and install JSword.
  • Can automatically install books if none found.
  • You can now type book names first in Ubiquity (don’t need to start with ‘sword’).
  • Fixed Ubiquity command installation issues.
  • Fixed issue with Sun’s Java 7 browser plugin.
  • Raised compatibility to work with more recent Firefox versions.

For those of you having issues getting Ubiquity to work with recent Firefox releases, please download this file and open it (File > Open File…) using Firefox. This is a version of Ubiquity being maintained by satyr.

Next up:

  • Getting FireBible working with OpenJDK / IcedTea browser plugin (still only works with Sun’s VM and plugin) but OpenJDK and IcedTea compatibility seems more possible than GCJ support.
  • Integration of a newer version of JSword with av11n support (which is still being developed) so I can finally support Catholic Bibles.

, , ,

No Comments

DataFox 1.9.5 Released

Announcing the release of DataFox 1.9.5, with:

  • Support for selfcare.ndc.bsnl.co.in, thanks to Rohit Singh for the help. The “charged usage” is displayed as 0, (at least for his account) and this is the value DataFox uses to display the progress; so if your account has this same problem, you will not see a progress bar at all and the surplus calculations will be off. Hopefully BSNL fixes this problem soon. If you manually enter selfcare.wdc.bsnl.co.in in the domain field, DataFox might work for that too because they appear to use the same backend. Unfortunately, because nobody has sent me their credentials, I have been unable to test this or add support if required.
  • Increased Firefox compatibility range to 15 – I don’t want to be forced to release a new version every couple of months with these monthly major version changes.

As always, if you want support for the selfcare portals, please send me your credentials or I have no way of implementing support and I will have to simply ignore and / or delete your comments.

, ,

No Comments

Google Talk Not Authorized – Pidgin / Trillian

I had been struggling with this problem for quite some time; every now and then Pidgin would refuse to connect to Google Talk and give me a Not Authorized failure message. All credentials, server details and network conditions were unchanged. I installed Trillian and found that when Pidgin failed in this way, Trillian wouldn’t connect either.A few forum threads would suggest updating to newer versions of Pidgin/Trillian or changing servers and re-checking credentials; most were dated threads which are irrelevant today. Pidgin would resume working as suddenly as it stopped, but sometimes after days of being unable to connect. All this time, the GMail based chat would work without issue, a veritable PIA!

I found, entirely by accident that my account had an Account Locked status if I logged in with the official Google Talk client. Unfortunately, I didn’t have their official client installed all this time, so I didn’t realize this earlier. Attempting to login to chat at this time would present you with a captha and after passing through this, you would be able to connect on Pidgin too. Apparently Pidgin and Trillian are foxed when the account is locked and don’t know how to proceed; I have no idea why my account gets locked either… I also don’t know what the platform independent solution is because AFAIK the official client is available only on Windows; logging in and out of chat in GMail didn’t help.

TL;DR If you get a Not Authorized message in Pidgin or Trillian, login using the official Google Talk client, pass the capthca test and you will now be able to connect again, even after quitting the official client.

, , ,

No Comments

DataFox 1.9.3 Released

Nothing special to see here, just a release I was forced to make to increase the range of Firefox versions that DataFox supports due to the recent Firefox 5 release. I have tested DataFox even with Firefox 6 and it works just fine, so increased the range to support Firefox 6. No new features or fixes in this release.

Something I may not have mentioned earlier, for Firefox 4 (and up) users, if you are wondering where DataFox has gone, you need to enable the Add-on bar from the View > Toolbar menu (or press ‘Ctrl + /’).

I am aware that DataFox does not work with the new BSNL selfcare sites; if users from each zone would send me their usernames and passwords, that would help a great deal. If you want selfcare support, please send me your credentials.

Share and enjoy!

,

7 Comments

FireBible 1.2 Released

A long overdue release of FireBible, version 1.2 adds support for Firefox versions 4 through 6 (yes, 6); so overall it is compatible with Firefox 3 and above. In this version, I also added the ability to view Bibles side by side. If you have FireBible installed, please check for updates to install version 1.2, or head on to FireBible to get it!

What’s next for FireBible:

  • Easier installation – most users have trouble with the separate JSword installation that is required, future versions will have JSword integrated; this concern has also been raised by the Mozilla add-ons review team.
  • Work towards support for Catholic Bibles by helping with deutrocanonical support in the JSword backend.
  • Several bug fixes and user requested enhancements; these have unfortunately been ignored for 1.2 because I did not want to delay Firefox 4 support by trying to pack everything into a single release.

Supporting a major new Firefox release has, unfortunately, never been too easy and Firefox 4 was no different:

  1. Protocol handling techniques changed and finding a solution that worked for both Firefox 3.x and 4.x was irritating.
  2. This bug threatened to make Java inaccessible to extensions, would have knocked FireBible out of Firefox for good.
  3. Bookmark / folder manipulation was made more difficult by removal of a method that I was actively using.
  4. Annotations handling code (used internally to classify FireBible URLs) had to moved to keep it working.
  5. Several other minor issues.

Ultimately, nothing required rocket science to fix, but the number of changes required to keep FireBible working was frustrating.

 

 

, ,

1 Comment