Character Counter issue, Suggestions & Request

[GoogleCodeExporter]

Client/Version: Pidgin 2.10.1
LibPurple Version: 2.10.1 
PrplTwtr Version: 0.11.0
Operating System: WinXP

Problem/Feature request (Be as specific as possible. Steps to reproduce are
especially helpful):

Today I downloaded and installed Prpltwtr on my portable version of Pidgin 

--- http://portableapps.com/apps/internet/pidgin_portable ---

I was able to login, authorize prpltwtr and receive tweet updates. With that 
said, I've questions, request & one suggestion.

--Character Counter
The character counter doesn't work, that is base on the tweeter guidelines.

The Counter counts as it should but once the 140 character limit is reached it 
just keeps counting. There is no action/notification that alerts the user of 
surpassing the limit. 

Is this happening to anybody else? 

The counter should be regressive [140-0] Or once it surpasses 140 character the 
text becomes red Or it becomes red & enters a minus status [-141]
--

--Rate Limit
Isn't there anyway to turn off the Rate Limit? Having it shown as the Topic 
keeps activating two Pidgin plugins that are a must for me: 

DiffTopic: Which alerts of a chance in the chat topic & displays exactly what 
was change.

Guification: Guification's alert for Topic Change

Must Rate Limit be displayed as the Topic? Can there be a way to remove it from 
the Topic?
--

--Documentation
I believe there should be more documentation as to what are the best settings 
for prpltwtr, what do the options do, are there any commands that can be use 
from the Chat/IM windows. etc.

I've been looking for these and while a littler messing around with Pidgin can 
get you some answer, it would be nice to have some documentation available, 
specially about Chat/IM commands.
--

Original issue reported on code.google.com by SevenFactors on 8 Feb 2012 at 12:50

[GoogleCodeExporter]

1. The counter should change to orange at 130 characters and red at 140. The 
reason it doesn't cut off is that DMs and responses are automatically split 
into multiple tweets. Note that I don't calculate the length of a tweet 
containing a URL correctly (it should be a fixed 20, currently, because of t.co 
wrapping); detecting a URL in C is a non trivial problem in text processing 
that I haven't tackled yet.

2. Rate limit -- good suggestions. I'll add it to the next release. Note that 
the next release will include some significant refactoring that's taking me a 
bit longer than expected.

3. Documentation -- standard problem. Any suggestions for the most urgent 
things? Or better yet, do you want to write some? ;)

Original comment by mikeage on 8 Feb 2012 at 2:54

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

1-For some reason the Counter doesn't behave as you have described. It never 
changes colors.

2-Thanks for taking my suggestion into account.

3-I can take you on that. I can write some documentation base on what I have 
found so far.

-Manually installing prpltwtr for PortablePidgin
-Explain the layout of prpltwtr and how it uses pidgin
-Chat Vs IM windows
--Who is populating the room.
-The behavior of prpltwtr when replying to a tweet in the timeline [done in a 
new IM window]
-Explain Rate Limit

How would this be done?

--A Question or Two

Are the .dbgsym files a must?
e.g. prpltwtr.dll.dbgsym

Are there any chat/IM window commands? You know, can I start a #search on a new 
tab by just typing on the text box /search #prpltwtr or a direct message /DM 
@prpltwtr

Original comment by SevenFactors on 9 Feb 2012 at 5:14

[GoogleCodeExporter]

I don't know why the counter isn't working for you; I'm a bit swamped at (real) 
work at the moment, but if I don't get back to you within a few days, bug me 
again (or tweet me @prpltwtr) and I can give you a version with insane amounts 
of debug to track it down if you want.

Original comment by mikeage on 9 Feb 2012 at 5:36