Re: [evolution-patches] e-cal APIs for beagle (like) applications to query e-d-s.



On Tue, 2005-06-21 at 17:06 +0530, Veerapuram Varadhan wrote:
> On Tue, 2005-06-21 at 13:01 +0200, Rodrigo Moya wrote:
> > On Tue, 2005-06-21 at 18:57 +0800, Not Zed wrote:
> > > Not a calendar guy, but these just look like helpers for things that can
> > > just be done in code anyway.  Why exactly does the api need expanding
> > > for this?  Shouldn't this just sit in the application?
> > > 
> > > Are e_cal_get_object_list and e_cal_new not exposed to outside code?
> > > 
> > yes, they are
> Yes, they are, but the "icalcomponent" is hard to wrap in evo-#.  So,
> the helper functions, abstract that, and returns back the items as a
> list of strings.

Could just pinvoke icalcomponent_as_ical_string or
e_cal_component_as_string in the evo# bindings themselves?

-JP
-- 
JP Rosevear <jpr novell com>
Novell, Inc.




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]