<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: BusyCal, what iCal for Lion should have been</title>
	<atom:link href="http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 05:18:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Graham Perrin</title>
		<link>http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/#comment-776732</link>
		<dc:creator><![CDATA[Graham Perrin]]></dc:creator>
		<pubDate>Fri, 16 Dec 2011 06:03:30 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=433514#comment-776732</guid>
		<description><![CDATA[Many thanks for drawing attention to the topic that I started in Apple Support Communities. 

I&#039;m a paid up user of BusyCal, but there is explicitly **no support** for Microsoft Exchange Server — http://www.busymac.com/faq/index.html#exchange

For that reason and others, continued use of iCal is a must. 

I should encourage each person who finds difficulties without the sidebar in iCal to send feedback to Apple. Please clear your reasons for each difficulty. 

The sidebar is good for Calendar in iCloud. 

The sidebar was good in iCal before Lion. Apple should allow the user to prefer a sidebar.]]></description>
		<content:encoded><![CDATA[<p>Many thanks for drawing attention to the topic that I started in Apple Support Communities. </p>
<p>I&#8217;m a paid up user of BusyCal, but there is explicitly **no support** for Microsoft Exchange Server — <a href="http://www.busymac.com/faq/index.html#exchange" rel="nofollow">http://www.busymac.com/faq/index.html#exchange</a></p>
<p>For that reason and others, continued use of iCal is a must. </p>
<p>I should encourage each person who finds difficulties without the sidebar in iCal to send feedback to Apple. Please clear your reasons for each difficulty. </p>
<p>The sidebar is good for Calendar in iCloud. </p>
<p>The sidebar was good in iCal before Lion. Apple should allow the user to prefer a sidebar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stilgherrian</title>
		<link>http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/#comment-723742</link>
		<dc:creator><![CDATA[Stilgherrian]]></dc:creator>
		<pubDate>Sun, 04 Dec 2011 09:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=433514#comment-723742</guid>
		<description><![CDATA[BusyCal? http://t.co/zIYKBN5A Looks interesting too, @BeauGiles, thank you.]]></description>
		<content:encoded><![CDATA[<p>BusyCal? <a href="http://t.co/zIYKBN5A" rel="nofollow">http://t.co/zIYKBN5A</a> Looks interesting too, @BeauGiles, thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beau</title>
		<link>http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/#comment-723687</link>
		<dc:creator><![CDATA[Beau]]></dc:creator>
		<pubDate>Sun, 04 Dec 2011 09:03:08 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=433514#comment-723687</guid>
		<description><![CDATA[@stilgherrian @trib @mpesce I hear good things about BusyCal http://t.co/bDHQ8HU9]]></description>
		<content:encoded><![CDATA[<p>@stilgherrian @trib @mpesce I hear good things about BusyCal <a href="http://t.co/bDHQ8HU9" rel="nofollow">http://t.co/bDHQ8HU9</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/#comment-695538</link>
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Sat, 26 Nov 2011 01:46:12 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=433514#comment-695538</guid>
		<description><![CDATA[I just did not upgrade to Lion and use the old iCal. (Which, also was ignored by Apple and during its last two updates, was mucked up even more, made harder to use for the sake of meaningless interface changes and has a number of bugs on entering information in it!) Despite its troubles, it works OK and, it&#039;s what I&#039;ve been using.
Apple has just blown it with iCal not being properly cared for and improved. Then this Lion junk iCal sunk it for me.
I think they just don&#039;t realize how CRITICAL a calendar and date book is on the Mac? Is iCal going to suffer the same long term neglect as printing did with Apple?]]></description>
		<content:encoded><![CDATA[<p>I just did not upgrade to Lion and use the old iCal. (Which, also was ignored by Apple and during its last two updates, was mucked up even more, made harder to use for the sake of meaningless interface changes and has a number of bugs on entering information in it!) Despite its troubles, it works OK and, it&#8217;s what I&#8217;ve been using.<br />
Apple has just blown it with iCal not being properly cared for and improved. Then this Lion junk iCal sunk it for me.<br />
I think they just don&#8217;t realize how CRITICAL a calendar and date book is on the Mac? Is iCal going to suffer the same long term neglect as printing did with Apple?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/#comment-692320</link>
		<dc:creator><![CDATA[Rick]]></dc:creator>
		<pubDate>Thu, 24 Nov 2011 13:50:14 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=433514#comment-692320</guid>
		<description><![CDATA[I kind of like BusyCal because, as you say, the developers have avoided some of the stupid decisions Apple has made with iCal. But there&#039;s nothing really impressive about it, and it seems strange to me that no-one&#039;s come up with really significant interface enhancements in the calendar field to compare with those in task management. An easy example would be allowing users to focus on a single calendar without having to deselect (and remember to reselect later) every other calendar.]]></description>
		<content:encoded><![CDATA[<p>I kind of like BusyCal because, as you say, the developers have avoided some of the stupid decisions Apple has made with iCal. But there&#8217;s nothing really impressive about it, and it seems strange to me that no-one&#8217;s come up with really significant interface enhancements in the calendar field to compare with those in task management. An easy example would be allowing users to focus on a single calendar without having to deselect (and remember to reselect later) every other calendar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Sørensen</title>
		<link>http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/#comment-690954</link>
		<dc:creator><![CDATA[Robert Sørensen]]></dc:creator>
		<pubDate>Wed, 23 Nov 2011 22:35:18 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=433514#comment-690954</guid>
		<description><![CDATA[BusyCal, what iCal for Lion should have been http://t.co/rlcyiY0G]]></description>
		<content:encoded><![CDATA[<p>BusyCal, what iCal for Lion should have been <a href="http://t.co/rlcyiY0G" rel="nofollow">http://t.co/rlcyiY0G</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Abramson</title>
		<link>http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/#comment-689110</link>
		<dc:creator><![CDATA[Andy Abramson]]></dc:creator>
		<pubDate>Wed, 23 Nov 2011 14:55:57 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=433514#comment-689110</guid>
		<description><![CDATA[BusyCal, what iCal for Lion should have been http://t.co/RA46TV8b]]></description>
		<content:encoded><![CDATA[<p>BusyCal, what iCal for Lion should have been <a href="http://t.co/RA46TV8b" rel="nofollow">http://t.co/RA46TV8b</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Brisman</title>
		<link>http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/#comment-688868</link>
		<dc:creator><![CDATA[Andrew Brisman]]></dc:creator>
		<pubDate>Wed, 23 Nov 2011 13:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=433514#comment-688868</guid>
		<description><![CDATA[Samsung is making fool of Apple fans in its new ad?! That’s hilarious! You gotta watch it!
http://goo.gl/pWWde]]></description>
		<content:encoded><![CDATA[<p>Samsung is making fool of Apple fans in its new ad?! That’s hilarious! You gotta watch it!<br />
<a href="http://goo.gl/pWWde" rel="nofollow">http://goo.gl/pWWde</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mícheál Ó Foghlú</title>
		<link>http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/#comment-688871</link>
		<dc:creator><![CDATA[Mícheál Ó Foghlú]]></dc:creator>
		<pubDate>Wed, 23 Nov 2011 13:21:59 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=433514#comment-688871</guid>
		<description><![CDATA[BusyCal, what iCal for Lion should have been http://t.co/dxW5JdZg via @zite]]></description>
		<content:encoded><![CDATA[<p>BusyCal, what iCal for Lion should have been <a href="http://t.co/dxW5JdZg" rel="nofollow">http://t.co/dxW5JdZg</a> via @zite</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WebLight</title>
		<link>http://gigaom.com/2011/11/22/busycal-what-ical-for-lion-should-have-been/#comment-688230</link>
		<dc:creator><![CDATA[WebLight]]></dc:creator>
		<pubDate>Wed, 23 Nov 2011 07:38:02 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=433514#comment-688230</guid>
		<description><![CDATA[BusyCal, what iCal for Lion should have been http://t.co/ofUrszCs]]></description>
		<content:encoded><![CDATA[<p>BusyCal, what iCal for Lion should have been <a href="http://t.co/ofUrszCs" rel="nofollow">http://t.co/ofUrszCs</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
