[sip-comm-dev] GUI call and hangup buttons


#1

Hi all,

A choice has to be made about the GUI and I'd like to share the responsability by asking you what do you think :))

You'll find here two screenshots. The important part is the phone number combobox and the call button. So there are two possibilities. The first one is to have two buttons "Call" and "Hang up" (the blue and yellow buttons on the first screenshot) and the second is to have only one button which changes its state from call to hangup (the second screenshot with the little button right to the combobox).

So here is my opinion. I like the two buttons:) but I think that the only case when they'll be enabled together (so we'll see them as they are on the first screen shot) is when someone calls to us. In all other cases, when we are making the call we'll have only one of two buttons enabled, so it's not so pretty:) and it takes a lot of space.
If we have only one button as it's on the second screenshot. We choose a person or write a phone number and the button is in state "Call", when the connection is established the button state is changed to "Hang up" (it may be the same button image as on the other screenshot). When some one calls us a popup appears with photo, user name etc. where we have two buttons and we could accept or decline.

WDYT?

p.s. the colors of the buttons are not yet decided also, so if someone thinks that it's confusing to have blue and yellow for a call and hangup buttons, let me know :))

yana


#2

I like the GUI. The single button interface could be confusing for a lot
of users.

I have a suggestion. I can try and invite people form CivicSpaceLabs to
have a look and evaluate the UI. I know that they would be interested in
having a good OpenSource cross platform messenger. They are working
already on integrating Asterix with CMS and CRM for activist
communities, etc...

What do you think? Should I go ahead. They have a lot of experience in
design for usability.

It could be a good thing to keep an eye on http://openusability.org

<quote>
The idea behind is simple: There are many Usability Experts who want to
contribute to software projects. And there are many Developers who want
to make their software more usable, and as a consequence, more
successful.
</quote>

It is a very helpful resource.

Cheers,
Vlado

···

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


#3

Yana Stamcheva wrote:

Hi all,

A choice has to be made about the GUI and I'd like to share the responsability by asking you what do you think :))

You'll find here two screenshots. The important part is the phone number combobox and the call button. So there are two possibilities. The first one is to have two buttons "Call" and "Hang up" (the blue and yellow buttons on the first screenshot) and the second is to have only one button which changes its state from call to hangup (the second screenshot with the little button right to the combobox).

So here is my opinion. I like the two buttons:) but I think that the only case when they'll be enabled together (so we'll see them as they are on the first screen shot) is when someone calls to us. In all other cases, when we are making the call we'll have only one of two buttons enabled, so it's not so pretty:) and it takes a lot of space.

If we have only one button as it's on the second screenshot. We choose a person or write a phone number and the button is in state "Call", when the connection is established the button state is changed to "Hang up" (it may be the same button image as on the other screenshot). When some one calls us a popup appears with photo, user name etc. where we have two buttons and we could accept or decline.

WDYT?

p.s. the colors of the buttons are not yet decided also, so if someone thinks that it's confusing to have blue and yellow for a call and hangup buttons, let me know :))

yana

I think the best is to have two buttons.
1. When you have hangup button, When some one is dialing you can cancel the call
2. When you're talking to some one you can use the Call button to dial some body else, as at that time the first call is on hold.
If something else come up I will tell you know but really my opinion is to have two buttons, because their fonctionality can be extended.


#4

Hi Vlado,

Thanks for the fast reponse! The GUI is very far from finished so I'd be glad to hear suggestions from anyone!

yana

vlado wrote:

···

I like the GUI. The single button interface could be confusing for a lot
of users.

I have a suggestion. I can try and invite people form CivicSpaceLabs to
have a look and evaluate the UI. I know that they would be interested in
having a good OpenSource cross platform messenger. They are working
already on integrating Asterix with CMS and CRM for activist
communities, etc...

What do you think? Should I go ahead. They have a lot of experience in
design for usability.It could be a good thing to keep an eye on http://openusability.org

<quote>
The idea behind is simple: There are many Usability Experts who want to
contribute to software projects. And there are many Developers who want
to make their software more usable, and as a consequence, more
successful.
</quote>

It is a very helpful resource.

Cheers,
Vlado

---------------------------------------------------------------------
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

vlado wrote:

I have a suggestion. I can try and invite people form CivicSpaceLabs to
have a look and evaluate the UI. I know that they would be interested in
having a good OpenSource cross platform messenger. They are working
already on integrating Asterix with CMS and CRM for activist
communities, etc...

What do you think? Should I go ahead. They have a lot of experience in
design for usability.

Sounds, promising. We'd be happy to have any kind of constructive criticism and especially when coming from experienced people. So yes feel free to invite them.

It could be a good thing to keep an eye on http://openusability.org

<quote>
The idea behind is simple: There are many Usability Experts who want to
contribute to software projects. And there are many Developers who want
to make their software more usable, and as a consequence, more
successful.
</quote>

It is a very helpful resource.

Wow! That sounds just great. Thanks a lot for the pointer, Vlado! How does it work? I tried a registration for sip-communicator and am apparently now waiting for acceptance. Is that all we need to do? How do things happen from that point on? We just sit and wait for a usability expert to show up?

Emil

···

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


#6

Damian Minkov wrote:

Yana Stamcheva wrote:

Hi all,

A choice has to be made about the GUI and I'd like to share the responsability by asking you what do you think :))

You'll find here two screenshots. The important part is the phone number combobox and the call button. So there are two possibilities. The first one is to have two buttons "Call" and "Hang up" (the blue and yellow buttons on the first screenshot) and the second is to have only one button which changes its state from call to hangup (the second screenshot with the little button right to the combobox).

So here is my opinion. I like the two buttons:) but I think that the only case when they'll be enabled together (so we'll see them as they are on the first screen shot) is when someone calls to us. In all other cases, when we are making the call we'll have only one of two buttons enabled, so it's not so pretty:) and it takes a lot of space.

If we have only one button as it's on the second screenshot. We choose a person or write a phone number and the button is in state "Call", when the connection is established the button state is changed to "Hang up" (it may be the same button image as on the other screenshot). When some one calls us a popup appears with photo, user name etc. where we have two buttons and we could accept or decline.

WDYT?

p.s. the colors of the buttons are not yet decided also, so if someone thinks that it's confusing to have blue and yellow for a call and hangup buttons, let me know :))

yana

Hi Damian,

Thanks for the reply!

I think the best is to have two buttons.
1. When you have hangup button, When some one is dialing you can cancel the call

If we decide to use one button I thought to handle this case by using a popup window which is shown when someone is calling and there to have two buttons "Answer" and "Hang up". You could see the attachement :slight_smile:

2. When you're talking to some one you can use the Call button to dial some body else, as at that time the first call is on hold.

This is a good reason. I'll examine carefully this case, because it also could be confusing that the call button is not disabled when you're talking with someone at the moment.

If something else come up I will tell you know but really my opinion is to have two buttons, because their fonctionality can be extended.

Regards,
yana

···

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


#7

Wow! That sounds just great. Thanks a lot for the pointer, Vlado! How
does it work? I tried a registration for sip-communicator and am
apparently now waiting for acceptance. Is that all we need to do? How do
things happen from that point on? We just sit and wait for a usability
expert to show up?

If it was that easy :slight_smile:

It's just a meeting point or a portal, if you prefer that term. We can
put annoucements, and ask people for help, advice, etc... As in most
communities nowbody will notice you, unless you promote yourself one
way or another.

I'm trying at the moment with CivicSpace, I don't know what will be the
result, I hope they will help, and yes, they do have experience in this
area, simply because they have to make their distribution friendly for
non-geeks.

I'll try and ask a few others as well.

The best bit are the resources
   http://openusability.org/docman/?group_id=52
and the networking opportunities.

Talking about networking, is anyone planning to be at FOSDEM in
Brussels? I probably will,but not sure yet, will be present. Somebody
could present the project, and it can offer a lot of very good contacts,
meaning good will and help :slight_smile:

Cheers,
Vlado

···

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


#8

Dear Kalpazana,

I think that the best way is to follow GSM technology. The big
companies like Nokia and Sony-Ericsson invest lot of money to research
how much button for each situation is better.

···

--
Best regards,
Miroslav mailto:miro@space-comm.com

Thursday, December 1, 2005, 6:54:43 PM, you wrote:

Damian Minkov wrote:

Yana Stamcheva wrote:

Hi all,

A choice has to be made about the GUI and I'd like to share the
responsability by asking you what do you think :))

You'll find here two screenshots. The important part is the phone
number combobox and the call button. So there are two possibilities.
The first one is to have two buttons "Call" and "Hang up" (the blue
and yellow buttons on the first screenshot) and the second is to have
only one button which changes its state from call to hangup (the
second screenshot with the little button right to the combobox).

So here is my opinion. I like the two buttons:) but I think that the
only case when they'll be enabled together (so we'll see them as they
are on the first screen shot) is when someone calls to us. In all
other cases, when we are making the call we'll have only one of two
buttons enabled, so it's not so pretty:) and it takes a lot of space.

If we have only one button as it's on the second screenshot. We
choose a person or write a phone number and the button is in state
"Call", when the connection is established the button state is
changed to "Hang up" (it may be the same button image as on the other
screenshot). When some one calls us a popup appears with photo, user
name etc. where we have two buttons and we could accept or decline.

WDYT?

p.s. the colors of the buttons are not yet decided also, so if
someone thinks that it's confusing to have blue and yellow for a
call and hangup buttons, let me know :))

yana

Hi Damian,

Thanks for the reply!

I think the best is to have two buttons.
1. When you have hangup button, When some one is dialing you can
cancel the call

If we decide to use one button I thought to handle this case by using a
popup window which is shown when someone is calling and there to have
two buttons "Answer" and "Hang up". You could see the attachement :slight_smile:

2. When you're talking to some one you can use the Call button to dial
some body else, as at that time the first call is on hold.

This is a good reason. I'll examine carefully this case, because it
also could be confusing that the call button is not disabled when you're
talking with someone at the moment.

If something else come up I will tell you know but really my opinion
is to have two buttons, because their fonctionality can be extended.

Regards,
yana

---------------------------------------------------------------------
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


#9

vlado wrote:

It's just a meeting point or a portal, if you prefer that term. We can
put annoucements, and ask people for help, advice, etc... As in most
communities nowbody will notice you, unless you promote yourself one
way or another.

OK I see. Well it seems like it would be worth the effort. There's no doubt that smooth user experience is crucial.

I'm trying at the moment with CivicSpace, I don't know what will be the
result, I hope they will help, and yes, they do have experience in this
area, simply because they have to make their distribution friendly for
non-geeks.

I am crossing my fingers then!

I'll try and ask a few others as well.

Thanks! By the way let me know if you are also willing to contribute on openusability and I'll give you the role you want on the new project there.

Talking about networking, is anyone planning to be at FOSDEM in
Brussels? I probably will,but not sure yet, will be present. Somebody
could present the project, and it can offer a lot of very good contacts,
meaning good will and help :slight_smile:

Yes I am planning on going. I believe Martin is also going (right?). Anyone else? I'd be glad to meet any of you there.

As for presenting, I am afraid it's already late and all slots seem to be booked. We'll have to do that next year!

Cheers
Emil

···

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


#10

Hi all,

it appears that some of you may be present at the FOSDEM, held in Brussels on Feb 25 and 26. As Emil and I are planning to go, it can be a good occasion to meet and discuss about the SIP Communicator.

If you're interested, speak up.

Martin

···

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