Discussion:
[CalendarX-users] Calendar X on Plone 4
David Siedband
2011-05-12 15:05:53 UTC
Permalink
Hi,

I saw the earlier thread about making CalendarX work on Plone 4 and I'm following up to see if anyone has made progress on this goal. I'm interested to move this forward and I'm reaching out to connect with people who might want to work together to make this happen. If you're interested in working on this or pooling resources, ping me on email or irc (siebo on freenode).

Lupa, you mentioned in an earlier thread two tasks that needed to be done to get CalendarX working on Plone 4, specifically (1) migrating from AdvancedQuery to standard Plone catalog queries, and (2) changing how the css/javascripts are registered with Plone. You mentioned that you had made some progress getting #1 working, and that you were looking for help with #2. I think with a bit more information I could take this on. I assume this means registering the CSS/scripts using GenericSetup. I'm just a little unclear on which css/scripts to associate and what kind of conditionals we'd be using to limit their rendering to CalX pages. Do you or someone else knowledgable about this have time to talk me through what this involves? Also, is the code for #1 in version control somewhere?

Thanks,
--
David Siedband
http://zentraal.com
Lupa Zurven
2011-05-12 15:59:33 UTC
Permalink
Hi David,
Your help would be greatly appreciated. I've been unPloned personally
for a couple years now, so I have little motivation to do this myself, but
am always tickled to see how many Plone sites still use CalendarX and how I
would be tickled to see someone else move it forward. I'll help as much as
I can, within limits of my time.

#1 - Yep, absolutely trivial. CalendarX has always had the code for both
AdvancedQuery and standard Plone catalog queries. All that needs to be done
is to change the default behavior from using AQ to using the standard
approach. I believe both sets of queries are in working order otherwise,
unless there are in Plone4 changes to the names of the parts of the standard
Event.

#2 - This is what flummoxed me. I got CalendarX to run (using the above)
just fine, except none of the Javascript and CSS were loading for the
Calendar, so it lacked key functionality as well as styling. I didn't
immediately find instructions on how to do this, but it sounds like you're
the one to help find it.

So I'd suggest simply building a fresh Plone4 install on your dev machine
with a default buildout and make sure all is well. Then add CalendarX to
your buildout and bring it down and watch the errors when you try to run
it.

Then change the default setting to NOT use AdvancedQuery, and it should then
run properly, but lack CSS styling and JS functionality in the views.

Then you can play with your local copy of CalendarX to get it to properly
read the JS and CSS. The JS is very old code and hence uses none of the
modern JS frameworks that would make things easier and/or shorter. That
said, it's a little less breakable this way and not long enough to be in any
real need of further brevity.

I hope that gets you started. Let's keep our discussions on the list too,
in case anyone else finds it helpful and/or feels like jumping in too.
+lupa+
Post by David Siedband
Hi,
I saw the earlier thread about making CalendarX work on Plone 4 and I'm
following up to see if anyone has made progress on this goal. I'm
interested to move this forward and I'm reaching out to connect with people
who might want to work together to make this happen. If you're interested
in working on this or pooling resources, ping me on email or irc (siebo on
freenode).
Lupa, you mentioned in an earlier thread two tasks that needed to be done
to get CalendarX working on Plone 4, specifically (1) migrating from
AdvancedQuery to standard Plone catalog queries, and (2) changing how the
css/javascripts are registered with Plone. You mentioned that you had made
some progress getting #1 working, and that you were looking for help with
#2. I think with a bit more information I could take this on. I assume
this means registering the CSS/scripts using GenericSetup. I'm just a
little unclear on which css/scripts to associate and what kind of
conditionals we'd be using to limit their rendering to CalX pages. Do you
or someone else knowledgable about this have time to talk me through what
this involves? Also, is the code for #1 in version control somewhere?
Thanks,
--
David Siedband
http://zentraal.com
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
CalendarX-users mailing list
https://lists.sourceforge.net/lists/listinfo/calendarx-users
Loading...