comparison ChangeLog.API @ 21361:6bbd023f0387

propagate from branch 'im.pidgin.pidgin.next.minor' (head 365b126365cc18309aea7f8eef0e9b2a19e6bda8) to branch 'im.pidgin.cpw.resiak.disconnectreason' (head 75e53ad0238f484c85aa2db94c12cd3f6872f8f6)

21253:ae330012956f

		* purple_plugin_disable(), which is intended to be called when
		  a purple_plugin_unload()--which was called when a user tried
		  to unload a plugin--fails.  This then prevents the plugin
		  from being saved in the saved plugins list, so it'll won't
		  be loaded at the next startup.
		* purple_util_init()
		* purple_util_uninit()

		* pidgin_dialogs_about_with_parent()
		* pidgin_log_show_contact_with_parent()

21361:6bbd023f0387

		* purple_plugin_disable(), which is intended to be called when
		  a purple_plugin_unload()--which was called when a user tried
		  to unload a plugin--fails.  This then prevents the plugin
		  from being saved in the saved plugins list, so it'll won't
		  be loaded at the next startup.

		* PurpleDisconnectReason enumeration of machine-readable
		  types of connection error.
		* purple_connection_error_reason(), to be used by prpls
		  (instead of purple_connection_error() and setting
		  gc->wants_to_die) to report errors along with a
		  PurpleDisconnectReason.
		* PurpleConnectionUiOps.report_disconnect_reason, to be
		  implemented by UIs (rather than .report_disconnect) if
		  they want to use the reported PurpleDisconnectReason
		  to give a more specific error.
		* purple_connection_reason_is_fatal(), acting as a hint
		  to whether automatic reconnection should be attempted
		  after a connection error (rather than checking
		  gc->wants_to_die).

		* purple_util_init()
		* purple_util_uninit()

		* pidgin_dialogs_about_with_parent()
		* pidgin_log_show_contact_with_parent()