<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <title>CalendarHub Weblog: Badge Updated; New Options Added, More Coming:</title>
  <id>tag:weblog.calendarhub.com,2005:Typo</id>
  <generator uri="http://typo.leetsoft.com" version="4.0">Typo</generator>
  <link href="http://weblog.calendarhub.com/xml/atom10/article/49/feed.xml" rel="self" type="application/xml+atom"/>
  <link href="http://weblog.calendarhub.com/articles/2007/06/06/badge-updated-new-options-added-more-coming" rel="alternate" type="text/html"/>
  <updated>2007-06-17T01:42:50+00:00</updated>
  <entry>
    <author>
      <name>Barry</name>
    </author>
    <id>urn:uuid:7e21c706-47fa-42fe-842d-d692364e9774</id>
    <published>2007-06-17T01:23:50+00:00</published>
    <updated>2007-06-17T01:42:50+00:00</updated>
    <title>Comment on Badge Updated; New Options Added, More Coming: by Barry</title>
    <link href="http://weblog.calendarhub.com/articles/2007/06/06/badge-updated-new-options-added-more-coming#comment-55" rel="alternate" type="text/html"/>
    <content type="html">We've since resolved Dirk's problem here, and I think the turnaround on the fix was actually fairly quick. I'm just now getting around to updating this because our blog was being very finicky and wouldn't let me post a response the day of the mishap. 

The problem was simply an ugly bit of experimental code that made its way into production thanks to yours truly. 

Props to Dirk for spotting and reporting this issue.</content>
  </entry>
  <entry>
    <author>
      <name>Dirk</name>
    </author>
    <id>urn:uuid:b8098542-7ca5-4243-b713-08a80f9b85cd</id>
    <published>2007-06-15T04:49:31+00:00</published>
    <updated>2007-06-15T04:52:24+00:00</updated>
    <title>Comment on Badge Updated; New Options Added, More Coming: by Dirk</title>
    <link href="http://weblog.calendarhub.com/articles/2007/06/06/badge-updated-new-options-added-more-coming#comment-50" rel="alternate" type="text/html"/>
    <content type="html">Hi,

Cool badge and it worked ...

But starting today I get a 'UniversalBrowsePermission denied' error; and why does the javacode try to login to localhost:3000? (Isn't that the rails test url?)

Please have a solution, otherwise I will have to drop the badge ...

</content>
  </entry>
  <entry>
    <author>
      <name>Barry</name>
    </author>
    <id>urn:uuid:fb817e4a-2017-4f3e-b2f1-726fb2691646</id>
    <published>2007-06-06T20:20:25+00:00</published>
    <updated>2008-09-26T09:06:09+00:00</updated>
    <title>Badge Updated; New Options Added, More Coming:</title>
    <link href="http://weblog.calendarhub.com/articles/2007/06/06/badge-updated-new-options-added-more-coming" rel="alternate" type="text/html"/>
    <content type="html">&lt;p&gt;Due to recent customer requests, we have added a few parameter options to the embeddable CalendarHub Event Badge. If you&amp;#8217;re not familiar with the badge, it&amp;#8217;s a little chunk of Javascript code and &lt;span class="caps"&gt;CSS&lt;/span&gt; that you can drop in your website or blog to display your upcoming events (those that are marked public) from a given calendar. See an example of its usage &lt;a href="http://www.homerlibrary.org"&gt;here&lt;/a&gt;.&lt;/p&gt;


	&lt;p&gt;New to the badge is the ability to display descriptions inline with the event title, along with settings for number of days in the future from which you wish to fetch events and max events to display. Not groundbreaking by any means, but worth noting if you are considering or already using the badge.&lt;/p&gt;


	&lt;p&gt;More near-term updates for the badge are being considered. Suggestions are welcome through the feedback system or here in the comments.&lt;/p&gt;</content>
  </entry>
</feed>
