Now, does each ESource have some sort of an identity that I can send as the ESource* parameter to the e_cal_new() function?
Or is their some way I can access the ESources using any functions [I see that there is a get_source() function in EBookBackend]. If so, can you elaborate on the value of parameters that I have to send to such a function.
Or do I have to construct the ESource on my own (parse the data obtained from gconftool and assign corresponding data members) ?
Thanks
On 7/20/06,
chenthill palanisamy <[EMAIL PROTECTED]> wrote:
On Wed, 2006-07-19 at 11:25 -0400, Teresa Thomas wrote:
> Hi
> I have one last (hopefully) question about libecal. I want to add a
> VEVENT to an existing Evolution calendar.
>
> Hence, I created an iCalComponenent to be added and hope to use the
> e_cal_create_object(ECal* eCal,iCalComponent iCalcomp, char** uid,
> char** error) function.
>
> Now, I understand that eCal is a calendar client. If I want to add my
> event to an Evolution calendar, what exactly should eCal contain? Is
> it some sort of an identity of a cal? If so, how can I obtain it.
ECal client can be obtained by using the function e_cal_new, by passing
an ESource. ESource holds the settings required for a calendar client
which is stored in gconf. The client is associated with the backend
through the protocol specified in the uri stored in ESource.
Eg: uri starting with file:/// would refer to file backend, contacts://
would be pointing to contacts backend.
- Chenthill.
>
> Thanks!
> On 7/19/06, Teresa Thomas <[EMAIL PROTECTED]> wrote:
> Thanks Mr Palanisamy!
>
> My Bad, I actually meant to ask about the function
> e_cal_component_new() in ECalComponent.h/c.
> Anyway, from what I understand it returns an ECalComponent,
> which is an (easier to manipulate) wrapper around an
> iCalComponent.
>
>
>
> On 7/19/06, chenthill palanisamy <[EMAIL PROTECTED]>
> wrote:
> On Tue, 2006-07-18 at 17:44 -0400, Teresa Thomas
> wrote:
> > Need some assistance in my quest to comprehend EDS.
> >
> > What exactly is the difference between
> e_cal_create_object() [in
> > ECalComponent] and e_cal_create_object() [in
> ECal ] ?
> e_cal_create_object is used to create a appointment,
> task or a memo
> object (ECalComponent) in the corresponding backend
> (file, http,
> groupwise etc). There is no function named
> e_cal_create_object in
> ECalComponent. There is a function
> e_cal_component_get_created which
> gives the creation date of a ECalComponent.
>
> Please have a look at
> http://www.go-evolution.org/EDS_Architecture .
>
>
> - Chenthill.
> >
>
>
>
>
_______________________________________________ Evolution-hackers mailing list [email protected] http://mail.gnome.org/mailman/listinfo/evolution-hackers
