<?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/"
		>
<channel>
	<title>Comments on: Overview of the New dotCMS 1.6 Calendar</title>
	<atom:link href="http://www.supersatellite.com/2008/05/14/overview-of-the-new-dotcms-16-calendar/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.supersatellite.com/2008/05/14/overview-of-the-new-dotcms-16-calendar/</link>
	<description>Blogging in a new web</description>
	<lastBuildDate>Mon, 23 Jan 2012 18:01:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Mel</title>
		<link>http://www.supersatellite.com/2008/05/14/overview-of-the-new-dotcms-16-calendar/comment-page-1/#comment-1088</link>
		<dc:creator>Mel</dc:creator>
		<pubDate>Fri, 10 Jul 2009 16:08:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.supersatellite.com/?p=287#comment-1088</guid>
		<description>How would one make that simple shortcut that pulls in events from the structure? 

I&#039;m new to dotCMS but I have to support no scripts users.</description>
		<content:encoded><![CDATA[<p>How would one make that simple shortcut that pulls in events from the structure? </p>
<p>I&#8217;m new to dotCMS but I have to support no scripts users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Fienen</title>
		<link>http://www.supersatellite.com/2008/05/14/overview-of-the-new-dotcms-16-calendar/comment-page-1/#comment-971</link>
		<dc:creator>Michael Fienen</dc:creator>
		<pubDate>Thu, 08 Jan 2009 00:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.supersatellite.com/?p=287#comment-971</guid>
		<description>You are 100% correct.  The front end calendar as it works out of the box is HEAVILY reliant on javascript, almost to a fault, one might say.  I&#039;ve been talking with Chris a little about possible options to get it working better without it.  Ultimately, I do plan on rewriting ours to be much more accessible once the time presents itself.

That said, it is a fairly simple shortcut to make a page that pulls in events from the structure in a much more plain, straightforward interface to use as an alternate page.  Not a perfect solution, but a decent middle ground.</description>
		<content:encoded><![CDATA[<p>You are 100% correct.  The front end calendar as it works out of the box is HEAVILY reliant on javascript, almost to a fault, one might say.  I&#8217;ve been talking with Chris a little about possible options to get it working better without it.  Ultimately, I do plan on rewriting ours to be much more accessible once the time presents itself.</p>
<p>That said, it is a fairly simple shortcut to make a page that pulls in events from the structure in a much more plain, straightforward interface to use as an alternate page.  Not a perfect solution, but a decent middle ground.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otis</title>
		<link>http://www.supersatellite.com/2008/05/14/overview-of-the-new-dotcms-16-calendar/comment-page-1/#comment-966</link>
		<dc:creator>Otis</dc:creator>
		<pubDate>Mon, 05 Jan 2009 18:48:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.supersatellite.com/?p=287#comment-966</guid>
		<description>The dotcms calendar lacks support for uses without javascript enabled or for users browsing the content from a screen reader. In our case we will have to rewrite much of the code to meet the clients and web standards for accessibility</description>
		<content:encoded><![CDATA[<p>The dotcms calendar lacks support for uses without javascript enabled or for users browsing the content from a screen reader. In our case we will have to rewrite much of the code to meet the clients and web standards for accessibility</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: idris</title>
		<link>http://www.supersatellite.com/2008/05/14/overview-of-the-new-dotcms-16-calendar/comment-page-1/#comment-672</link>
		<dc:creator>idris</dc:creator>
		<pubDate>Fri, 13 Jun 2008 15:33:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.supersatellite.com/?p=287#comment-672</guid>
		<description>hey Michael!
   thanks for yr response... 
i unpublished or even tried archeiving the event but still it shows on the front end... till it is deleted....why so?
i am working on the dotCMS 1.6.0.6 version...</description>
		<content:encoded><![CDATA[<p>hey Michael!<br />
   thanks for yr response&#8230;<br />
i unpublished or even tried archeiving the event but still it shows on the front end&#8230; till it is deleted&#8230;.why so?<br />
i am working on the dotCMS 1.6.0.6 version&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Fienen</title>
		<link>http://www.supersatellite.com/2008/05/14/overview-of-the-new-dotcms-16-calendar/comment-page-1/#comment-671</link>
		<dc:creator>Michael Fienen</dc:creator>
		<pubDate>Fri, 13 Jun 2008 02:22:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.supersatellite.com/?p=287#comment-671</guid>
		<description>On the back end, all events show up on the calendar, including unpublished and archived events. Note the colored markers next to them.  Things with yellow and red markers won&#039;t be visible on the front end.  This is for two reasons: one, to prevent accidental deletion and provide a moderation backchannel, and two, because calendar events are content like anything else in the system, it has to adhere to the same publishing rules.  This also means they follow standard workflow protocols, so event &quot;approval&quot; would stem from the permissions of the person creating the event.</description>
		<content:encoded><![CDATA[<p>On the back end, all events show up on the calendar, including unpublished and archived events. Note the colored markers next to them.  Things with yellow and red markers won&#8217;t be visible on the front end.  This is for two reasons: one, to prevent accidental deletion and provide a moderation backchannel, and two, because calendar events are content like anything else in the system, it has to adhere to the same publishing rules.  This also means they follow standard workflow protocols, so event &#8220;approval&#8221; would stem from the permissions of the person creating the event.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: idris</title>
		<link>http://www.supersatellite.com/2008/05/14/overview-of-the-new-dotcms-16-calendar/comment-page-1/#comment-670</link>
		<dc:creator>idris</dc:creator>
		<pubDate>Thu, 12 Jun 2008 22:06:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.supersatellite.com/?p=287#comment-670</guid>
		<description>hi
is it that i am mistaken? i tried using the cms 1.6 calender... but i cant find the evenet approval or disapproval link and even after unpublishing or archeiving the event remains on the list...
only if i delete does it not show...
is there something i am missing...

besides all this the feature is cool and i am luving to use it.... the video helped too.. thanks</description>
		<content:encoded><![CDATA[<p>hi<br />
is it that i am mistaken? i tried using the cms 1.6 calender&#8230; but i cant find the evenet approval or disapproval link and even after unpublishing or archeiving the event remains on the list&#8230;<br />
only if i delete does it not show&#8230;<br />
is there something i am missing&#8230;</p>
<p>besides all this the feature is cool and i am luving to use it&#8230;. the video helped too.. thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Falzone</title>
		<link>http://www.supersatellite.com/2008/05/14/overview-of-the-new-dotcms-16-calendar/comment-page-1/#comment-600</link>
		<dc:creator>Christopher Falzone</dc:creator>
		<pubDate>Thu, 15 May 2008 12:02:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.supersatellite.com/?p=287#comment-600</guid>
		<description>Great Article!  Thanks for the overview.</description>
		<content:encoded><![CDATA[<p>Great Article!  Thanks for the overview.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

