> 1) What *exactly* does the evolution-test-component do ? create_view_fn > looks as if there is supposed to be a visual display but I can't see how > to get Evolution to call this.
When it calls evolution_shell_component_new, it passes the folder_types array and create_view_fn. folder_types tells the shell what kinds of folders this component handles creating views for, and create_view_fn is the function that will be called when the shell needs a view for one of that type of folder. Then, when the shellcomponent emits "owner_set", the test component calls setup_custom_storage, which creates a new storage in the folder tree with some folders of type "test", and when you click on one of those folders, create_view_fn will be invoked. (Note that Connector does not have any create_view_fn though, since it doesn't create any views of its own. It just creates a storage containing mail, calendar, contact, and task views.) > 2) I am assuming that the Exchange connector is set up as a separate > storage. How is the creation of an account handled in the setup druid ? > I know that the camel provider will "register" itself by having various > provider flags set. Part of Connector is a Camel provider, which gets registered like any other provider and finds its way into the account config dialog that way. The evolution-exchange-storage process reads the configuration database at startup to see if there is an exchange account, and also listens for changes (using bonobo-conf in 1.0/1.2 and gconf in 1.4). -- Dan _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
