[sip-comm-dev] a few corrections ...


#1

Hi devs,

I was using SC (with the french translation) and i saw that not everything
is translated such as in the menu Outils>Advanced call history search and
in the help menu I get to elements About which give the same result after
clicking on it.

Concerning the systay, I saw that a french version of the properties file is
also missing...right ? Shoudl it be done ?

I was trying to find the messages.properties to see if there were some
mistakes I could find but I didn't find this file ( referenced also in the
resources_fr.properties ).
So where could I find the messages.properties file, if there still is one.

However I did find a few typing mistakes in the resources_fr.properties
file.

Here are the lines fixed as far as i'm concerned. It may remains a few more
though...

···

resources_fr.properties

========================================

56 authRejected=Le contact a rejetÃ(c) votre demande d'autorisation.

67 banFailedNotAllowed=Erreur lors de l'exclusion {0}. Le propriÃ(c)taire et
l'administrateur du salon ne peuvent pas être exclus.

68 banFailedNotEnoughPermissions=Erreur lors de l'exclusion {0}. Vous n'avez
pas les droits suffisants pour cela.

76 chatRoomConfiguration=Configuration du salon {0}

86 chatRoomNotExist=Le salon {0} est introuvable sur le serveur {1}. Prière
de vÃ(c)rifier la validité du nom que vous avez saisi.

90 chatRoomRegistrationRequired=Vous devez être enregistrÃ(c) avant de
pouvoir rejoindre le salon {0}.

100 connectionFailedMessage=Echec de connexion pour le compte : Nom
d'utilisateur : {0}, Nom du serveur : {1}.

101 connectionExpiredMessage=Vous avez Ã(c)tÃ(c) dÃ(c)connectÃ(c) du
serveur {0}.

103 contactNotSupportingTelephony=Le contact choisi {0} ne supporte pas la
tÃ(c)lÃ(c)phonie.

106 contactTypingStateStale=L'Ã(c)tat de la saisie ne peut pas être mis Ã
jour

110 copyLink=Copier l'&adresse

114 createChatRoomError=Echec lors de la crÃ(c)ation du salon : {0}.

117 createGroupName=Veuillez saisir dans le champ suivant le nom du groupe
que vous dÃ(c)sirez crÃ(c)er.

175 kickFailedNotAllowed=Echec de la tentative d'exclusion {0}. Le
propriÃ(c)taire et l'administrateur du salon ne peuvent être exclus.

185 logoffNotSucceeded=Une erreur est survenue lors de la dÃ(c)connexion avec
le compte suivant : Nom d'utilisateur : {0}, Nom du serveur : {1}.

192 moveContactError=Le &contact ne peut pas être dÃ(c)placÃ(c)

194 msgDeliveryOfflineNotSupported=Le protocole que vous utilisez ne
supporte pas l'envoi de messages en mode "dÃ(c)connectÃ(c)". Vous
pouvez essayer
de joindre votre contact au moyen d'un autre protocole ou attendre jusqu'Ã
ce qu'il ou elle soit "connectÃ(c)(e)".

196 msgNotDelivered=Un problème au niveau du rÃ(c)seau est survenu.

240 removeContactText=<DIV>Etes-vous certain de vouloir supprimer <b> {0}
</b><br>de votre liste de contacts ?</DIV>

243 renameContact=Re&nommer le contact

245 renameGroup=Re&nommer le groupe

246 renameGroupInfo=Dans le champ suivant, vous pouvez saisir le nom de
groupe que vous souhaitez utiliser.

246 renameGroupInfo=Dans le champ suivant, vous pouvez saisir le nom de
groupe que vous souhaitez utiliser.

249 requestAuthorizationInfo=Impossible d'ajouter {0} Ã votre liste de
contacts. {0} doit accepter votre demande pour l'ajouter. Merci d'entrer
votre demande ci-dessous.

251 requestAuthReasonEnter=Entrez la raison de votre demande

252 responseAuthReasonEnter=Entrez la raison de votre rÃ(c)ponse

274 sendSmsNotSupported=Le protocole que vous avez sÃ(c)lectionnÃ(c) ne permet
pas l'envoi de SMS.

293 unknown=Utilisateur inconnu

============================================================

Cheers,

JD


#2

Hi JD,

JD wrote:

Hi devs,

I was using SC (with the french translation) and i saw that not everything
is translated such as in the menu Outils>Advanced call history search and
in the help menu I get to elements About which give the same result after
clicking on it.

Concerning the systay, I saw that a french version of the properties file is
also missing...right ? Shoudl it be done ?

Yes, we don't have a french version of the systray yet. You're more than welcome to do one if you wish:)

I was trying to find the messages.properties to see if there were some
mistakes I could find but I didn't find this file ( referenced also in the
resources_fr.properties ).
So where could I find the messages.properties file, if there still is one.

The messages.properties file is now replaced by the resources.properties file that you have found in resources/languages/impl/gui.

However I did find a few typing mistakes in the resources_fr.properties
file.

Here are the lines fixed as far as i'm concerned. It may remains a few more
though...

Hey, thanks for this contribution! It may take some time to apply it though, because of the GSoC, but don't be discouraged, we'll let you know as soon as we commit it.

Cheers,
Yana

···

>>>>resources_fr.properties

56 authRejected=Le contact a rejet�(c) votre demande d'autorisation.

67 banFailedNotAllowed=Erreur lors de l'exclusion {0}. Le propri�(c)taire et
l'administrateur du salon ne peuvent pas être exclus.

68 banFailedNotEnoughPermissions=Erreur lors de l'exclusion {0}. Vous n'avez
pas les droits suffisants pour cela.

76 chatRoomConfiguration=Configuration du salon {0}

86 chatRoomNotExist=Le salon {0} est introuvable sur le serveur {1}. Prière
de v�(c)rifier la validit� du nom que vous avez saisi.

90 chatRoomRegistrationRequired=Vous devez être enregistr�(c) avant de
pouvoir rejoindre le salon {0}.

100 connectionFailedMessage=Echec de connexion pour le compte : Nom
d'utilisateur : {0}, Nom du serveur : {1}.

101 connectionExpiredMessage=Vous avez �(c)t�(c) d�(c)connect�(c) du
serveur {0}.

103 contactNotSupportingTelephony=Le contact choisi {0} ne supporte pas la
t�(c)l�(c)phonie.

106 contactTypingStateStale=L'�(c)tat de la saisie ne peut pas être mis �
jour

110 copyLink=Copier l'&adresse

114 createChatRoomError=Echec lors de la cr�(c)ation du salon : {0}.

117 createGroupName=Veuillez saisir dans le champ suivant le nom du groupe
que vous d�(c)sirez cr�(c)er.

175 kickFailedNotAllowed=Echec de la tentative d'exclusion {0}. Le
propri�(c)taire et l'administrateur du salon ne peuvent être exclus.

185 logoffNotSucceeded=Une erreur est survenue lors de la d�(c)connexion avec
le compte suivant : Nom d'utilisateur : {0}, Nom du serveur : {1}.

192 moveContactError=Le &contact ne peut pas être d�(c)plac�(c)

194 msgDeliveryOfflineNotSupported=Le protocole que vous utilisez ne
supporte pas l'envoi de messages en mode "d�(c)connect�(c)". Vous
pouvez essayer
de joindre votre contact au moyen d'un autre protocole ou attendre jusqu'�
ce qu'il ou elle soit "connect�(c)(e)".

196 msgNotDelivered=Un problème au niveau du r�(c)seau est survenu.

240 removeContactText=<DIV>Etes-vous certain de vouloir supprimer <b> {0}
</b><br>de votre liste de contacts ?</DIV>

243 renameContact=Re&nommer le contact

245 renameGroup=Re&nommer le groupe

246 renameGroupInfo=Dans le champ suivant, vous pouvez saisir le nom de
groupe que vous souhaitez utiliser.

246 renameGroupInfo=Dans le champ suivant, vous pouvez saisir le nom de
groupe que vous souhaitez utiliser.

249 requestAuthorizationInfo=Impossible d'ajouter {0} � votre liste de
contacts. {0} doit accepter votre demande pour l'ajouter. Merci d'entrer
votre demande ci-dessous.

251 requestAuthReasonEnter=Entrez la raison de votre demande

252 responseAuthReasonEnter=Entrez la raison de votre r�(c)ponse

274 sendSmsNotSupported=Le protocole que vous avez s�(c)lectionn�(c) ne permet
pas l'envoi de SMS.

293 unknown=Utilisateur inconnu

============================================================

Cheers,

JD

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

JD wrote:
> Hi devs,
>
> I was using SC (with the french translation) and i saw that not
everything
> is translated such as in the menu Outils>Advanced call history search
and
> in the help menu I get to elements About which give the same result
after
> clicking on it.
>
> Concerning the systay, I saw that a french version of the properties
file is
> also missing...right ? Shoudl it be done ?

Yes, we don't have a french version of the systray yet. You're more than
welcome to do one if you wish:)

Ok it's done. The french version of the systray resources.properties is
attached to this mail.

>
> I was trying to find the messages.properties to see if there were some
> mistakes I could find but I didn't find this file ( referenced also in
the
> resources_fr.properties ).
> So where could I find the messages.properties file, if there still is
one.

The messages.properties file is now replaced by the resources.properties
file that you have found in resources/languages/impl/gui.

Ok I thought so.

>
> However I did find a few typing mistakes in the resources_fr.properties
> file.
>
> Here are the lines fixed as far as i'm concerned. It may remains a few
more
> though...

Hey, thanks for this contribution! It may take some time to apply it
though, because of the GSoC, but don't be discouraged, we'll let you
know as soon as we commit it.

Sure, I totally understand.

resources_fr.properties (1.62 KB)

···

On Tue, Apr 1, 2008 at 10:28 AM, Yana Stamcheva <yana@sip-communicator.org> wrote:

Cheers,
Yana

>
>
> >>>>resources_fr.properties
> ========================================
>
> 56 authRejected=Le contact a rejetÃ(c) votre demande d'autorisation.
>
> 67 banFailedNotAllowed=Erreur lors de l'exclusion {0}. Le
propriÃ(c)taire et
> l'administrateur du salon ne peuvent pas être exclus.
>
> 68 banFailedNotEnoughPermissions=Erreur lors de l'exclusion {0}. Vous
n'avez
> pas les droits suffisants pour cela.
>
> 76 chatRoomConfiguration=Configuration du salon {0}
>
> 86 chatRoomNotExist=Le salon {0} est introuvable sur le serveur {1}.
Prière
> de vÃ(c)rifier la validité du nom que vous avez saisi.
>
> 90 chatRoomRegistrationRequired=Vous devez être enregistrÃ(c) avant de
> pouvoir rejoindre le salon {0}.
>
> 100 connectionFailedMessage=Echec de connexion pour le compte : Nom
> d'utilisateur : {0}, Nom du serveur : {1}.
>
> 101 connectionExpiredMessage=Vous avez Ã(c)tÃ(c) dÃ(c)connectÃ(c) du
> serveur {0}.
>
> 103 contactNotSupportingTelephony=Le contact choisi {0} ne supporte pas
la
> tÃ(c)lÃ(c)phonie.
>
> 106 contactTypingStateStale=L'Ã(c)tat de la saisie ne peut pas être mis
Ã
> jour
>
> 110 copyLink=Copier l'&adresse
>
> 114 createChatRoomError=Echec lors de la crÃ(c)ation du salon : {0}.
>
> 117 createGroupName=Veuillez saisir dans le champ suivant le nom du
groupe
> que vous dÃ(c)sirez crÃ(c)er.
>
> 175 kickFailedNotAllowed=Echec de la tentative d'exclusion {0}. Le
> propriÃ(c)taire et l'administrateur du salon ne peuvent être exclus.
>
> 185 logoffNotSucceeded=Une erreur est survenue lors de la dÃ(c)connexion
avec
> le compte suivant : Nom d'utilisateur : {0}, Nom du serveur : {1}.
>
> 192 moveContactError=Le &contact ne peut pas être dÃ(c)placÃ(c)
>
> 194 msgDeliveryOfflineNotSupported=Le protocole que vous utilisez ne
> supporte pas l'envoi de messages en mode "dÃ(c)connectÃ(c)". Vous
> pouvez essayer
> de joindre votre contact au moyen d'un autre protocole ou attendre
jusqu'Ã
> ce qu'il ou elle soit "connectÃ(c)(e)".
>
> 196 msgNotDelivered=Un problème au niveau du rÃ(c)seau est survenu.
>
> 240 removeContactText=<DIV>Etes-vous certain de vouloir supprimer <b>
{0}
> </b><br>de votre liste de contacts ?</DIV>
>
> 243 renameContact=Re&nommer le contact
>
> 245 renameGroup=Re&nommer le groupe
>
> 246 renameGroupInfo=Dans le champ suivant, vous pouvez saisir le nom de
> groupe que vous souhaitez utiliser.
>
>
> 246 renameGroupInfo=Dans le champ suivant, vous pouvez saisir le nom de
> groupe que vous souhaitez utiliser.
>
> 249 requestAuthorizationInfo=Impossible d'ajouter {0} Ã votre liste de
> contacts. {0} doit accepter votre demande pour l'ajouter. Merci d'entrer
> votre demande ci-dessous.
>
> 251 requestAuthReasonEnter=Entrez la raison de votre demande
>
> 252 responseAuthReasonEnter=Entrez la raison de votre rÃ(c)ponse
>
> 274 sendSmsNotSupported=Le protocole que vous avez sÃ(c)lectionnÃ(c) ne
permet
> pas l'envoi de SMS.
>
> 293 unknown=Utilisateur inconnu
>
>
> ============================================================
>
>
>
> Cheers,
>
> JD
>

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

sorry for the lag. I have just committed your french translation of the systray. I'll also add your contribution to our web site. Thanks!!!

Cheers,
Yana

JD wrote:

···

On Tue, Apr 1, 2008 at 10:28 AM, Yana Stamcheva <yana@sip-communicator.org> > wrote:

Hi JD,

JD wrote:

Hi devs,

I was using SC (with the french translation) and i saw that not

everything

is translated such as in the menu Outils>Advanced call history search

and

in the help menu I get to elements About which give the same result

after

clicking on it.

Concerning the systay, I saw that a french version of the properties

file is

also missing...right ? Shoudl it be done ?

Yes, we don't have a french version of the systray yet. You're more than
welcome to do one if you wish:)

Ok it's done. The french version of the systray resources.properties is
attached to this mail.

I was trying to find the messages.properties to see if there were some
mistakes I could find but I didn't find this file ( referenced also in

the

resources_fr.properties ).
So where could I find the messages.properties file, if there still is

one.

The messages.properties file is now replaced by the resources.properties
file that you have found in resources/languages/impl/gui.

Ok I thought so.

However I did find a few typing mistakes in the resources_fr.properties
file.

Here are the lines fixed as far as i'm concerned. It may remains a few

more

though...

Hey, thanks for this contribution! It may take some time to apply it
though, because of the GSoC, but don't be discouraged, we'll let you
know as soon as we commit it.

Sure, I totally understand.

Cheers,
Yana

>>>>resources_fr.properties

56 authRejected=Le contact a rejet�(c) votre demande d'autorisation.

67 banFailedNotAllowed=Erreur lors de l'exclusion {0}. Le

propri�(c)taire et

l'administrateur du salon ne peuvent pas être exclus.

68 banFailedNotEnoughPermissions=Erreur lors de l'exclusion {0}. Vous

n'avez

pas les droits suffisants pour cela.

76 chatRoomConfiguration=Configuration du salon {0}

86 chatRoomNotExist=Le salon {0} est introuvable sur le serveur {1}.

Prière

de v�(c)rifier la validit� du nom que vous avez saisi.

90 chatRoomRegistrationRequired=Vous devez être enregistr�(c) avant de
pouvoir rejoindre le salon {0}.

100 connectionFailedMessage=Echec de connexion pour le compte : Nom
d'utilisateur : {0}, Nom du serveur : {1}.

101 connectionExpiredMessage=Vous avez �(c)t�(c) d�(c)connect�(c) du
serveur {0}.

103 contactNotSupportingTelephony=Le contact choisi {0} ne supporte pas

la

t�(c)l�(c)phonie.

106 contactTypingStateStale=L'�(c)tat de la saisie ne peut pas être mis

jour

110 copyLink=Copier l'&adresse

114 createChatRoomError=Echec lors de la cr�(c)ation du salon : {0}.

117 createGroupName=Veuillez saisir dans le champ suivant le nom du

groupe

que vous d�(c)sirez cr�(c)er.

175 kickFailedNotAllowed=Echec de la tentative d'exclusion {0}. Le
propri�(c)taire et l'administrateur du salon ne peuvent être exclus.

185 logoffNotSucceeded=Une erreur est survenue lors de la d�(c)connexion

avec

le compte suivant : Nom d'utilisateur : {0}, Nom du serveur : {1}.

192 moveContactError=Le &contact ne peut pas être d�(c)plac�(c)

194 msgDeliveryOfflineNotSupported=Le protocole que vous utilisez ne
supporte pas l'envoi de messages en mode "d�(c)connect�(c)". Vous
pouvez essayer
de joindre votre contact au moyen d'un autre protocole ou attendre

jusqu'�

ce qu'il ou elle soit "connect�(c)(e)".

196 msgNotDelivered=Un problème au niveau du r�(c)seau est survenu.

240 removeContactText=<DIV>Etes-vous certain de vouloir supprimer <b>

{0}

</b><br>de votre liste de contacts ?</DIV>

243 renameContact=Re&nommer le contact

245 renameGroup=Re&nommer le groupe

246 renameGroupInfo=Dans le champ suivant, vous pouvez saisir le nom de
groupe que vous souhaitez utiliser.

246 renameGroupInfo=Dans le champ suivant, vous pouvez saisir le nom de
groupe que vous souhaitez utiliser.

249 requestAuthorizationInfo=Impossible d'ajouter {0} � votre liste de
contacts. {0} doit accepter votre demande pour l'ajouter. Merci d'entrer
votre demande ci-dessous.

251 requestAuthReasonEnter=Entrez la raison de votre demande

252 responseAuthReasonEnter=Entrez la raison de votre r�(c)ponse

274 sendSmsNotSupported=Le protocole que vous avez s�(c)lectionn�(c) ne

permet

pas l'envoi de SMS.

293 unknown=Utilisateur inconnu

============================================================

Cheers,

JD

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

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


#5

Hi! I noticed, that adding a new (SIP) contact is not very comfortable and
intuitive. You just enter the ID (the telefon number, not everyone
recognizes this) and afterwards can rename your contact. I propose to split
the dialog, that a DisplayName and the ID can be entered. The displayname
then shall be the name in the contact list, the telephonnumber (or other
account id) are then the ID(s) of the selected accounts.

What do you think?

Cheers, Thomas


#6

Hi Thomas,

You're right, but for some protocole like MSN, the DisplayName is
stored on the server.
In this case, we don't need to specify a DisplayName, and if we set a
DisplayName, will it be change if the contact set another nickname ?

Why not personalize the word "Identifier" depending on the type of account ?

For example :
SIP : telephone number
MSN : Email address
Dict : Dictionary

And if the contact ID isn't explicit (always depending of the type of
account) adding a field to set a DisplayName directly.

What do you think ?

Cheers

Damien

···

2008/4/28 Thomas Hofer <mailinglisten@familie-hofer.net>:

Hi! I noticed, that adding a new (SIP) contact is not very comfortable and
intuitive. You just enter the ID (the telefon number, not everyone
recognizes this) and afterwards can rename your contact. I propose to split
the dialog, that a DisplayName and the ID can be entered. The displayname
then shall be the name in the contact list, the telephonnumber (or other
account id) are then the ID(s) of the selected accounts.

What do you think?

Cheers, Thomas

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


#7

I've implemented following dialog:

If more than one accounts are added to a new meta-contact, the metacontact
can be given a name.

If a protocol is added without serverstored information (like sip) the
metacontact can be given a name.

If a protocol is added with serverstored information (like icq) the
metacontact cannot be given a name.

I hope this meets all requirements.

If there are no comments left, I'll commit it in the afternoon.

Yana: you wrote the original code, what do you think of my
changes/extensions?

Cheers, Thomas

···

Von: Thomas Hofer [mailto:mailinglisten@familie-hofer.net]
Gesendet: Montag, 28. April 2008 11:31
An: dev@sip-communicator.dev.java.net
Betreff: [sip-comm-dev] New Contact Dialog

Hi! I noticed, that adding a new (SIP) contact is not very comfortable and
intuitive. You just enter the ID (the telefon number, not everyone
recognizes this) and afterwards can rename your contact. I propose to split
the dialog, that a DisplayName and the ID can be entered. The displayname
then shall be the name in the contact list, the telephonnumber (or other
account id) are then the ID(s) of the selected accounts.

What do you think?

Cheers, Thomas


#8

Hello

I want to work on interoperability in SC.Can i have some suggestions from
anyone here?

Rossi


#9

You're right, but how to implement this:
1) serverstored protocols impmement OperationSetServerStoredContactInfo,
right?
2) how? The plugin shall provide the identifier?

And if the contact ID isn't explicit (always depending of the type of
account) adding a field to set a DisplayName directly.

3) actually, no protocol has per default a explicit display name, I think.
Am I right?

Cheers, Thomas

···

-----Ursprüngliche Nachricht-----
Von: Damien Roth [mailto:damien.roth@gmail.com]
Gesendet: Montag, 28. April 2008 11:52
An: dev@sip-communicator.dev.java.net
Betreff: Re: [sip-comm-dev] New Contact Dialog

Hi Thomas,

You're right, but for some protocole like MSN, the DisplayName is
stored on the server.
In this case, we don't need to specify a DisplayName, and if we set a
DisplayName, will it be change if the contact set another nickname ?

Why not personalize the word "Identifier" depending on the type of
account ?

For example :
SIP : telephone number
MSN : Email address
Dict : Dictionary

And if the contact ID isn't explicit (always depending of the type of
account) adding a field to set a DisplayName directly.

What do you think ?

Cheers

Damien

2008/4/28 Thomas Hofer <mailinglisten@familie-hofer.net>:
>
>
>
>
> Hi! I noticed, that adding a new (SIP) contact is not very
comfortable and
> intuitive. You just enter the ID (the telefon number, not everyone
> recognizes this) and afterwards can rename your contact. I propose to
split
> the dialog, that a DisplayName and the ID can be entered. The
displayname
> then shall be the name in the contact list, the telephonnumber (or
other
> account id) are then the ID(s) of the selected accounts.
>
>
>
> What do you think?
>
> Cheers, Thomas

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


#10

Hi Thomas,

I agree that we should make changes and make the add contact process more intuitive, but I'm not sure I understand your idea. Could you explain a little more what is your suggestion?

Thanks,
Yana

Thomas Hofer wrote:

···

I've implemented following dialog:

If more than one accounts are added to a new meta-contact, the metacontact
can be given a name.

If a protocol is added without serverstored information (like sip) the
metacontact can be given a name.

If a protocol is added with serverstored information (like icq) the
metacontact cannot be given a name.

I hope this meets all requirements.

If there are no comments left, I'll commit it in the afternoon.

Yana: you wrote the original code, what do you think of my
changes/extensions?

Cheers, Thomas

Von: Thomas Hofer [mailto:mailinglisten@familie-hofer.net] Gesendet: Montag, 28. April 2008 11:31
An: dev@sip-communicator.dev.java.net
Betreff: [sip-comm-dev] New Contact Dialog

Hi! I noticed, that adding a new (SIP) contact is not very comfortable and
intuitive. You just enter the ID (the telefon number, not everyone
recognizes this) and afterwards can rename your contact. I propose to split
the dialog, that a DisplayName and the ID can be entered. The displayname
then shall be the name in the contact list, the telephonnumber (or other
account id) are then the ID(s) of the selected accounts.

What do you think?

Cheers, Thomas

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


#11

Hey,

I didn't see the attached images. I'll have a look and reply write you again.

Cheers,
Yana

Thomas Hofer wrote:

···

I've implemented following dialog:

If more than one accounts are added to a new meta-contact, the metacontact
can be given a name.

If a protocol is added without serverstored information (like sip) the
metacontact can be given a name.

If a protocol is added with serverstored information (like icq) the
metacontact cannot be given a name.

I hope this meets all requirements.

If there are no comments left, I'll commit it in the afternoon.

Yana: you wrote the original code, what do you think of my
changes/extensions?

Cheers, Thomas

Von: Thomas Hofer [mailto:mailinglisten@familie-hofer.net] Gesendet: Montag, 28. April 2008 11:31
An: dev@sip-communicator.dev.java.net
Betreff: [sip-comm-dev] New Contact Dialog

Hi! I noticed, that adding a new (SIP) contact is not very comfortable and
intuitive. You just enter the ID (the telefon number, not everyone
recognizes this) and afterwards can rename your contact. I propose to split
the dialog, that a DisplayName and the ID can be entered. The displayname
then shall be the name in the contact list, the telephonnumber (or other
account id) are then the ID(s) of the selected accounts.

What do you think?

Cheers, Thomas

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


#12

Another issue: you can select multiple accounts in the first page, but only
one ID-page is displayed for all protocols. I do not thing, anybody has the
same id in his SIP/Yahoo/MSN and Yahoo account.

I'll have a detailed look on it
Cheers
Thomas

···

-----Ursprüngliche Nachricht-----
Von: Thomas Hofer [mailto:mailinglisten@familie-hofer.net]
Gesendet: Montag, 28. April 2008 13:52
An: dev@sip-communicator.dev.java.net
Betreff: AW: [sip-comm-dev] New Contact Dialog

You're right, but how to implement this:
1) serverstored protocols impmement
OperationSetServerStoredContactInfo,
right?
2) how? The plugin shall provide the identifier?

> And if the contact ID isn't explicit (always depending of the type of
> account) adding a field to set a DisplayName directly.
3) actually, no protocol has per default a explicit display name, I
think.
Am I right?

Cheers, Thomas

> -----Ursprüngliche Nachricht-----
> Von: Damien Roth [mailto:damien.roth@gmail.com]
> Gesendet: Montag, 28. April 2008 11:52
> An: dev@sip-communicator.dev.java.net
> Betreff: Re: [sip-comm-dev] New Contact Dialog
>
> Hi Thomas,
>
> You're right, but for some protocole like MSN, the DisplayName is
> stored on the server.
> In this case, we don't need to specify a DisplayName, and if we set a
> DisplayName, will it be change if the contact set another nickname ?
>
> Why not personalize the word "Identifier" depending on the type of
> account ?
>
> For example :
> SIP : telephone number
> MSN : Email address
> Dict : Dictionary
>
> And if the contact ID isn't explicit (always depending of the type of
> account) adding a field to set a DisplayName directly.
>
> What do you think ?
>
> Cheers
>
> Damien
>
> 2008/4/28 Thomas Hofer <mailinglisten@familie-hofer.net>:
> >
> >
> >
> >
> > Hi! I noticed, that adding a new (SIP) contact is not very
> comfortable and
> > intuitive. You just enter the ID (the telefon number, not everyone
> > recognizes this) and afterwards can rename your contact. I propose
to
> split
> > the dialog, that a DisplayName and the ID can be entered. The
> displayname
> > then shall be the name in the contact list, the telephonnumber (or
> other
> > account id) are then the ID(s) of the selected accounts.
> >
> >
> >
> > What do you think?
> >
> > Cheers, Thomas
>
> ---------------------------------------------------------------------
> 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

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


#13

So. commited (and fixed) the automatic-status-plugin yesterday.

Currently i am working on a better "new contact" dialog, which is
1) more intuitively
2) can add several contacts under one metacontact, which have different
account-ids
3) fixing some bugs in the dialog.

cheers

···

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


#14

Hi!
I've got a problem with the voice quality.
The SIP-Server and SC handshake and the used codec is
ALAW/rtp, 8000.0 Hz, 8-bit, Mono, FrameSize=8 bits

But if I use other clients, the voice quality is much better. They seem to
use other parameters with higher quality, e.g. 16000Hz 16bit.
I found the way to set the preferred codec in MediaControl, but - please -
explain to me, how to set the voice parameters for this codec, so that the
better settings will be used.

Cheers, thomas

···

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


#15

Hi yana! Did you find the time by now?

Cheers, thomas

···

-----Ursprüngliche Nachricht-----
Von: Yana Stamcheva [mailto:yana@sip-communicator.org]
Gesendet: Dienstag, 29. April 2008 13:57
An: dev@sip-communicator.dev.java.net
Betreff: Re: AW: [sip-comm-dev] New Contact Dialog

Hey,

I didn't see the attached images. I'll have a look and reply write you
again.

Cheers,
Yana

Thomas Hofer wrote:
> I've implemented following dialog:
>
>
>
>
>
>
>
> If more than one accounts are added to a new meta-contact, the
metacontact
> can be given a name.
>
> If a protocol is added without serverstored information (like sip)
the
> metacontact can be given a name.
>
> If a protocol is added with serverstored information (like icq) the
> metacontact cannot be given a name.
>
>
>
> I hope this meets all requirements.
>
>
>
> If there are no comments left, I'll commit it in the afternoon.
>
> Yana: you wrote the original code, what do you think of my
> changes/extensions?
>
>
>
> Cheers, Thomas
>
>
>
>
>
>
>
> Von: Thomas Hofer [mailto:mailinglisten@familie-hofer.net]
> Gesendet: Montag, 28. April 2008 11:31
> An: dev@sip-communicator.dev.java.net
> Betreff: [sip-comm-dev] New Contact Dialog
>
>
>
> Hi! I noticed, that adding a new (SIP) contact is not very
comfortable and
> intuitive. You just enter the ID (the telefon number, not everyone
> recognizes this) and afterwards can rename your contact. I propose to
split
> the dialog, that a DisplayName and the ID can be entered. The
displayname
> then shall be the name in the contact list, the telephonnumber (or
other
> account id) are then the ID(s) of the selected accounts.
>
>
>
> What do you think?
>
> Cheers, Thomas
>
>
>
>
>
>
>
>

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


#16

Is the other client using ALAW/rtp?

I think (but I could be mistaken) that ALAW/rtp is supposed to always be 8000hz, according to the standard

http://www.iana.org/assignments/rtp-parameters

Ken

Thomas Hofer wrote:

···

Hi!
I've got a problem with the voice quality. The SIP-Server and SC handshake and the used codec is ALAW/rtp, 8000.0 Hz, 8-bit, Mono, FrameSize=8 bits

But if I use other clients, the voice quality is much better. They seem to
use other parameters with higher quality, e.g. 16000Hz 16bit. I found the way to set the preferred codec in MediaControl, but - please -
explain to me, how to set the voice parameters for this codec, so that the
better settings will be used.

Cheers, thomas

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


#17

Is it planned from someone to create a Skype-Plugin using the Skype API?

Cheers, Thomas

···

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


#18

The other "client" is a softswitch, which has implemented a lot of codecs.
However, we prefer alaw/ulaw, as it should have the best quality. Bandwidth
is not an issue here, aswell.

I think (but I could be mistaken) that ALAW/rtp is supposed to always
be
8000hz, according to the standard

Oh. I'll have to check this>

Cheers, thomas

···

-----Ursprüngliche Nachricht-----
Von: Ken Larson [mailto:forum@larsontechnologies.com]
Gesendet: Dienstag, 29. April 2008 17:02
An: dev@sip-communicator.dev.java.net
Betreff: Re: [sip-comm-dev] Preferred Codec

Is the other client using ALAW/rtp?

I think (but I could be mistaken) that ALAW/rtp is supposed to always
be
8000hz, according to the standard

http://www.iana.org/assignments/rtp-parameters

Ken

Thomas Hofer wrote:
> Hi!
> I've got a problem with the voice quality.
> The SIP-Server and SC handshake and the used codec is
> ALAW/rtp, 8000.0 Hz, 8-bit, Mono, FrameSize=8 bits
>
> But if I use other clients, the voice quality is much better. They
seem to
> use other parameters with higher quality, e.g. 16000Hz 16bit.
> I found the way to set the preferred codec in MediaControl, but -
please -
> explain to me, how to set the voice parameters for this codec, so
that the
> better settings will be used.
>
> Cheers, thomas
>
>
> ---------------------------------------------------------------------
> 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

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


#19

Has anybody yet tried to run SC and/or the installer on a Vista 64bit
System. One of my collegues reports an error, but I've not 64bit Vista here.
Is this a known issue with a workaround? Or do I have to check myself?

Cheers, thomas

···

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


#20

Hey Thomas,

Sorry again for the lag. I am going through my 150+ mail backlog these
days so you'll probably be hearing me apologise quite often :).

I completely agree that we are probably not handling meta contacts
in the most intuitive way now. As a matter of fact, this year we are
once again part of the season of usability program on openusability.org
so Mike Oren, and his mentor Raphael Wimmer (both CCed) would be
contributing to our project input on exactly that subject.

So, back to the topic. I had a look at what you suggest and I basically
like the idea. I also had a look at what we currently have and it seems
to me that our "add contact" wizard is currently slightly inconsistent
since it allows users to choose more than one account but then seems to
ignore all but the first one.

There are still two issues that bother me a bit here:

1. On the first image you have two SIP fields. It would probably be a
good idea to let the user know which account each of these is pertaining
to.

2. (more important) The form does not allow you to enter more than one
contact per account. I agree that few users would need this feature but
some definitely will (e.g. some people have a personal and a biz account
on the same network). I am therefore afraid that this may cause
confusion and make users believe that it is not possible to merge
contacts from the same network.

One solution that I see would be to add a button next to the field that
would say sth like "more users from the same net" and would add extra
fields when clicked. This might make the form overly complicated though
so I am not sure it's a good way to go.

I am curious to know what other people think.

Cheers
Emil

Thomas Hofer написа:

···

Hi yana! Did you find the time by now?

Cheers, thomas

-----Ursprüngliche Nachricht-----
Von: Yana Stamcheva [mailto:yana@sip-communicator.org]
Gesendet: Dienstag, 29. April 2008 13:57
An: dev@sip-communicator.dev.java.net
Betreff: Re: AW: [sip-comm-dev] New Contact Dialog

Hey,

I didn't see the attached images. I'll have a look and reply write you
again.

Cheers,
Yana

Thomas Hofer wrote:

I've implemented following dialog:

If more than one accounts are added to a new meta-contact, the

metacontact

can be given a name.

If a protocol is added without serverstored information (like sip)

the

metacontact can be given a name.

If a protocol is added with serverstored information (like icq) the
metacontact cannot be given a name.

I hope this meets all requirements.

If there are no comments left, I'll commit it in the afternoon.

Yana: you wrote the original code, what do you think of my
changes/extensions?

Cheers, Thomas

Von: Thomas Hofer [mailto:mailinglisten@familie-hofer.net]
Gesendet: Montag, 28. April 2008 11:31
An: dev@sip-communicator.dev.java.net
Betreff: [sip-comm-dev] New Contact Dialog

Hi! I noticed, that adding a new (SIP) contact is not very

comfortable and

intuitive. You just enter the ID (the telefon number, not everyone
recognizes this) and afterwards can rename your contact. I propose to

split

the dialog, that a DisplayName and the ID can be entered. The

displayname

then shall be the name in the contact list, the telephonnumber (or

other

account id) are then the ID(s) of the selected accounts.

What do you think?

Cheers, Thomas

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

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