303174 - iCalendar extension-properties suggestion

Status: VERIFIED WONTFIX

(Calendar :: Internal Components, enhancement)

Description

[Felipe]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

What about an option to add additional extension properties to an event? For
example, a way to get

X-Link: http://something.net/foo

exported in an iCal of an event?

Reproducible: Always

Steps to Reproduce:

Comment 1

[Joey Minta]

This should already be possible.  See this thread for a very similar question:
http://groups.google.com/group/netscape.public.mozilla.calendar/browse_frm/thread/354da3bafb5f4338?tvc=1&q=syncid&hl=en

Comment 2

[Felipe]

It's possible, but is there UI to add the extra iCal fields? I can't find it
anywhere....it seems like it should be somewhere within an event's properties
dialog.

Comment 3

[Joey Minta]

(In reply to comment #2)
> It's possible, but is there UI to add the extra iCal fields? I can't find it
> anywhere....it seems like it should be somewhere within an event's properties
> dialog.

Wouldn't that be the role of an extension?  Writing an extension that adds a
particular field to the event dialog is fairly easy.  However, adding UI to
allow for general addition of fields, in the standard build, would be something
that every user would have to deal with and I think this feature would confuse
more people than it would help.

If this is just a UI request, then I suggest that it is WONTFIX.

Comment 4

[Felipe]

Fair enough....you're right; most users would have no idea what that UI is for.

Is it equally easy to add the parsing mechanism when importing iCal data?

Comment 5

[gekacheka]

(clarifying title, was "iCal extension suggestion":
iCal is the Apple iCal program to many people... --> iCalendar
extension means xpi to many in context of moz apps --> extension-properties)

Extension properties are just stored and retrieved as text, no additional
parsing is done.

If your extension property is a date property, you can use
calDateTime.icalString to generate the date in ics format.  If it is a floating
date or a UTC ("zulu") date, then you won't have to worry about parsing the
timezone.  The ics format can be parsed with a regular expression.  For an
example, search for "X-DTEND" in the patches to bug 298102.  The ItemDialog
there uses an "X-DTEND" extension property to store the end date for tasks,
which normally do not have an end date.  (There is also an extension xpi for
nightly builds there so you can test and see that it works.)

Comment 6

[Joey Minta]

This is WONTFIX, in line with comment #3

Comment 7

[Reed Loden [:reed]]

The bugspam monkeys have been set free and are feeding on Calendar :: Internal Components. Be afraid for your sanity!