Mercurial > pidgin
view m4/artsc.m4 @ 12645:fc28451f5d96
[gaim-migrate @ 14983]
SF Patch #1314512 from Sadrul (who has a patch for everything)
"This patch introduces a flag for protocol plugins that
support offline messages (like Y!M and ICQ). This was
encouraged by the following conversation:
<sadrul> should offline buddies be listed/enabled in
the send-to menu?
<rekkanoryo> i would think only for protocols that
support offline messaging, if it's indicated that the
buddy is offline
-- <snip> --
<Bleeter> sadrul: personally, I'd like to see a
'supports offline' flag of some description
<Bleeter> one could then redirect (via plugins) through
email or alternative methods
<Bleeter> just a thought
<Paco-Paco> yeah, that sounds like a reasonble thing to have
This patch uses this flag to disable the buddies in the
send-to menu who are offline and the protocol doesn't
support offline messages."
I made this make the label insensitive instead of the whole menuitem. This
should address SimGuy's concerns about inconsistency (i.e. you could create a
conversation with someone via the buddy list that you couldn't create via the
Send To menu). I also hacked up some voodoo to show the label as sensitive when
moused-over, as that looks better (given the label-insensitive thing is itself a
hack). I think this works quite well.
BUG NOTE:
This makes more obvious an existing bug. The Send To menu isn't updated when
buddies sign on or off or change status (at least under some circumstances).
We need to fix that anyway, so I'm not going to let it hold up this commit.
Switching tabs will clear it up. I'm thinking we just might want to build the
contents of that menu when it is selected. That would save us a mess of
inefficient signal callbacks that update the Send To menus in open windows all
the time.
AIM NOTE:
This assumes that AIM can't offline message. That's not strictly true. You can
message invisible users on AIM. However, by design, we can't tell when a user
is invisible without resorting to dirty hackery. In practice, this isn't a
problem, as you can still select the AIM user from the menu. And really, how
often will you be choosing the Invisible contact, rather than the user going
Invisible in the middle of a conversation or IMing you while they're Invisible?
JABBER NOTE:
This assumes that Jabber can always offline message. This isn't strictly true.
Sadrul said:
I have updated Jabber according to this link which seems to
talk about how to determine the existence offline-message
support in a server:
http://www.jabber.org/jeps/jep-0013.html#discover
However, jabber.org doesn't seem to send the required
info. So I am not sure about it.
He later said:
I talked to Nathan and he said offline message support is
mostly assumed for most jabber servers. GTalk doesn't yet
support it, but they are working on it. So I have made
jabber to always return TRUE.
If there is truly no way to detect offline messaging capability, then this is
an acceptable solution. We could special case Google Talk because of its
popularity, and remove that later. It's probably not worth it though.
MSN NOTE:
This assumes that MSN can never offline message. That's effectively true, but
to be technically correct, MSN can offline message if there's already a
switchboard conversation open with a user. We could write an offline_message
function in the MSN prpl to detect that, but it'd be of limited usefulness,
especially given that under most circumstances (where this might matter), the
switchboard connection will be closed almost immediately.
CVS NOTE:
I'm writing to share a tragic little story.
I have a PC that I use for Gaim development. One day, I was writing a commit
message on it, when all of a suddent it went berserk. The screen started
flashing, and the whole commit message just disappeared. All of it. And it was
a good commit message! I had to cram and rewrite it really quickly. Needless to
say, my rushed commit message wasn't nearly as good, and I blame the PC for that.
Seriously, though, what kind of version control system loses your commit
message on a broken connection to the server? Stupid!
committer: Tailor Script <tailor@pidgin.im>
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Fri, 23 Dec 2005 19:26:04 +0000 |
parents | 64d8ef561763 |
children |
line wrap: on
line source
dnl Test for the ArtsC interface. AC_DEFUN([AM_PATH_ARTSC], [ AC_ARG_ENABLE(artsc-test, [ --disable-artsc-test Do not compile and run a test ArtsC program.], [artsc_test="yes"], [artsc_test="no"]) dnl Search for the arts-config program. AC_PATH_PROG(ARTSC_CONFIG, artsc-config, no) min_artsc_version=ifelse([$1],,0.9.5,$1) AC_MSG_CHECKING(for ArtsC - version >= $min_artsc_version) no_artsc="" if test "x$ARTSC_CONFIG" != "xno"; then ARTSC_CFLAGS=`$ARTSC_CONFIG --cflags` ARTSC_LIBS=`$ARTSC_CONFIG --libs` artsc_major_version=`$ARTSC_CONFIG $artsc_args --version | \ sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\1/'` artsc_minor_version=`$ARTSC_CONFIG $artsc_args --version | \ sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\2/'` artsc_micro_version=`$ARTSC_CONFIG $artsc_config_args --version | \ sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\3/'` # Test if a simple ArtsC program can be created. if test "x$artsc_test" = "xyes"; then ac_save_CFLAGS="$CFLAGS" ac_save_LIBS="$LIBS" CFLAGS="$CFLAGS $ARTSC_CFLAGS" LIBS="$LIBS $ARTSC_LIBS" rm -f conf.artsc AC_TRY_RUN([ #include <stdio.h> #include <stdlib.h> #include <string.h> #include <artsc.h> char* my_strdup(char *str) { char *new_str; if (str) { new_str = malloc((strlen(str) + 1) * sizeof(char)); strcpy(new_str, str); } else { new_str = NULL; } return new_str; } int main() { int major, minor, micro; char *tmp_version; system ("touch conf.artsc"); /* HP/UX 9 writes to sscanf strings */ tmp_version = my_strdup("$min_artsc_version"); if (sscanf(tmp_version, "%d.%d.%d", &major, &minor, µ) != 3) { printf("%s, bad version string\n", "$min_artsc_version"); exit(1); } if (($artsc_major_version > major) || (($artsc_major_version == major) && ($artsc_minor_version > minor)) || (($artsc_major_version == major) && ($artsc_minor_version == minor) && ($artsc_micro_version >= micro))) { return 0; } else { printf("\n*** 'artsc-config --version' returned %d.%d.%d, but the minimum version\n", $artsc_major_version, $artsc_minor_version, $artsc_micro_version); printf("*** of ARTSC required is %d.%d.%d. If artsc-config is correct, then it is\n", major, minor, micro); printf("*** best to upgrade to the required version.\n"); printf("*** If artsc-config was wrong, set the environment variable ARTSC_CONFIG\n"); printf("*** to point to the correct copy of artsc-config, and remove the file\n"); printf("*** config.cache before re-running configure\n"); return 1; } } ],, no_artsc=yes,[echo $ac_n "cross compiling; assumed OK... $ac_c"]) CFLAGS="$ac_save_CFLAGS" LIBS="$ac_save_LIBS" fi else no_artsc=yes fi if test "x$no_artsc" != "xyes"; then AC_MSG_RESULT(yes) ifelse([$2], , :, [$2]) else AC_MSG_RESULT(no) if test "x$ARTSC_CONFIG" = "xno" ; then echo "*** The artsc-config script installed by ArtsC could not be found" echo "*** If ArtsC was installed in PREFIX, make sure PREFIX/bin is in" echo "*** your path, or set the ARTSC_CONFIG environment variable to the" echo "*** full path to artsc-config." else if test -f conf.artsc ; then : else echo "*** Could not run ArtsC test program, checking why..." CFLAGS="$CFLAGS $ARTSC_CFLAGS" LIBS="$LIBS $ARTSC_LIBS" AC_TRY_LINK([ #include <stdio.h> #include <artsc.h> ],[return 0;], [ echo "*** The test program compiled, but did not run. This usually means" echo "*** that the run-time linker is not finding ArtsC or finding the wrong" echo "*** version of ArtsC. If it is not finding ArtsC, you'll need to set your" echo "*** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point" echo "*** to the installed location Also, make sure you have run ldconfig if that" echo "*** is required on your system" echo "***" echo "*** If you have an old version installed, it is best to remove it, although" echo "*** you may also be able to get things to work by modifying LD_LIBRARY_PATH"], [ echo "*** The test program failed to compile or link. See the file config.log for the" echo "*** exact error that occured. This usually means ArtsC was incorrectly installed" echo "*** or that you have moved ArtsC since it was installed. In the latter case, you" echo "*** may want to edit the artsc-config script: $ARTSC_CONFIG" ]) CFLAGS="$ac_save_CFLAGS" LIBS="$ac_save_LIBS" fi fi ARTSC_CFLAGS="" ARTSC_LIBS="" ifelse([$3], , :, [$3]) fi AC_SUBST(ARTSC_CFLAGS) AC_SUBST(ARTSC_LIBS) rm -f conf.artsc ])