«
»

JSONView Updated to 0.1b3

Today I uploaded a new version of JSONView to addons.mozilla.org. I’m sticking with the wimpy version number for now, but I think JSONView has been proving itself out in the wild. One major bug was uncovered that caused JSON documents larger than 8KB to render incorrectly, and that’s fixed in this new version. I’ve also added three new translations of the extension (French, Dutch, and Czech) courtesy of the folks at BabelZilla.org – if you want to help out you can check out the available translations and add yours. Lastly, the extension is now compatible with Firefox 3.1b3. I’ve been trying to keep things tested on the beta browsers within a day or two of their release. If you have an older version of the extension you’ll need to go back to AMO and install it again – automatic updates won’t work until JSONView is out of the sandbox.

JSONView has gotten a bit of coverage on the blogs, too, which I’ve enjoyed. It made it onto the front page of Delicious and reddit programming, and Ars Technica wrote an article in their journals. Also, I was interviewed on OpenSource Release Feed, which was fun. I’m glad that people are getting to use the extension and find it helpful. Hopefully when it gets released from the sandbox it’ll get even broader exposure.

Tags: , , ,

This entry was posted on Sunday, March 15th, 2009 at 6:45 pm and is filed under JSONView. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 Responses to “JSONView Updated to 0.1b3”

  1. riz says:
    April 16, 2009 at 11:53 am

    Hi there! I love the idea of JSONView, but one thing I’d like to change is that I’d like JSONView to support not only “application/json” content types, but “text/json” as well.

    I am not familiar enough with nsIStreamConverter, but if you point me in the right direction, I can try doing it myself in Google code (and post back the changes to you). It sounds like you’d have to register another whole stream converter for “text/json”.

  2. Ben Hollis says:
    April 16, 2009 at 10:27 pm

    Hey riz, you can follow the discussion about that on the Google Code project issue tracker: http://code.google.com/p/jsonview/issues/detail?id=12

    You’re right that it wouldn’t be hard, but the issue is that there’s really only one correct content type for JSON, and that’s “application/json”. It’s not like JavaScript which has a handful of valid types. So I’d recommend fixing your server rather than extending JSONView to handle invalid cases.

Leave a Reply