Opened 11 years ago

Last modified 8 years ago

#5034 new enhancement

Please bring back the 2.3.1 typing indicator!

Reported by: Arvedui Owned by:
Milestone: Plugin Suggested Component: pidgin (gtk)
Version: 2.4.0 Keywords: animated typing indicator
Cc: juba

Description

The 2.3.1 animated typing icon in the upper-right corner was much more useful than the in-line notification, especially since it showed typing-pauses in an eye-catching, graphical way. Its corner placement was also nice for positioning windows in front of each other, to save screen-space and still be able to see at a glance which one might be in the process of responding. That's much harder to notice when it's a line of text in the actual window.

Please bring back the typing icon, either alone or in conjunction with the new "<name> is typing" line in the message window, or put an option in the preferences to be able to choose one or the other, or both. I'm seriously considering reinstalling and sticking with 2.3.1 for the old indicator alone.

Change History (60)

comment:1 Changed 11 years ago by nunop

I also think the 2.3.1 animated typing icon was a better choice (from a usability point of view). I agree with everything Arvedui said before. I find this new way dificult to notice.

An option under the preferences->interface to choose one or the other or both or none wold be nice.

thank you.

comment:2 follow-up: Changed 11 years ago by hbons

The position of the old typing notification was worse, you are right about the pause notification, but that can be implemented now too. The position of the old notification looks totally random and makes no sense, having it at the end of the conversation, where your focus usually is when actively in the conversation, is better usability.

comment:3 Changed 11 years ago by datallah

  • Component changed from winpidgin (gtk) to pidgin (gtk)
  • Owner datallah deleted

comment:4 in reply to: ↑ 2 Changed 11 years ago by nunop

Replying to hbons:

The position of the old notification looks totally random and makes no sense, having it at the end of the conversation, where your focus usually is when actively in the conversation, is better usability.

The old notification makes sense to me. If you assume that both you and your contact are just chatting (and doing nothing else), then ok, I agree with you. But generally I am doing some other things, and if the other person takes a bit longer to reply, I am no longer focused in the chat window, I just glance it as Arvedui wrote. And in those contitions the corner of the window is much more noticeable.

Beside that I get a bit confused when i'm writing and the other person starts typing for a fraction of a second I wonder if that's a reply and I think - "oh no, it's just the notification" a sec later it is a reply in the exact same place. It awful, imo.

comment:5 Changed 11 years ago by hbons

If you assume that both you and your contact are just chatting (and doing nothing else), then ok, I agree with you.

Well, Pidgin was made to do just that. You can still align your window so that the new typing notification is seen when your conversation window is not active, so that's not a valid argument for the old place of the notification (And the tab color still changes to green). I agree that its color is not very eye catching but so wasn't the color of the old typing icon. I am for finding a better default color, or take the color from the GTK theme.

comment:6 Changed 11 years ago by deryni

Placing windows so that the bottom of the history area sticks out when the rest of the window doesn't is significantly less feasible than doing the same with the top right corner. That being said the tabs are generally more useful for that feature (and is in fact exactly why I use side tabs when I am in Windows).

comment:7 Changed 11 years ago by kepplah

I think the typing notification would work well on the tabs, so I can see if someone is typing in one of my conversations that is not the current active one.

I liked the pause detection the icon provided, but the location in 2.4 makes sense too.

comment:8 Changed 11 years ago by deryni

Tabs *do* indicate typing notification, that's what the "green" and "yellow" mean.

comment:9 Changed 11 years ago by kepplah

I've never seen a yellow dot. It's always green. I only use AIM and IRC. The old keyboard looking icon used to work in AIM.

comment:10 Changed 11 years ago by nunop

it's not the dot, it's the name of the contact.

A good solution to please everyone is to make both options available and configurable. :)

comment:11 Changed 11 years ago by deryni

A plugin could likely be written to create the corner typing notification icon, I imagine one or two of the plugin pack plugins will likely provide good examples of how to do that.

comment:12 Changed 11 years ago by Apewall

I'm not sure the new behavior makes any more sense then the old one.

Typing notifications in the conversation window really has nothing to do with the conversation that is going on, and just clutters the conversation window while your friend slams away at his keyboard and edits their text repeatedly.

I thought the "detailed information bar" was more logical if anything, as typing is not NEED TO KNOW information vital to the chat.

Pidgin's older icon system for notifying while not in line with other chat programs, provided a much less cluttering way of notifying the user of the event.

Personally I prefer using tabs for seeing the notification.

comment:13 Changed 11 years ago by fumo7887

The fact that this debate exists should be enough to back up the suggestion that somebody already made... make it a user option. I, for one, prefer the old-style notification. This allows me to keep just the right edge of the IM window visible behind whatever I'm doing to look for the icon. With the new system, I can't do the same and need to keep the whole window visible. I can understand why some people would like the new one, but with so many supporting the old one, why can't we have the best of both worlds... or at least the choice between both worlds?

comment:14 Changed 11 years ago by tibormolnar

I also agree that this should be configurable.

I personally found the old-style indicator nice and useful, even though the existence of the mere notification is not vital for me.

On the other hand, the new-style in-line indicator I found so frustrating that I downgraded back to 2.3.1. Every time my chat buddy starts typing someting, the "user is typing" line appears in the conversation window and catches my attention because it seems as if a new message was received.

I would be grateful for any kind of solution that enables me to switch off the in-line indicator - whether along with swtiching on the old-style icons or not.

comment:15 Changed 11 years ago by AishaDracoGryph

I just hope this does not become another issue like protocol icons that the purple team attempts to just out right ignore it's users about until someone has to go and do the work for them

comment:16 Changed 11 years ago by misch

I agree with the original poster. The inline typing notification is annoying. If I'm trying to catch up on a conversation with a person, the "X is typing" notification moves the text I am reading.

Text on the screen should not move unless a new message is entered from the local user or the remote message contact.

Please bring back the old icon-based style, or make it text, but put it outside the in-line message box.

I cannot think of another messaging client that does it this way.

comment:17 Changed 11 years ago by AishaDracoGryph

well to be honest, MSN messenger does it that way, just seems silly to implement a new method for doing something that was not in need of being fixed.

not broken don't fix it.

comment:18 Changed 11 years ago by deryni

  • Milestone set to Plugin Suggested

The fact that a number of people asked for this new notification combined with the fact that a large number of official and third-party clients do this (and are touted by their users as wonderful) was a reason to do this. While it was indeed the case that the previous method was not broken (whereas the protocol icons in fact were, but that's a discussion I don't want to have again) it is not therefore the case that a change is not in order. While the idea that you shouldn't change things that aren't broken has merit the extent to which our usesr would like us to adhere to it would make any forward motion impossible (as there is always someone who likes any given feature/bug/unintended consequence/etc. of pidgin regardless of whether it is actually a good idea or not). Stagnation is not something that is helpful to anyone, least of all users (developers included). I sympathize with the people who dislike the new notification method and would not object to it being made into a plugin (though I believe a plugin could just hide the current text as well). Likewise, a plugin could add back the typing notification menu-tray icon. As with the protocol icons we welcome any such plugins, perhaps not for inclusion but there is a wiki page for plugins for reasons exactly like this.

comment:19 follow-up: Changed 11 years ago by AishaDracoGryph

ahh but what you do not realize is just as with the protocol icons, this was an option that should be considered, and your user base is asking for the "option" forward thinking is also about not forgetting past features that arguably a large number of users would like to at least have the option to use.

If you were so inclined to let all of this be relegated to plugins, why did you bother including the protocol icon mod? because the users wanted it. My earlier statement still applies, it seems that something so simple is beyond the purple team's ability to code and thus they allow others to do the work for them.

users like forward thinking but also do not like being ignored either, and not many if any have asked for the new typing indicator method to be removed, we simply want the old indicator as an option.

comment:20 follow-up: Changed 11 years ago by Apewall

Why are we emulating other messenger's mistakes like MSN?

I'm really getting bored of the "Someone should make it a plugin" attitude. The point is to have the default behavior be optimal, where as currently it is far from. Making such changes because other current messengers have them is a poor excuse to base a decision on for what Pidgin's default behavior should be.

I'm getting tired of explaining to people who have used Pidgin before or are moving to Pidgin to turn on multiple plugins to get what I(and they) feel should be default behavior.

I consider the current typing notification still a fault in design.

comment:21 in reply to: ↑ 19 Changed 11 years ago by deryni

Replying to AishaDracoGryph: Requesting that people who actually want the code write a plugin is allowing for it to be added as an option. We are very much attempting not to forbid anything. I didn't include the protocol icon patch, and in fact I fought against including it as a patch, and told the author he should make it a plugin, other people decided to accept it. None of these things is beyond us, we just don't want them so we choose not to spend our time on them. No matter how many times people demand things if we don't see the point or merit in them we are under no obligation to spend our time on them. We at all points attempt to make it possible for people who *do* care to make pidgin work the way they want it to work (and have more than once in the past added signals for which we had no usage simply because someone said "I need signal X to make a plugin to do Y").

Your assertion is that the only correct way to be "forward thinking" is to make only changes that do not remove anything that has ever existed (because someone or some people might want it that way) that is not in the slightest a viable option.

comment:22 in reply to: ↑ 20 Changed 11 years ago by deryni

Replying to Apewall:

Why are we emulating other messenger's mistakes like MSN?

We aren't, we are however trying to emulate the successes of other clients (especially the ones that we hear people praising frequently and requesting that we support).

I'm really getting bored of the "Someone should make it a plugin" attitude. The point is to have the default behavior be optimal, where as currently it is far from. Making such changes because other current messengers have them is a poor excuse to base a decision on for what Pidgin's default behavior should be.

I'm sorry you are tired of a perfectly reasonable and incredibly useful attitude, but that isn't going to change the fact that it is still an attitude we like and want to support.

You believe that having an option for the typing icon (or having it on without an option) is optimal, we don't. It really is that simple. We removed it because we didn't see the need to have three typing notifications when we felt two would do. It is intentionally still possible to have the typing icon added by a plugin and we have encouraged people who want it back to do so (most of the code can likely be pulled straight out of pidgin 2.3.1 and stuffed into a plugin with the right signals).

We do not make changes just because other clients are doing things, if we did pidgin would be a hell of a lot more bloated and contain a hell of a lot less useful features. It would also likely not be written in C or core/ui split or any of those other nice things that make pidgin work so well.

I'm getting tired of explaining to people who have used Pidgin before or are moving to Pidgin to turn on multiple plugins to get what I(and they) feel should be default behavior.

Ah but therein lies the rub, it is, in general, more difficult to write a plugin to *disable* a given default behaviour than it is to *enable* a behaviour; and it often works less well. For example in the case at hand, a plugin to add the icon needs to listen on a couple of signals, add the icon, and keep it updated. Were the icon to be in pidgin (without an option) the plugin would need to listen to some of the same signals and hide the icon (an icon that pidgin would be continuously updating for no reason as no one will ever see it). So adding features with plugins really tends to be more reasonable then going the other way.

Which plugins (other than this one) do you and those people you refer to do you feel should be default behaviour? And why?

I consider the current typing notification still a fault in design.

Why? What about it is a fault in your eye/mind?

comment:23 Changed 11 years ago by amishmm

Just to add weightage to the ticket request. Even I personally think that old typing notification was much better.

Honestly, when I first saw the new way of notification, I was like, ah nice idea! But as I started chatting, within five minutes it became annoying to me.

"It was repeatedly causing confusion, disturbance and making my eyes READ it and making my brain KNOW every second that my friend is TYPING, when I was not interested in knowing! Every second eye reads it and brain realises that its just a notification and then throws it out!"

My brains so many CPU cycles are getting wasted and its getting so many unwanted interrupts! :-p

Earlier I cud simply glance on top right corner, if I wanted to know that.

I do understand that there are people who like the new way but same way there are people who like the old way. So I request instead of making/waiting for a plugin for it, it shud be direct option in Pidgin. Old code is there. New code is there. With due respect to developers, I think just for one 'if' condition we cant develop a new plugin.

comment:24 in reply to: ↑ description Changed 11 years ago by fractos

I'd really like to see the "old style" 2.3.1 typing indicator allowable as an option as I too find the "x is typing" indicator incredibly irritating and a step backwards in terms of design. I understand and appreciate that other, more successful messengers (although they may have a captive audience) use the "new style" indication, but I and it seems many others just from looking at this thread believe that the 2.3.1 style was better and should be available as an option.

My opinion on the design is that the conversation window should be a track of "what has been", not "what might be". The fact that someone is typing is out of context of the content of the conversation. Furthermore I support the opinion of amishmm where they say that it takes more brain cycles to process the information. A symbol in the top right corner was optimal for this process. Having the first few lines of a conversation window visible is not, especially when the indicator text is replaced by the sent message. My eyes simply do not register the change in the same way and I will definitely be sticking to 2.3.1 until this is resolved in some way.

comment:25 Changed 11 years ago by AishaDracoGryph

"Your assertion is that the only correct way to be "forward thinking" is to make only changes that do not remove anything that has ever existed (because someone or some people might want it that way) that is not in the slightest a viable option."

My assertion is, that the best way to think forward, is to add new features and options and keep features and options that users like and find useful. and not treat their uses like they don't matter. By keeping old features and options, I of course mean not removing anything that a significant portion of your user base find usefully and at least keeping them as an optional component.

I can only imagine Microsoft taking a similar stance and not including support for old usb 1.0 devices or midi sound format, hell why not forget MS dos support, that's old right? BMP is an out dated format for images, oh and while we are at it we can just forget ps2 ports for peripherals. Oh and what about penicillin, they sure have new forms of antibiotics, we sure don't need that.

all you need to do stop releasing public versions of Pidgin and state that your now coding it solely for your personal use and I'll shut up, but the fact is you at least claim your coding this for "us as well" and if it's for us too, we at least ask you listen to us when we ask for something, honestly not very difficult.

Asking for someone else to make a plugin is fine, but you do not seem to have a place for users to upload plugins, so even if someone does make a plug in we are not likely to notice it.

their is a big disadvantage to loading up 50 plugins to re-enable features that were already hard coded into the program to begin with, and that is it uses ram, and one of Pidgin's strong points is it uses little ram.

he bottom line here is, you can be forward thinking without forgetting to look behind you and make sure your not leaving anyone off the bus.

comment:26 follow-up: Changed 11 years ago by amishmm

I wud say, I do not see anything in this matter, that has anything to do with "forward thinking".

This is user interface (UI) related option and nothing to do with "something better". Some find old way better and some new way. Its an individual choice.

Mercedes can come up with new car with new engine (libpurple) but it wud still provide with same color range (Pidgin). It wud not say, that ok people now like black color more so just stop providing silver Mercedes.

comment:27 in reply to: ↑ 26 Changed 11 years ago by AishaDracoGryph

Replying to amishmm:

I wud say, I do not see anything in this matter, that has anything to do with "forward thinking".

This is user interface (UI) related option and nothing to do with "something better". Some find old way better and some new way. Its an individual choice.

Mercedes can come up with new car with new engine (libpurple) but it wud still provide with same color range (Pidgin). It wud not say, that ok people now like black color more so just stop providing silver Mercedes.

or for that matter, them saying "no more cup holders, the wave of the future is beer hats in your car!"

comment:28 Changed 11 years ago by varchar255

cc

comment:29 Changed 11 years ago by andrixnet

My vote is bring back the 2.3.1 typing notification.

A few notes on the new one :

  • tab color in 2.4.1 does not change to indicate "typing notification"
  • if I send a message while the other is typing, the typing notification is replaced by my message

comment:30 Changed 11 years ago by andrixnet

on tab color I mean "active tab". I make a point of it, because of the second detail

comment:31 Changed 11 years ago by dawg

The old icon was AMAZINGly useful. The new way is a good idea, but there should definitely be an option for each method. The old way is a lot better. It is all but impossible to notice when the other user starts and stops typing...

comment:32 Changed 11 years ago by yip0815

Let me add another vote for the old typing icon. It was a great indicator and it's the only reason I'll be going back to 2.3.1 immediately after hitting "submit"! Please remove this god-awful textline or at least make it an option.

comment:33 Changed 11 years ago by AishaDracoGryph

I thought Pidgin (gaim at the time) was unique and innovative for having a different typing indicator among other things, I sure hope this habit and behavior of mimicking other clients to the point of removing useful and desirable features that a huge part of the user base is asking in some cases begging for, will not continue, because once pidgin becomes just like every other client then why even bother?

comment:34 Changed 11 years ago by BrokenForks

I think that the new typing indicator is a step backwards as it's functionality is greatly less than that of it's predecessor. The old style typing indicator didn't have anything wrong with it. It is also plain to see here that a decent piece of the community on this website does not enjoy the new typing indicator (This is currently the plugin ticket with the most comments)

Would a check box option be that hard to do considering the response that this topic has had from the community of users?

comment:35 Changed 11 years ago by fractos

Hi, I see from the changelog for 2.4.2 that you can now customise (font etc) the typing indicator, but I'm very disappointed to not see the option for the animated icon available. Did I miss something? Can I do that with the customisation? I must admit that I've not played with the .gtkrc file before. What's happening?

comment:36 follow-up: Changed 11 years ago by deryni

No, adding back the typing icon can not be done via the gtkrc file, but can be done with a plugin (and has always been possible with a plugin).

comment:37 in reply to: ↑ 36 Changed 11 years ago by fractos

Replying to deryni:

No, adding back the typing icon can not be done via the gtkrc file, but can be done with a plugin (and has always been possible with a plugin).

Please could you tell me which plugin?

comment:38 Changed 11 years ago by deryni

I don't know that one exists for it at the moment.

comment:39 Changed 11 years ago by tibormolnar

Sorry, if this is a lamer question, but could you guys please help me with step-by-step instructions on how to disable the inline typing indicator? It completely drives me crazy... :(
The changelog for 2.4.2 mentions that it can be disabled, but I just can't figure out how. Many thanks!

comment:40 Changed 11 years ago by fractos

Okay, downloaded new version, checked out the release notes, can't seem to remove the MSN style typing indicator - how do I do this?

Oh, and does anyone fancy writing the legendary plugin to bring back the old indicator please? I'll buy them several pints of good quality beer or equivalent.

Meantime, back to 2.3.1 ... :(

comment:41 Changed 11 years ago by deryni

You need to use the relevant section of the Sample gtkrc file.

comment:42 Changed 11 years ago by Nukkels

I'll sign this petition too. Due to ICQ changing something, I had to update to a newer version of Pidgin and get greeted with this PITA.

Pros:

  • it's in the text window which *might* be useful to some people

Cons:

  • it's in the text window which doesn't help if they're a slow/intermittent typist
  • the missing icon at the top
  • lack of buddy name colour indication
  • difficult to notice (could add bold/colour/bg)
  • bumps up the text one line

comment:43 Changed 11 years ago by fr1a1nky

I also can just agree with the majority, the old typing notification was much more usefull:

old version: + shows typing rate + L=> estimated text length + good indication of typing pauses + usefull position (IMHO) + nice amusement while waiting for a response ;)

  • ?

new version: + ?

  • disturbs while reading text (IMHO)
  • easy to miss, because your view is rarely at the bottom of a window (IMHO)

So,at least, there should be the option to choose. Can't see the point why therefore a plugin is neccessary. But it seems I still have to use 2.2.1 for some time...

comment:44 follow-up: Changed 11 years ago by deryni

Nukkels: What do you mean "lack of buddy name colour indication"? Do you mean the buddies name in the typing indicator isn't colored? Why would you want that? Also the typing notification was intentionally made subtle so that it could be ignored when desired and so it wouldn't be confused with a new message sent by the buddy.

fr1a1nky: The speed at which the keys were 'pressed' in the old typing icon was not an indication of the speed your buddy was typing, pidgin gets no such notifications.

Similarly it provided no indication of pauses that the current indicator doesn't also provide (unless the new indicator doesn't indicate typing-stopped in which case that is a bug and needs fixing).

I'm not sure how you think it gave an indication of estimated text length so I can't really respond to that.

The previous position was useful under certain circumstances and the new position is useful under certain circumstances. Which circumstances occur more often in general I do not know.

The fact that the typing notification does not have a line reserved for it is something that has been discussed a number of times but no one has put forth a really good argument for forcibly stealing a line of scrollback at all times. The current typing notification is disable-able via some gtkrc file tweaks (I posted a link to an example gtkrc with the necessary bits a couple comments ago). And we have repeatedly suggested that someone recreate the old notification as a plugin (which is why the milestone on this ticket is Plugin Suggested).

A plugin is suggested because it doesn't require a patch, it doesn't require us to maintain a feature we don't want or use, and it means it can be expanded as needed by the people who do want and use it to do the things they want it to do.

comment:45 Changed 11 years ago by Nukkels

deryni: I mean when the buddy was typing their named appeared in green, and when they had sent the message it appeared in red. This was useful with multiple buddies in tabs across the top, since the old icon didn't show who was typing, just that one of the buddies in an open tab was.

Please correct me if I'm wrong here, but there weren't hundreds of requests saying that the old one sucked and needed to be changed were there? There ARE hundreds of requests saying this new ones sucks - if it's not broke, don't fix it... So why did you try and fix it?

The simplest solution to this problem is to have a drop down box in the preferences (of the next version) if you really are dead set on keeping this new feature, a plugin is not the answer because a lot of people might upgrade Pidgin from a very old version and then hate it and so give up without trying to install plugins to fix it.

I've already rolled back to using 2.3.1 and have crippled myself by having no access to the ICQ network any more. Also some of the new plugins no longer work, but that's not a huge loss. This should give you some indication how serious the problem is - when people are reverting back to older, crippled versions to get away from it, you know something is wrong.

comment:46 Changed 11 years ago by deryni

The color changing of the tab labels still exists, the infopane does not however change colors. So with a single tab you will not see the color changing as the tab is hidden to reduce the amount of duplicate information on screen.

There were a large number of requests for an iChat/Google Talk style typing notification, how many I don't know as I didn't count. No, there aren't "hundreds" of requests for the old icon back, and every single person who has requested the icon back is free to create the exact same plugin I would be likely to create at this point if I was going to add this feature.

Your assumption is that there wasn't a reason to remove the old icon and that there wasn't a reason to add the new notification. You are wrong on both of those counts. A number of people (a small number I'll grant) didn't like the icon. A number of people (as I stated a moment ago) wanted the new notification. The old icon was not disable-able (which would could have fixed without removing it entirely, I'll grant) the new notifications are. More plugins, especially for features not everyone wants is a good thing.

A plugin is a fine solution, if people hate the lack of the icon so much they are so infuriated that they don't bother to go look for ways to get it back I'm not exactly eager to go out of my way to cater to them. As opposed to people who do come to look for a solution to whom I am more than willing to explain and give help (but I'm not writing code for a plugin I have no intention of using, I don't have that kind of time).

Adding a dropdown in the preferences is in no real way a better option than a plugin and is in at least one way worse, it doesn't allow people to choose both. And before you say "well ok then use checkboxes then" I'll say that's exactly why I want a plugin. I'd even likely vote for including a cleanly written, simple plugin to bring the icon back in pidgin directly if the author wanted us to do that.

Yes, something is wrong. You, and the handful of people like you who want the behaviour back, are unwilling to put forth the work necessary to bring it back. You want us to do the work for you because you ask us to. Thankfully, you have no idea how much I thank you for this, you haven't resorted to the sort of rampant name-calling and insulting that the manual resize 'champions' resorted to.

As I said, I am more than happy to assist anyone who is attempting to write the typing notification icon plugin with whatever assistance they need, but I am not going to write the code myself. The other pidgin developers are likely to also be more than willing to answers any questions asked, either on the devel mailing list or in the pidgin chatrooms.

comment:47 Changed 11 years ago by Nukkels

Cheers for the explanation =}

I'm willing to put forward some effort to help, but my coding skills aren't exactly what they should be (I'm more of a hardware guy). I'd be happy to take a look at code, beta test or whatever you might need me to do, but honestly I'm just not up to writing code at this level.

I guess I'm a firm believer in the "if it isn't broken, don't fix it" school of thought, but if there really was public outcry wanting to change it, then obviously it's what the majority want and a plugin to give the old notifications back is a fine solution.

comment:48 Changed 11 years ago by amishmm

Can we know if the decision to remove "old typing indicator" was taken by joint decision of all developers or it was taken by one single person?

Thanks in advance.

comment:49 in reply to: ↑ 44 Changed 11 years ago by fr1a1nky

fr1a1nky: The speed at which the keys were 'pressed' in the old typing icon was not an indication of the speed your buddy was typing, pidgin gets no such notifications.

You're rigth. So this turns into an argument pro the new notification, because it does not provide this "extra" information. Anyway it would be nice to have such an indicator ;D

comment:50 Changed 11 years ago by deryni

I can't with any honesty claim that either side of this argument has a majority. I can only say that we did get requests for the new notification method (and I don't recall ever seeing anyone comment about liking the icon, whereas people have commented about liking the new notification (though not at all many)). I forget which plugins in the purple plugin pack have a menu tray icon (though I believe the xmms remote plugin does). Whichever plugin that is would likely be a good start for reading up on what is needed to write a plugin which adds an icon there. Responding to the typing notification signals is the easy part. I may (with no certainty whatsoever) sit down to work on this (and some other things) when I find time to start working on pidgin again more actively in the (hopefully) near future.

I do not recall what the breakdown was regarding adding the new notification and/or removing the old notification but that is largely unimportant at this point. I don't think the current system is likely to change again anytime soon.

While it might be nice (I have my doubts as to whether it actually would be) to have information about typing speed/etc. I know of no protocol which actually sends anything remotely resembling the information necessary for pidgin to display that. There are some protocols which do send the entered text character-by-character (meaning you see what your friend is typing in real time) but that's about as close as things are likely to get.

comment:51 Changed 10 years ago by juba

I've tried that with the .gtkrc file, it doesn't work (It know that it reads the file since it prints warning messages when I write crap into it. But the annoying "xy is typing" stays.)

comment:52 Changed 10 years ago by deryni

What exactly did you put in your .gtkrc-2.0 file (or the ~/.purple/gtkrc-2.0 file) the settings do work, so you probably just got something slightly incorrect.

comment:53 Changed 10 years ago by juba

~$ cat .gtkrc-2.0
# Disable the pidgin typing notification
style "no-typing-notification" {
    GtkIMHtml::typing-notification-enable = 0
}
widget_class "*" style "no-typing-notification"




include ".gtkrc-2.0-gnome-color-chooser"

(the last one was added automatically recently)

comment:54 Changed 9 years ago by luigifab

For the 2.3.1 animated typing icon, what's new ?

comment:55 Changed 9 years ago by fractos

Sadly I've not heard anything new on this. 2.3.1 startup is now quite broken on my PC as it complains that "name changes too rapidly" on MSN accounts which is a headache.

I'm very disappointed in the response that this ticket has received. I'd really like to see the animated typing icon indicator back as an option. If this is possible via a plugin then all well and good - but could someone with a bit more knowledge write this, please? I feel strongly about this so if someone can do it to the same effect as 2.3.1 then I'll happily donate money to a favourite charity.

comment:56 Changed 9 years ago by luigifab

For the new year a plugins will appear ? Please...

comment:57 follow-up: Changed 9 years ago by luigifab

Hey ! I find a software called Carrier or Fun Pidgin, with the 2.3.1 typing indicator :p

http://funpidgin.sourceforge.net/content/features « Two different ways of seeing that your buddies are typing. »

comment:58 in reply to: ↑ 57 Changed 9 years ago by fractos

Replying to luigifab:

Hey ! I find a software called Carrier or Fun Pidgin, with the 2.3.1 typing indicator :p

http://funpidgin.sourceforge.net/content/features « Two different ways of seeing that your buddies are typing. »

Yep that's absolutely brilliant! Goodbye, Pidgin. Thanks for ignoring our requests and not wanting to give us an _Option_, which was the whole idea of why I switched to Gaim in the first place.

Ciao.

comment:59 Changed 9 years ago by luigifab

But there is a problem, the new tab in the preferences window isn't added by a plugin. And I haven't found an amd64 deb on the website...

comment:60 Changed 8 years ago by luigifab

What's new ?

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!