comparison src/gtkconn.c @ 7431:643cbc9a6035

[gaim-migrate @ 8036] This is good enough for CVS. This is new logging. It centers around the highly modular "GaimLogLogger," which controls how to write the log. Currently I only have the plain text logger. I wrote the beginning of an XML logger, but decided I didn't think it was that great an idea. Plugins can implement loggers themselves, so you can have, like, an SQL logger or something. The default logger writes to a file unique to the conversation, and they're saved on disk in a heirarchical fashion: ~/.gaim/logs/aim/seanegn/robflynn-date.log would be a conversation I had with Rob on date. What doesn't work: System logging The search button in the log viewer. Oh, chats probably don't log either, I didn't test. You can only log in plain text right now. Obviously, it's not done yet. But you can play around with it, and give it some love. I'll get back to it tomorrow after school, maybe. committer: Tailor Script <[e-mail]>

7430:783eea64614c

};
struct disconnect_window *disconnect_window = NULL;

static void disconnect_response_cb(GtkDialog *dialog, gint id, GtkWidget *widget)
{
	switch(id) {
	case GTK_RESPONSE_CLOSE:
		gtk_widget_destroy(disconnect_window->window);
		g_free(disconnect_window);
		disconnect_window = NULL;
		break;
	case GTK_RESPONSE_ACCEPT:
		break;
	}
}

static void disconnect_tree_cb(GtkTreeSelection *sel, GtkTreeModel *model) 

7431:643cbc9a6035

};
struct disconnect_window *disconnect_window = NULL;

static void disconnect_response_cb(GtkDialog *dialog, gint id, GtkWidget *widget)
{
	GaimAccount *account = NULL;
	
	switch(id) {
	case GTK_RESPONSE_CLOSE:
		gtk_widget_destroy(disconnect_window->window);
		g_free(disconnect_window);
		disconnect_window = NULL;
		break;
	case GTK_RESPONSE_ACCEPT:
		
		gaim_account_connect(account);
		break;
	}
}

static void disconnect_tree_cb(GtkTreeSelection *sel, GtkTreeModel *model)