Nabble - Magnolia

Re: Update on the calendar feed generation progress

2009-11-30T10:02:52Z

On Wed, Nov 25, 2009 at 3:23 PM, Jan Haderka
<jan.haderka@...> wrote:
>
> On Tue, 2009-11-24 at 09:28 -0700, Ryan Gardner wrote:
>> I have it working on my dev system. What I haven't finished yet is
>> getting it integrated into the STK.
>>
>> I decided the best place for the CalendarFeedGenerator would be in the
>> STK module since it is coupled to the stkEvent already.
>
> That's fine. Just put it in the same package as the PageSyndicator is.

Yep, that's where I put it.

>> I see the preferred way to add links to the stk pages is via runtime
>> decoration with javascript. I have a prototype I did yesterday that
>> adds a behavior to initbehavior that adds a calendar download link to
>> the events pages.
>>
> Is it now? I thought you will just produce icon with a link similar to
> templating-kit/paragraphs/teasers/syndicate.ftl, but maybe you had
> something more fancy in mind (like a link in the header of the page?).

The "print" link is the one I noticed that gets decorated into the
page which is what made me assume that approach was the preferred
approach.

I was thinking of something like this for the UI for the links on the
overview page (I made a quick page on google sites to share the
screenshot)

http://sites.google.com/site/ryebryeimages/screensh

Now that I see what you are talking about - it could be pretty easy to
add some icons to the side there with the syndicate.ftl

>> A future step could be calendar aggregation. iCal4j parses ical feeds
>> as well as creates them, so you could do some kind of calendar
>> subscriptions that get dumped into an events page in magnolia quite
>> easily.
>> (Since I have no need personally for calendar subscriptions being
>> pulled into magnoloa, it is unlikely I will be working on this soon)
>
> well, you can pull them in and display them on the calendar with the
> events created directly in Magnolia. Actually this together with part
> you are working on and few other features would be enough to justify
> another STK release.

Interesting idea. How would you suggest setting up a UI or something
for a user to enter calendar feeds? The way I understand the RSS
Aggregation works is that it takes the feeds and loads the data into
the data module. Creating something similar that would read a calendar
feed from a public URL (say a shared google calendar's feed) and
putting that into the data module wouldn't be hard. How would you
suggest modifying the STK to allow for it to show those events that
site in the data repository to show up alongside the events that site
in the website repository in a straightforward way?

The current way it works, unless I missed something, is that the
"events overview" page will list off any event that exists as a child
of it. Should the "events overview" be modified to give it a page
property where you could pick data module nodes to pull events from as
well and then modify the model piece to have it pull both of those
together and spit them out?

From my point of view, pulling in a calendar feed from a URL and
putting the data into the data repository is a fairly easy thing to
do. There are a few issues to work through involving things that
iCalendar supports but magnolia's current events implementation does
not - such as recurrence rules, time zones, or . Having it run on the
same timer as the RSS Aggregation is probably less than optimal but
would work for the time being. The tricky part for me (since I'm not
yet intimately familiar with the workings of the STK) would be getting
them to display in an elegant way alongside the website-repository
events.

I could make the module create nodes in the website repository and
populate with the data from the calendar feed - this would be the
easiest way to tie into the existing STK events implementation but I
don't know about

If you have some suggestions on an approach for this, I could take a
stab at doing that as well.

>> How far along would you like me to get this before I submit it?
>
> As far as you dare to take it :D
>
> Just submit the patch for review once you feel it feature complete and
> we can continue the discussion from that point.

Sounds good. Calendar aggregation could be a killer feature for some
companies that already leverage calendar servers that support
exporting things into an iCalendar format. Even for companies using an
Exchange server, they could use some relatively painless workarounds
such as using Google Calendar's calendar sync program to get their
exchange calendars out onto a calendar they could share into magnolia
(should they leverage google calendar, they could decide to not share
the calendar publicly but to use the "private link" that google
calendar gives you to share just to trusted people)... but I'll avoid
getting ahead of myself... I've also got to now migrate a 3.5 site
over to 4.2 and work on migrating all my older content and a few
custom jsp templates into the STK / fre :)

Ryan

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <dev-list-unsubscribe@...>
----------------------------------------------------------------

Nabble - Magnolia

Re: Update on the calendar feed generation progress

[JIRA] Updated: (MAGNOLIA-2853) Upgrade to jackrabbit 1.6

Some general questions with regard to listings and performance

[JIRA] Created: (MAGNOLIA-2961) multiplehosts property does not work with default cache policy configuration

[JIRA] Created: (MGNLDMS-176) info.magnolia.module.dms.DMSDownloadServlet logs as error level when interrupting download

[JIRA] Created: (MAGNOLIA-2960) Automatic cleanup of unwanted namespaces during export

[JIRA] Created: (MAGNOLIA-2959) MgnlContext.doInsystemContext: binary incompatible change in version 4.2

Re: mod_jk Authentication etc.

mod_jk Authentication etc.

[JIRA] Commented: (MGNLDATA-93) Introduce generics into the parts where they are still missing and cleanup the code

[JIRA] Commented: (MAGNOLIA-2910) Preserve DMS specific versioning command upon workflow installation

[JIRA] Updated: (MAGNOLIA-2903) activation: users having only write permission in a subpart of the hierarchy are not able to activate

[JIRA] Commented: (MAGNOLIA-2958) (Local?) Magnolia 4.1/4.2 AdminCentral often does not display right in Firefox 3.5

[JIRA] Commented: (MAGNOLIA-2958) (Local?) Magnolia 4.1/4.2 AdminCentral often does not display right in Firefox 3.5

[JIRA] Commented: (MAGNOLIA-2958) (Local?) Magnolia 4.1/4.2 AdminCentral often does not display right in Firefox 3.5

[JIRA] Commented: (MAGNOLIA-2958) (Local?) Magnolia 4.1/4.2 AdminCentral often does not display right in Firefox 3.5

[JIRA] Updated: (MAGNOLIA-2958) (Local?) Magnolia 4.1/4.2 AdminCentral often does not display right in Firefox 3.5

[JIRA] Created: (MAGNOLIA-2958) (Local?) Magnolia 4.1/4.2 AdminCentral often does not display right in Firefox 3.5

[JIRA] Created: (MGNLDMS-175) Preview of inbox item doesn't work when activating folder incl. subfolders

[JIRA] Updated: (MAGNOLIA-2491) Generate content2bean documentation

[JIRA] Updated: (MAGNOLIA-2820) Backend with HTTPS - warning in IE7

Re: when will 4.2.2 be released?

Re: A couple of questions:

Re: Login after backup restore

Re: Update on the calendar feed generation progress

Re: Re: custom 301 error message -- moved permanently

Re: when will 4.2.2 be released?

Re: when will 4.2.2 be released?

[JIRA] Updated: (MAGNOLIA-2957) multiple editCode controls cannot coexsit in the same dialog

Magnolia 4.2 released

Magnolia 4.2 released

Re: A couple of questions:

when will 4.2.2 be released?