Mercurial > pidgin
view PROGRAMMING_NOTES @ 4109:4efc492cf16f
[gaim-migrate @ 4324]
(21:14:00) Robot101: although I just had a thought.... before you commit it, change this:
(21:14:11) LSchiere: ugh
(21:14:24) Robot101: trust me, it's far harder for me to re-diff it :P
(21:14:30) LSchiere: not now it isn't
(21:14:34) LSchiere: what line?
(21:14:53) LSchiere: of the file not the patch
(21:15:05) Robot101: buddy.c 2479
(21:15:22) LSchiere: kay
(21:15:36) LSchiere: gint x, y, width, height;
(21:15:47) Robot101: remove width and height, then remove the call to gtk_window_get_size, and change the
4 occurences of width and height to event.width and event.height
(21:16:13) Robot101: size is not dependent on gravity, so we don't need to get it via gtk.
(21:17:03) LSchiere: any other thoughts?
(21:17:33) Robot101: yes. I'm an idiot.
(21:17:42) LSchiere: you said it, not me.
(21:17:53) deryni: I smell commit message
committer: Tailor Script <tailor@pidgin.im>
author | Luke Schierer <lschiere@pidgin.im> |
---|---|
date | Sat, 21 Dec 2002 02:19:42 +0000 |
parents | e074172f4a41 |
children | 59ff9d0b7b85 |
line wrap: on
line source
Notes on keeping GAIM OS independant ------------------------------------ General ------- - Use G_DIR_SEPARATOR_S and G_DIR_SEPARATOR for paths - Use g_getenv, g_snprintf, g_vsnprintf - Use gaim_home_dir instead of g_get_home_dir or g_getenv("HOME") - Make sure when including win32dep.h that it is the last header to be included. Paths ----- - DATADIR, LOCALEDIR & LIBDIR are defined in wingaim as functions. Doing the following will therefore break the windows build: printf("File in DATADIR is: %s\n", DATADIR G_DIR_SEPARATOR_S "pic.png"); it should be: printf("File in DATADIR is: %s%s%s\n", DATADIR, G_DIR_SEPARATOR_S, "pic.png"); PLUGINS & PROTOS ---------------- - G_MODULE_EXPORT all functions which are to be accessed from outside the scope of its "dll" or "so". (E.G. gaim_plugin_init) - G_MODULE_IMPORT all global variables which are located outside your dynamic library. (E.G. connections) (Not doing this will cause "Memory Access Violations" in Win32)