Mercurial > pidgin
view PROGRAMMING_NOTES @ 8250:b248c1f4efbd
[gaim-migrate @ 8973]
1) Minor changes to the network listen code again. Tim, let me know
if you have any other suggestions.
2) Changed how charsets are handled in oscar a tad bit. I think this
should guarantee that Gaim doesn't crash when people send funky
messages, or have funky away messages or really anything that is
using a charset that isn't utf8, iso-8859-1, ucs-2be, or ascii.
Ethan, this should fix the problem with that person's away message.
Although, the message itself still looks kinda funky to me. The
encoding is Windows-31J, which is apparently a valid iconv encoding?
You would know more than I.
3) Fix the following crash:
1. IM yourself a message on AIM
2. Do NOT begin to type a second message, but instead hit CTRL+up
committer: Tailor Script <tailor@pidgin.im>
| author | Mark Doliner <mark@kingant.net> |
|---|---|
| date | Fri, 13 Feb 2004 05:37:12 +0000 |
| parents | 10b5ac17fdd6 |
| children | da88e2cd5c53 |
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"); - When writing out paths to .gaimrc, use wgaim_escape_dirsep. This is necessary because the Windows dir separator '\' is being used to escape characters, when paths are read in from the .gaimrc file. 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)
