#5 Event Owners

[Valcar]

The ability to create an identity for an event, and assign that identity as an owner of/linked to said event. Multiple events can have the same owner.

For example, doing a WW2 timeline haveing both the Axis and Allied timeline together in the same document. But being able to break down which events belonw to Germany, Italy, Great Britian, and the United States etc.

* Ability to create new owners
* Ability to assign the owner to an event
* Ability to filter owners in the time line

[Sebastian Fischer]

Logged In: YES
user_id=1135379
Originator: NO

Wouldn't it be better to use different calendars in the same document? Did you already notice that by selecting View->Calendar_list you get a list of calendars in the current document. If you then add one calendar for Axis, Allied, etc. you can name and colour them differently and also decide to hide or show them.

Whereas the idea of an owner would make sence for shared calendars, the idea of a filter as you suggested is - although a mighty tool - a bit complex in my opinion. Surely one could think of such a function, but I dont now any "normal" (none timeline) calendar that would use this. I would rather use different calendars and thereby make the structure of the events more explicit.

One possible useful extension for larger documents could be a hierarchy of calendars. But also that is very complex, and I would think if there is a easier way to structure events in a complex
document.

[Valcar]

Logged In: YES
user_id=1646676
Originator: YES

Ahh, I did not notice that. Indeed having multiple calendars for one timeline will work quite well. In essence this is exactly what I suggested, only an alternative way of achieving it. In essence a calendar is an ‘owner’ of all events placed in that calendar, then by selecting the calendar it displays it, (and allows you to change the color). This provides the functionality that I require.

A possible solution to the hierarchy of calendars could be a document hierarchy, which holds multiple documents in much the same way the current document holds multiple calendars.

Thank you for answering my feature suggestion.

[ojcit]

Logged In: YES
user_id=1292979
Originator: NO

I think it can be even more general than that. You could have the ability to assign arbitrary objects/descriptions to each event, including owners, attendees, points of contact, guests of honor, etc. In the most general implementation, you could sort by arbitrary XML object or attribute, but maybe what I'm thinking of is beyond current scope.

My thinking is, instead of implementing an Owner object per se, create a person.eventowner or whatever and be able to break it down. So, as soon as you break it down by axis/allied, you'll want to do it by theater, then by commander, all the way down to the individual unit or even beyond (think serial numbers on rifles). Probably an even lower priority.

[ojcit]

Logged In: YES
user_id=1292979
Originator: NO

I think it can be even more general than that. You could have the ability to assign arbitrary objects/descriptions to each event, including owners, attendees, points of contact, guests of honor, etc. In the most general implementation, you could sort by arbitrary XML object or attribute, but maybe what I'm thinking of is beyond current scope.

My thinking is, instead of implementing an Owner object per se, create a person.eventowner or whatever and be able to break it down. So, as soon as you break it down by axis/allied, you'll want to do it by theater, then by commander, all the way down to the individual unit or even beyond (think serial numbers on rifles). Probably an even lower priority.

[Sebastian Fischer]

Logged In: YES
user_id=1135379
Originator: NO

Thanks for this discussion. My point is, that I would like to stay ical conform at least until a first, stable, "round" release is done. Then I can also think of leaving the ical, and replace it by ical import and export functionality. But even though this timeline calendar provides more possibilities than a normal calendar, I would like to stay close to what you would expect from a standard calendar program, as it makes switching between both simpler. Also implementing a timeline view for sunbird e.g. could then be easier done and I would like to see something in that direction approach. When I had a close look at the ical format, I found many ical specifications that could be of great value, although rarely used in the "normal" calendar programs that I know. At the moment calizo only uses very very little of the ical opportunities.