Mercurial > pidgin.yaz
view PROGRAMMING_NOTES @ 4898:bd37db7531e4
[gaim-migrate @ 5230]
I Nathan D. Walped the gaimrc file so that it writes a .gaimrc.save file
and then renames it to .gaimrc, in the hopes of avoiding the loss of this
data in a time that could be crucial to forward progress. Or something.
I tested it with and without specifying -f
I added a "Status: Not Available" (or whatever) string to ICQ tooltips.
This should help at least until we get some new icons. AHEM. And then
I dunno, I was planning on taking it out after that, but it could be
useful.
Also updated some comments and var names in oscar.c to keep things accurate,
because I'm one of those people that actually does that.
Go ask your Goddess if you've served her well
committer: Tailor Script <tailor@pidgin.im>
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Thu, 27 Mar 2003 21:41:21 +0000 |
parents | 59ff9d0b7b85 |
children | 10b5ac17fdd6 |
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. - Open binary files when reading or writing with 'b' mode. e.g: fopen("somefile", "wb"); Not doing so will open files in windows using defaut translation mode. i.e. newline -> <CR><LF> 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)