Would it be possible to see a screenshot of this before we get it in?

Also, statements like "the GUI alread has a lot of problems" kind of worry
me because they sound as an excuse to pile up new ones.

--sent from my mobile
On 20 Apr 2014 12:40 PM, "Ingo Bauersachs" <notifications@github.com> wrote:

> In
> src/net/java/sip/communicator/plugin/accountinfo/AccountDetailsPanel.java:
>
> > +        stringBuffer.append(
> > +            "<html><body><p align=\"left\">"
> > +                + "<font color=\"" + fontColor + "\" size=\"3\">");
> > +
> > +        // Protocol name
> > +        stringBuffer.append(getLineString(R.getI18NString(
> > +                "service.gui.PROTOCOL"), protocolProvider.getProtocolName()));
> > +
> > +        // Server address and port
> > +        stringBuffer.append(getLineString(R.getI18NString(
> > +                "service.gui.ADDRESS"),
> > +                protocolProvider.getAccountID().getServerAddress()));
> > +        stringBuffer.append(getLineString(R.getI18NString(
> > +                "service.gui.PORT"),
> > +                protocolProvider.getAccountID().getServerPort()));
> > +
>
> From the active socket, so for XMPP, through the same way you obtain the
> TLS information. For SIP, same complicated story as a couple of months ago.
>
> Maybe a new OpSetConnectionInfo would make sense? The OpSetTls could then
> be derived from it and the isSecure() method (or similar) on the
> ProtocolProviderService could be moved there.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jitsi/jitsi/pull/26/files#r11797515>
> .
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev
>