122647 - (cal-exporting) Exporting Calendars (Calendar Requirements Document, section 5)

Status: RESOLVED INVALID

(Calendar :: General, defect)

Description

[Chris Charabaruk]

This is a tracking bug for Download Calendars, section 4.0 of the Calendar 
Requirements 
Document.

Comment 1

[Tom Neff]

May I suggest doing the initial version of this feature as a simple XML dump and
reload of the personal calendar database.  That would let people share their
calendars across multiple machines, pending more complex interaction with
calendar servers.

Comment 2

[Chris Charabaruk]

Bugspam: Adding meta keyword to tracking bugs, something they should have had
from the start. :P

Comment 3

[paul w brown]

IMHO, another part of this bug should have some functionality/interoperability
of/with Calendar Servers (ie., Netscape Calendar Server)

Comment 4

[Mike Potter]

Tracking bug. Sorry for the spam.

Comment 5

[Mike Lee]

I dont imagine this bug is too hard. Basically another instance of oeIICal and
copy the selections across. However I can't stop the feeling there are a more
elegant solution which integrate with other export features (email, multiple
users, import, etc)

Comment 6

[Brant Gurganus]

Default QA Contact for Calendar has changed.  If you wish to remain the QA
contact for this bug, feel free to change it back.

Comment 7

[Carl Brewer]

This would help me a lot, I use mozilla at home and at work, and I'd like
to be able to publish my calender from work, pick it up when at home,
publish again from home, and pick it up again from work.  At the 
moment I can't see an easy way to do this unless I want to run
two calenders, which seems clunky at best.

Just a simple reload from dav server would be fine as a simple feature.
This wouldn't scale well, but for my use (which is typical?) it'd
work fine.

Comment 8

[HadaDeLaLuna]

maybe download page can propose to copy-paste link into a 'new calendar'
'location' boxe... it works that way... instead of incitate so download ;o)) it
would be simplier for most ppl

Comment 9

[Rohezal]

Not sure where to put this suggestion:
What about an option to export your calendar to an image? It would be real neat
if you could have a desktop wallpaper showing upcoming events. This would then
be updated every time something changes and you would have all your appointments
right onto your desktop, no need to switch to calendar. 
Have a look at the "Active Desktop Calendar" to get an idea of what I'm talking
about:
http://www.xemico.com/adc/screenshots.html

Comment 10

[José Luis Tallón]

It would be easier to export to HTML: simply save a dump of the HTML which is
already generated by Calendar: instead of rendering it in Gecko, save it to a
file... 

Ideally, the output would be split among several pages (one per month), linked
by means of REL="prev" / REL="next" tags.

Of Course, the period to export should be selectable, and there should be a
button  available to select *all events* in the calendar with one click. This
way, exporting a whole Calendar would be a matter of five clicks at most (start
Export Wizard, select HTML output format, select "all events" option, select
output file, click Finish)
[sorry, too busy with many other OSS projects to devote time to yet another one :-S]

Comment 11

[Simon Paquet [:sipaq]]

We don't need this tracking bug, because the underlying requirement document is outdated and has therefore been removed.