This discussion is based off http://drupal.org/node/872330.
In the latest version of QTC, a user can set his status to invisible but that user will still appear to everyone online as 'invisible'! For me, invisible means that you can see who is online but no one else can see you.
I don't think this is really invisible....
@Quiptime - you said that Google Chat has this similar functionality but I did a little research tonight and it seems that invisible on google chat means that your contacts can't see you.
http://www.google.com/support/talk/bin/answer.py?hl=en&answer=69422
If others can see you while you're invisible then what's the difference between invisible and busy? What are you trying to tell others if you go 'invisible' but they can still see you?
Anyway, for me, the most important thing is to have an option where I can be online but not show up to my friends in the friends list.
I look forward to hearing your thoughts on this.
Comments
Part of the discussion starting point
Part of the beginning of the discussion:
I think the final answer is the answer to the third Question.
Functionality of invisible vs. offline
For me the invisible functionality should be just what is sounds like... otherwise users will be confused. Perhaps something like this:
Invisible -- your friends can't see that you are online but you are still able to see that your friends are online. Kind of a 'stealth' mode.
Offline -- No one can see you and you can't see anyone online. You are truly offline from the program. Maybe you don't want to use it.
While it would be cool to have both of these, I could live with just one or the other as long as there is someway to hide myself so that others can't send me a message.
I hope that 'Speichern' means 'submit'. :). Everything has changed to German in this group ;).
Yes, 'Speichern' means
Yes, 'Speichern' means 'Submit'.
Yes, I changed the group language option to German. :-)
The current implementation of
The current implementation of the available/invisible/busy functionality is not final. I need the discussion to this thema to find a possible final solution.
That helps me also to avoid unnecessary development time (I have already invested a lot of time.).
Today I discovered a logic error - a strong confusion candidate. The lack of logic: Disable (in the module configutation) the invisible and busy function and then use the options of the chat bar. :-(
At the moment I have no solution for this confusion.
logic
Strange. This group is having some problems. I got a 503 error (which I also got once while trying to join yesterday) and I lost my last post. Here goes again:
I can see what you mean by the logic error. If you disable invisible/busy in the settings then what is the point of having the options in the chat bar, right?
Well, here are a few ideas on how to solve this problem:
Create an 'offline' status that can't be disabled in the settings and this will always show up in options no matter if invisible/busy are enabled OR
Move the status options onto the chatbar itself (easier access) and put something else in the options menu. In this way, users wouldn't have to click on 'options' to change their status from the chat bar.
I had a screenshot to show you but for some reason, I can't upload to this group. Is there a way to enable this?
Just a couple of ideas...hope they help a little.
The theme is a little bit more complex
Thanks for your idea,
1.
The theme is a little bit more complex.
The functionality to hide the options available/invisible/busy status is already implemented:
admin/settings/qtc/chat -> Online status -> Online status variant -> No, use drupals default
I think a fourth status option, with name offline, is not necessary (and makes a usability-overload in this context).
My idea to solve the problem with the logic error:
Disable the options "Allow invisible status" and "Allow busy status" hide the usage in the chat bar options list and on all other places* to use the function to change the online status.
It is the same (usability) as if the option is disabled Online status variant -> "Yes, accept users status" and used the option "No, use Drupals default".
But, internally, it is not the same.
Is enabled "Yes, accept users status" a logout and login of a user immediately changed his status. QTChat immediately recognize this new status and visualized him.
Is disabled "Yes, accept users status" and used "No, use Drupals default" a logout and login of a user not immediately change the status of the user. In this case are used a time-based visualization of the status. This time-based visualization uses the setting of admin/settings/qtc/chat -> Online status -> Online status time.
other places*
Is enabled "Yes, accept users status" users can change the online status in the preferences of the user account: user/x/online-status
To access the page "My online status" I will make additionally accessible by a menu entry.
2.
Mhm ...
To attach images to group post comments - I can not administer this. I send a mail with a feature request. I await your screenshot. To attach a image you can make a new post, not a comment.
Accessibility
Ok, so let me make sure that I understand...
You would completely remove the invisible/busy status options from the module, correct?
The "Yes, accept users status" or "No, use drupals default" would remain, correct?
If "Yes, accept users status" is selected by the administrator, then users would be able to change their online/offline status by going to a page like 'user/x/online-status', correct?
For me personally, the invisible/busy options aren't all that important. Last time I checked, this wasn't an option in Facebook. Others might like this functionality though.
However, I do think that there should still be an easy (and quick way) for users to change this online/offline status without having to go to another page to do it. Having to load 'user/x/online-status' seems like too much trouble.
Would it be possible to add this option to the chat bar itself?
1. No no, this options I will
1.
No no, this options I will not remove.
I will reorganize the things are the two status options Invisible and Busy (by admin) collectively not allowed.
2.
Yes, correct.
3.
Yes, correct.
Thanks for your screenshot.
What is the difference
And, what is the difference between click "Options" and click "Online" (your screenshot)?
The result is the same: The user sees the clickable status options.
The "little man" icon at the bottom of the chat bar visualize the users online status.
Reserved for future functions
But, at the moment in this place are only the "Options" settings available and other settings on this place are temporarily not displayed. These other settings are settings of the "Friend lists". These settings not displayed because I have not yet developed friend lists functionality for the chat bar and because not to display a nonfunctional chat bar area.
In other words, the area to the right/left of "Options" is already reserved for future functions of "Friend lists".
Yes, OK.
And in the next week will be a feature request if they have not implemented.
This is already implemented. With AJAX interaction.
What is lacking is an additional link in the user account menu.
Clear now
Now I understand better. I had thought that you were going to remove the 'Ajax' functionality from the chat bar and only allow users to change their status on a separate page. But what you mean is that you are going to add an additional link in the user account menu. That sounds great.
Sorry, I misunderstood what you were saying. If you are going to keep the online/offline status functions in the "Options" then you are right...there is no reason to have a click "Online"...
I think your plan will work out just fine, then.
I really love this module. It is the 'coolest' module that I have ever used on Drupal. I still can't believe how well it has worked out of the box.
My site is closed for the summer so I don't have many users on here right now but so far, using the Devel module, I don't see any extra major load on the database using QTC. It appears to be pretty lightweight.
Starting in the first week of September, I will have about a few hundred users who will be on my site. I will be testing QTC to see how it performs with lots of users.
Many thanks for your statement
Many thanks for your statement. :-)
I worked hard for that. And the module is not yet fully developed.
In addition to the many small things are yet to come two important functions.
The first:
Messages from same user in multiple browser tabs.
This will take not so long time.
The second:
This is a bigger thing and probably only for a few users interesting. It is the CTChat APE functionality.
But this will take some time. And, perhaps there is generous donor, to support this development.
I am very interested in test results with such a user scenario. I hope the light weight of QTC is to confirm.