Re: [Evolution-hackers] CAL_STATIC_CAPABILITY_* documentation?
Hi Harry, Thanks a lot for these explanations. Most helpful :-) Does any one know about the remaining ones below? Thanks, jules On Tue, 2006-05-09 at 20:59 +0800, Harry Lu wrote: > > * CAL_STATIC_CAPABILITY_NO_CONV_TO_ASSIGN_TASK > > What is this? Convert from what? > > > > * CAL_STATIC_CAPABILITY_NO_CONV_TO_RECUR > > What is this? Convert from what? > > > A normal event can not be converted to a recurrence event.(???) > > * CAL_STATIC_CAPABILITY_NO_GEN_OPTIONS > > What is this? > > > > * CAL_STATIC_CAPABILITY_REQ_SEND_OPTIONS > > What is this? > > > > * CAL_STATIC_CAPABILITY_RECURRENCES_NO_MASTER > > What is this? > > > > * CAL_STATIC_CAPABILITY_ORGANIZER_MUST_ACCEPT > > The organizer must accept the meeting. > > > > * CAL_STATIC_CAPABILITY_DELEGATE_SUPPORTED > > Support for delegation > > > > * CAL_STATIC_CAPABILITY_NO_ORGANIZER > > Support for meeting without any organizer. > > > > * CAL_STATIC_CAPABILITY_DELEGATE_TO_MANY > > Can delegate to more than one at the same time. > > > > * CAL_STATIC_CAPABILITY_HAS_UNACCEPTED_MEETING > > What is this? ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] CAL_STATIC_CAPABILITY_* documentation?
Jules, I will try to explain some of these based on my understanding when developing evolution-jescs. See my comments below. Harry Jules Colding 写道: On Tue, 2006-05-09 at 14:32 +0200, Jules Colding wrote: On Tue, 2006-05-09 at 14:30 +0200, Jules Colding wrote: * CAL_STATIC_CAPABILITY_NO_AUDIO_ALARMS No audio alarms. Again, how is this related to the backend? Hmm... cut'n paste from a HTML page. These horizontal lines wasn't intended to be in the mail. Here is a better list from current CVS HEAD: * CAL_STATIC_CAPABILITY_NO_ALARM_REPEAT No repeating alarms. How is this related to the backend? Isn't it the Evolution front-end that do the alarm stuff? The backend doesn't support storing repeat alarms. So this feature will disabled from the GUI. * CAL_STATIC_CAPABILITY_NO_AUDIO_ALARMS No audio alarms. Again, how is this related to the backend? The backend doesn't support storing audio alarms. * CAL_STATIC_CAPABILITY_NO_DISPLAY_ALARMS No visual alarms. Again, how is this related to the backend? Similar as above. * CAL_STATIC_CAPABILITY_NO_EMAIL_ALARMS No email alarms. Again, how is this related to the backend? Similar as above. * CAL_STATIC_CAPABILITY_NO_PROCEDURE_ALARMS What is this? The backend doesn't support storing alarms which will call other programs. * CAL_STATIC_CAPABILITY_NO_TASK_ASSIGNMENT The backend can not assign tasks to individual entities. * CAL_STATIC_CAPABILITY_NO_THISANDFUTURE The backend can not do a search for events/tasks that are starting at any time from and including now. When modifying a recurrence event, the backend doesn't support modifying "This and Future instances". * CAL_STATIC_CAPABILITY_NO_THISANDPRIOR The backend can not do a search for events/tasks that are starting at any time before but including now. Similar as above. * CAL_STATIC_CAPABILITY_NO_TRANSPARENCY What is this? The backend doesn't support the event's transparency property. This feature will be disabled in the GUI. * CAL_STATIC_CAPABILITY_ONE_ALARM_ONLY Only one alarm can be active at any one time. Again, how is this related to the backend? Isn't it the Evolution front-end that do the alarm stuff? The backend only support storing one alarm. * CAL_STATIC_CAPABILITY_ORGANIZER_MUST_ATTEND The organizer is a required participant in any meeting. * CAL_STATIC_CAPABILITY_ORGANIZER_NOT_EMAIL_ADDRESS What is this? The organizer field of a meeting is not a e-mail address. It might be a user id, for example. * CAL_STATIC_CAPABILITY_REMOVE_ALARMS Alarms can be removed. * CAL_STATIC_CAPABILITY_SAVE_SCHEDULES What is this? Don't send meeting invitation or updating info from GUI. The backend will do this by itself. * CAL_STATIC_CAPABILITY_NO_CONV_TO_ASSIGN_TASK What is this? Convert from what? * CAL_STATIC_CAPABILITY_NO_CONV_TO_RECUR What is this? Convert from what? A normal event can not be converted to a recurrence event.(???) * CAL_STATIC_CAPABILITY_NO_GEN_OPTIONS What is this? * CAL_STATIC_CAPABILITY_REQ_SEND_OPTIONS What is this? * CAL_STATIC_CAPABILITY_RECURRENCES_NO_MASTER What is this? * CAL_STATIC_CAPABILITY_ORGANIZER_MUST_ACCEPT The organizer must accept the meeting. * CAL_STATIC_CAPABILITY_DELEGATE_SUPPORTED Support for delegation * CAL_STATIC_CAPABILITY_NO_ORGANIZER Support for meeting without any organizer. * CAL_STATIC_CAPABILITY_DELEGATE_TO_MANY Can delegate to more than one at the same time. * CAL_STATIC_CAPABILITY_HAS_UNACCEPTED_MEETING What is this? Thanks, jules ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] CAL_STATIC_CAPABILITY_* documentation?
On Tue, 2006-05-09 at 14:32 +0200, Jules Colding wrote: > On Tue, 2006-05-09 at 14:30 +0200, Jules Colding wrote: > > > > > * CAL_STATIC_CAPABILITY_NO_AUDIO_ALARMS > > No audio alarms. Again, how is this related to the backend? > > Hmm... cut'n paste from a HTML page. These horizontal lines wasn't > intended to be in the mail. Here is a better list from current CVS HEAD: * CAL_STATIC_CAPABILITY_NO_ALARM_REPEAT No repeating alarms. How is this related to the backend? Isn't it the Evolution front-end that do the alarm stuff? * CAL_STATIC_CAPABILITY_NO_AUDIO_ALARMS No audio alarms. Again, how is this related to the backend? * CAL_STATIC_CAPABILITY_NO_DISPLAY_ALARMS No visual alarms. Again, how is this related to the backend? * CAL_STATIC_CAPABILITY_NO_EMAIL_ALARMS No email alarms. Again, how is this related to the backend? * CAL_STATIC_CAPABILITY_NO_PROCEDURE_ALARMS What is this? * CAL_STATIC_CAPABILITY_NO_TASK_ASSIGNMENT The backend can not assign tasks to individual entities. * CAL_STATIC_CAPABILITY_NO_THISANDFUTURE The backend can not do a search for events/tasks that are starting at any time from and including now. * CAL_STATIC_CAPABILITY_NO_THISANDPRIOR The backend can not do a search for events/tasks that are starting at any time before but including now. * CAL_STATIC_CAPABILITY_NO_TRANSPARENCY What is this? * CAL_STATIC_CAPABILITY_ONE_ALARM_ONLY Only one alarm can be active at any one time. Again, how is this related to the backend? Isn't it the Evolution front-end that do the alarm stuff? * CAL_STATIC_CAPABILITY_ORGANIZER_MUST_ATTEND The organizer is a required participant in any meeting. * CAL_STATIC_CAPABILITY_ORGANIZER_NOT_EMAIL_ADDRESS What is this? * CAL_STATIC_CAPABILITY_REMOVE_ALARMS Alarms can be removed. * CAL_STATIC_CAPABILITY_SAVE_SCHEDULES What is this? * CAL_STATIC_CAPABILITY_NO_CONV_TO_ASSIGN_TASK What is this? Convert from what? * CAL_STATIC_CAPABILITY_NO_CONV_TO_RECUR What is this? Convert from what? * CAL_STATIC_CAPABILITY_NO_GEN_OPTIONS What is this? * CAL_STATIC_CAPABILITY_REQ_SEND_OPTIONS What is this? * CAL_STATIC_CAPABILITY_RECURRENCES_NO_MASTER What is this? * CAL_STATIC_CAPABILITY_ORGANIZER_MUST_ACCEPT The organizer must accept the meeting. * CAL_STATIC_CAPABILITY_DELEGATE_SUPPORTED Support for delegation * CAL_STATIC_CAPABILITY_NO_ORGANIZER Support for meeting without any organizer. * CAL_STATIC_CAPABILITY_DELEGATE_TO_MANY Can delegate to more than one at the same time. * CAL_STATIC_CAPABILITY_HAS_UNACCEPTED_MEETING What is this? Thanks, jules ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] CAL_STATIC_CAPABILITY_* documentation?
On Tue, 2006-05-09 at 14:30 +0200, Jules Colding wrote: > > * CAL_STATIC_CAPABILITY_NO_AUDIO_ALARMS > No audio alarms. Again, how is this related to the backend? Hmm... cut'n paste from a HTML page. These horizontal lines wasn't intended to be in the mail. Sorry, jules ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
[Evolution-hackers] CAL_STATIC_CAPABILITY_* documentation?
Hi, Does any documentation as to the precise meaning of the capabilities exists? Some of these aren't entirely obvious. Here is my take on the definitions: * CAL_STATIC_CAPABILITY_NO_ALARM_REPEAT No repeating alarms. How is this related to the backend? Isn't it the Evolution front-end that do the alarm stuff? * CAL_STATIC_CAPABILITY_NO_AUDIO_ALARMS No audio alarms. Again, how is this related to the backend? * CAL_STATIC_CAPABILITY_NO_DISPLAY_ALARMS No visual alarms. Again, how is this related to the backend? * CAL_STATIC_CAPABILITY_NO_EMAIL_ALARMS No email alarms. Again, how is this related to the backend? * CAL_STATIC_CAPABILITY_NO_PROCEDURE_ALARMS What is this? * CAL_STATIC_CAPABILITY_NO_TASK_ASSIGNMENT The backend can not assign tasks to individual entities. * CAL_STATIC_CAPABILITY_NO_THISANDFUTURE The backend can not do a search for events/tasks that are starting at any time from and including now. * CAL_STATIC_CAPABILITY_NO_THISANDPRIOR The backend can not do a search for events/tasks that are starting at any time before but including now. * CAL_STATIC_CAPABILITY_NO_TRANSPARENCY What is this? * CAL_STATIC_CAPABILITY_ONE_ALARM_ONLY Only one alarm can be active at any one time. Again, how is this related to the backend? Isn't it the Evolution front-end that do the alarm stuff? * CAL_STATIC_CAPABILITY_ORGANIZER_MUST_ATTEND The organizer is a required participant in any meeting. * CAL_STATIC_CAPABILITY_ORGANIZER_NOT_EMAIL_ADDRESS What is this? * CAL_STATIC_CAPABILITY_REMOVE_ALARMS Alarms can be removed. * CAL_STATIC_CAPABILITY_SAVE_SCHEDULES What is this? Thanks, jules ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
