pmg-gui/js/MailProxyTLSPanel.js
Stoiko Ivanov 0f5a92f010 rename TLSDomain to TLSDestination
with the changes for fixing #1948 it is now possible to define tls policies
for destinations (remote domains or next-hop transports) instead of only for
Domains.
This patch reflects this addition by renaming all occurences of Domain with
Destination.

Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
Reviewed-By: Dominik Csapak <d.csapak@proxmox.com>
2020-03-24 18:10:51 +01:00

37 lines
775 B
JavaScript

Ext.define('PMG.MailProxyTLSPanel', {
extend: 'Ext.panel.Panel',
alias: 'widget.pmgMailProxyTLSPanel',
layout: {
type: 'vbox',
align: 'stretch'
},
bodyPadding: '0 0 10 0',
defaults: {
collapsible: true,
animCollapse: false,
margin: '10 10 0 10'
},
initComponent: function() {
var me = this;
var tlsSettings = Ext.create('PMG.MailProxyTLS', {
title: gettext('Settings')
});
var tlsDestinations = Ext.create('PMG.MailProxyTLSDestinations', {
title: gettext('TLS Destination Policy'),
flex: 1
});
me.items = [ tlsSettings, tlsDestinations ];
me.callParent();
tlsSettings.relayEvents(me, ['activate', 'deactivate', 'destroy']);
tlsDestinations.relayEvents(me, ['activate', 'deactivate', 'destroy']);
}
});