It would probably be better to use the InetAddress class to validate the
address string rather than a regular expression of your own. This way
you would be certain that you are not missing any non-common cases such
as different IPv6 address forms for example. Besides, if you use
InetAddress.getByName() this would also give you a DNS check for FQDNs.
Thanks for the idea of using the InetAddress class. We have some
missing patterns, currently we are only matching textual web address
(like dict.org or all.dict.org) and not IP v4 or v6 address.
Could you please explain what exactly is the difference between your
AddContactPanel and the default one?
The difference between the AddContactPanel presented and the default
one is the presence of a combo box in place of a text field. I don't
remember if we explain this in a previous mail, but the dictionaries
code used in the servers are not easy to know. So it's more easy to
get the list (code + description) from the server and display it as a
I heard that the LAPD protocol will be implemented in SC, this system
might be usefull and it seams that a solution was found by some SC
Hmmm. Be careful with this one. I doubt that anyone that doesn't know
the protocol in detail would know what a "strategy" is. I guess it would
be best to simply pick a default one and hide the combo box in an
"Advanced" tab so that it would not confuse users. WDYT?
Today we had a meeting with Vincent Lucas (who support us) and we also
come to the same result. We decided to automatically select the first
possible strategy. More we will add some explanations below the combo
According to our schedule, we sould publish on the mailing list a
patch containing the implementation of the Dict protocol and the add
contact wizard. We hope it will be functional by then.
Other than that, I think this is a great project so good luck, guys!
Thanks a lot for your encouragement.
Damien & Cédric
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com