[sip-comm-dev] comments after almost a week of usage


#1

Hello,

I've been using siip communicator and I have a few comments, if you
consider these are issues to be solved I volunteer to create the
corresponding issues and try to fix them.

1. I think that messages are not necessarily sent in the order they
where written, they should probably be queued by the core before
passing them to the protocol implementation.

2. The font in the place to write is different from the place where it
is shown, it might be good to use the same font.

3. The legend showing date and time should probably not be shown on
every message. sometimes people write more than one message without
getting a response and with this text it is difficult to read. It
would probably be convenient to wait a few minutes after the writing
stops to print it. It might also be good to use a font color which
doesn't distract from the content, e.g. light gray.

4. It might be useful to have a button on the chat window to clear the
history, just to give the user the option to clean the panel to
facilitate reading.

5. SIP communicator sends lots of notifications of typing, Facebook
servers don't like getting lots of messages, they ask to refresh the
session when it happens, i.e. getting sent messages by requesting the
history and connect again to request newer messages.

6. Show the number of online buddies in the group separator

br,
edgar

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hi Edgar,

I personally agree with most of your observations :slight_smile:

About this one:

6. Show the number of online buddies in the group separator

It's done but I think it's still having some performance tests.

Cheers,
Valentin

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Edgar,

Thank you for sharing your comments with us!

I'll quickly add my opinion inline and let the other members of our community share theirs as well.

2. The font in the place to write is different from the place where it
is shown, it might be good to use the same font.

Ah, I so much want them to be the same (e.g. because the font switching not only in SC but also in Thunderbird quickly tires my eyes). I even want them to be the same as the font of the other interface elements but the respective Swing component has been resisting my tries.

3. The legend showing date and time should probably not be shown on
every message. sometimes people write more than one message without
getting a response and with this text it is difficult to read. It
would probably be convenient to wait a few minutes after the writing
stops to print it. It might also be good to use a font color which
doesn't distract from the content, e.g. light gray.

I agree. It may be a habit but I only care about the timestamp when there has been a long pause e.g. after I've been away from my computer for a few minutes and a message has come while I was away. I think I created an issue about the default chat style wasting too much space and I believe the timestamp issue that you're talking about is in line with it.

4. It might be useful to have a button on the chat window to clear the
history, just to give the user the option to clean the panel to
facilitate reading.

Well... I personally think another button isn't anything I need. I'd go for a menu item in the chat window menu or the context menu of the chat history panel.

Anyway, it isn't really a feature I've ever missed.

5. SIP communicator sends lots of notifications of typing, Facebook
servers don't like getting lots of messages, they ask to refresh the
session when it happens, i.e. getting sent messages by requesting the
history and connect again to request newer messages.

Isn't it something that should be handled at the protocol-specific level? I mean if Facebook has a problem, isn't it appropriate to throttle them in the Facebook protocol rather that in SIP Communicator in general?

Regards,
Lubomir

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Hi Lubomir,

thanks for your feedback.

5. SIP communicator sends lots of notifications of typing, Facebook
servers don't like getting lots of messages, they ask to refresh the
session when it happens, i.e. getting sent messages by requesting the
history and connect again to request newer messages.

Isn't it something that should be handled at the protocol-specific level? I
mean if Facebook has a problem, isn't it appropriate to throttle them in the
Facebook protocol rather that in SIP Communicator in general?

I think you are right.

br,
edgar

···

On Thu, Sep 3, 2009 at 11:41 PM, Lubomir Marinov<lubomir.marinov@gmail.com> wrote:

Regards,
Lubomir

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Hey Edgar,

Sorry for the late reply.

Yes please, feel free to log issues for these.

Cheers
Emil

Edgar Poce wrote:

···

Hi Lubomir,

thanks for your feedback.

On Thu, Sep 3, 2009 at 11:41 PM, Lubomir > Marinov<lubomir.marinov@gmail.com> wrote:

5. SIP communicator sends lots of notifications of typing, Facebook
servers don't like getting lots of messages, they ask to refresh the
session when it happens, i.e. getting sent messages by requesting the
history and connect again to request newer messages.

Isn't it something that should be handled at the protocol-specific level? I
mean if Facebook has a problem, isn't it appropriate to throttle them in the
Facebook protocol rather that in SIP Communicator in general?

I think you are right.

br,
edgar

Regards,
Lubomir

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net