Re: [Evolution-hackers] Creating folders via CORBA interface

[Not Zed <notzed ximian com>]

On Tue, 2003-06-24 at 06:57, Patrick Gerzanics wrote:
> What is the 'recommended' way for creating additional folders (such as
> Calendar/Tasks/etc.) via the CORBA interface?  Currently I am using the the
> GNOME/Evolution/Storage interface which allows me to obtain the list of
> GNOME/Evolution/Folder objects but when I attempt to call:
> 
> createAsyncFolder(...) it crashes Evolution.
> 
> I've tried the following parameters:
> 
> asyncCreateFolder("file:///home/patrickg/evolution/local/Test1", "calendar",
> "Test1", "", listenerReference)
> 
> asyncCreateFolder("file:///home/patrickg/evolution/local/Test1", "calendar",
> "Test1", "file:///home/patrickg/evolution/local/", listenerReference)
> 
> asyncCreateFolder("file:///home/patrickg/evolution/local/Test1", "calendar",
> "Test1", "file:///home/patrickg/evolution/local", listenerReference)
> 
> There was no documentation for these functions which makes me wonder if
> they're intended to be private CORBA interfaces, in which case what is the
> intended way of creating the folders?

Hmm, you're adventurous.

Unfortunately I dont know the answer either :-/  Those interfaces look
'right' to me.

Although definelty one problem, is the arguments aren't quite right.

void asyncCreateFolder (in string path,
                                        in string type,
                                        in string description,
                                        in string parent_physical_uri,
                                        in Bonobo::Listener listener);


path is just a simple path, from the root directory of the component.
i.e. probably just 'Test1' in this case.  It should match the uri in
some form or another.

But on the other hand, local folders are handled in a rather odd way, so
... i dont know.


> Also, is there a way to make the retail version of Evolution (1.4 downloaded
> via the Ximian Red Carpet method) emit debug information?  It would be nice
> to have more feedback then 'Application "evolution-1.4... has crashed due to
> a fatal error"

run it inside gdb and get a backtrace when it crashes.

but unless you have debugging symbols (and even better, the source
itself), you're not going to find a lot of terribly useful information
from the traces generated - you might get enough for a hint though.

> Thanks for any and all assistance.

what language are you trying this with anyway?