Mercurial > pidgin
view PROGRAMMING_NOTES @ 10134:0aca774bef87
[gaim-migrate @ 11198]
Patch 1051145, from Nathan Fredrickson, a rewrite of the smiley selection
dialog:
This patch replaces the smiely selection dialog with a
smiley popup menu. The smileys are still arranged in a
square grid.
Screenshots here:
http://worksintheory.org/files/gaim/smiley-menu/
One outstanding issue is with the yahoo smileys. Some
of them are extra wide, and it seems that pixmap width
affects menuitem height due to gtk's calculation of the
"toggle size". The result is unecesseary vertical
spacing. Not sure whether this is a gtk bug or not.
Even with the extra vertical spacing, which only
effects yahoo smiley's, I prefer this menu to the
original dialog.
committer: Tailor Script <tailor@pidgin.im>
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Sat, 23 Oct 2004 18:07:11 +0000 |
parents | da88e2cd5c53 |
children | 83ec0b408926 |
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)