As has been mentioned by KarenS, Views iCal module duplicates most of the functionality of Date iCal.

The difference is that Views iCal allows to add and configure fields using standard Views UI, while it requires modifying template files to configure field output of Date iCal.

It makes sense to merge these two modules in order to avoid duplicate efforts. Suggestions welcome.

Mukhsim.

Comments

babbage’s picture

babbage commented

mukhsim, as the developer of the Views iCal module, can you outline the features of Views iCal that are not presently in Date iCal?

mukhsim’s picture

mukhsim commented

Views iCal allows adding extra fields through Views UI while Date iCal requires doing so through the provided template file. You have full power and flexibility of views fields with Views iCal module.

coredumperror’s picture

coredumperror commented
Title: Duplicate module » Merge Views iCal module into Date iCal.
Version: 7.x-1.x-dev » 7.x-2.x-dev
Assigned: Unassigned » coredumperror

Thanks for the heads up about Views iCal! I'd be happy to merge it into Date iCal, since I'm not especially happy with the way that Date iCal actually pulls each node's data into the VEVENTs.

I'll take a look at how Views iCal is implemented, so we can collaborate.

coredumperror’s picture

coredumperror commented
Status: Active » Postponed

I think merging Date iCal and Views iCal may still be a good idea, but it would be a complicated process that I do not currently have time for.

coredumperror’s picture

coredumperror commented
Status: Postponed » Closed (won't fix)

With the addition of the iCal Fields plugin in the latest version of Date iCal, I think integrating Views iCal will no longer be necessary.