napcok/calamares
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
7a7e2b16cb
calamares/src/modules/tracking/page_trackingstep.ui

248 lines
7.8 KiB
Plaintext
Raw Normal View History

Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it *possible* for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module.
2017-08-29 14:00:37 +02:00
<?xml version="1.0" encoding="UTF-8"?>
<ui version="4.0">
<class>TrackingPage</class>
<widget class="QWidget" name="TrackingPage">
<property name="geometry">
<rect>
<x>0</x>
<y>0</y>
<width>799</width>
<height>400</height>
</rect>
</property>
<property name="windowTitle">
<string>Form</string>
</property>
<layout class="QHBoxLayout" name="horizontalLayout">
<item>
[tracking] Polish UI some more - Enable translations, substitute ShortProductName into string, - Simplify code for enabling tracking option blocks, - Set checkboxes based on configuration, - Read checkboxes when leaving page, - Don't stretch the tracking option blocks.
2017-11-08 10:25:36 +01:00
<layout class="QVBoxLayout" name="verticalLayout" stretch="0,0,0,0">
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it *possible* for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module.
2017-08-29 14:00:37 +02:00
<item>
<widget class="QGroupBox" name="installTrackingBox">
<property name="title">
<string>Install Tracking</string>
</property>
<layout class="QVBoxLayout" name="verticalLayout_3">
<item>
<layout class="QVBoxLayout" name="verticalLayout_2">
<item>
[tracking] Polish UI a bit - add icons for graphical display of actions - extend description of tracking options - add debug logging - enable next button - show/hide tracking options based on configuration
2017-11-06 16:12:41 +01:00
<layout class="QHBoxLayout" name="horizontalLayout_2">
<item>
<widget class="QLabel" name="installActionIcon">
<property name="maximumSize">
<size>
<width>64</width>
<height>64</height>
</size>
</property>
<property name="baseSize">
<size>
<width>64</width>
<height>64</height>
</size>
</property>
<property name="text">
<string/>
</property>
<property name="pixmap">
<pixmap resource="page_trackingstep.qrc">:/tracking/phone.png</pixmap>
</property>
</widget>
</item>
<item>
<widget class="QLabel" name="installExplanation">
<property name="text">
[tracking] Polish UI some more - Enable translations, substitute ShortProductName into string, - Simplify code for enabling tracking option blocks, - Set checkboxes based on configuration, - Read checkboxes when leaving page, - Don't stretch the tracking option blocks.
2017-11-08 10:25:36 +01:00
<string>Placeholder text</string>
[tracking] Polish UI a bit - add icons for graphical display of actions - extend description of tracking options - add debug logging - enable next button - show/hide tracking options based on configuration
2017-11-06 16:12:41 +01:00
</property>
<property name="textFormat">
<enum>Qt::RichText</enum>
</property>
<property name="wordWrap">
<bool>true</bool>
</property>
</widget>
</item>
<item>
<widget class="QToolButton" name="toolButton">
<property name="text">
<string>...</string>
</property>
<property name="icon">
<iconset resource="page_trackingstep.qrc">
<normaloff>:/tracking/data/images/information.svgz</normaloff>:/tracking/data/images/information.svgz</iconset>
</property>
<property name="arrowType">
<enum>Qt::NoArrow</enum>
</property>
</widget>
</item>
</layout>
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it *possible* for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module.
2017-08-29 14:00:37 +02:00
</item>
<item>
[tracking] Polish UI some more - Enable translations, substitute ShortProductName into string, - Simplify code for enabling tracking option blocks, - Set checkboxes based on configuration, - Read checkboxes when leaving page, - Don't stretch the tracking option blocks.
2017-11-08 10:25:36 +01:00
<widget class="QCheckBox" name="installCheckBox">
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it *possible* for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module.
2017-08-29 14:00:37 +02:00
<property name="text">
<string>Enable install-tracking</string>
</property>
</widget>
</item>
</layout>
</item>
</layout>
</widget>
</item>
<item>
<widget class="QGroupBox" name="machineTrackingBox">
<property name="title">
<string>Machine Tracking</string>
</property>
<layout class="QVBoxLayout" name="verticalLayout_7">
<item>
<layout class="QVBoxLayout" name="verticalLayout_4">
<item>
[tracking] Polish UI a bit - add icons for graphical display of actions - extend description of tracking options - add debug logging - enable next button - show/hide tracking options based on configuration
2017-11-06 16:12:41 +01:00
<layout class="QHBoxLayout" name="horizontalLayout_3">
<item>
<widget class="QLabel" name="machineActionIcon">
<property name="maximumSize">
<size>
<width>64</width>
<height>64</height>
</size>
</property>
<property name="baseSize">
<size>
<width>64</width>
<height>64</height>
</size>
</property>
<property name="text">
<string/>
</property>
<property name="pixmap">
<pixmap resource="page_trackingstep.qrc">:/tracking/machine.png</pixmap>
</property>
</widget>
</item>
<item>
<widget class="QLabel" name="machineExplanation">
<property name="text">
[tracking] Polish UI some more - Enable translations, substitute ShortProductName into string, - Simplify code for enabling tracking option blocks, - Set checkboxes based on configuration, - Read checkboxes when leaving page, - Don't stretch the tracking option blocks.
2017-11-08 10:25:36 +01:00
<string>Placeholder text</string>
[tracking] Polish UI a bit - add icons for graphical display of actions - extend description of tracking options - add debug logging - enable next button - show/hide tracking options based on configuration
2017-11-06 16:12:41 +01:00
</property>
<property name="wordWrap">
<bool>true</bool>
</property>
</widget>
</item>
<item>
<widget class="QToolButton" name="toolButton_2">
<property name="text">
<string>...</string>
</property>
<property name="icon">
<iconset resource="page_trackingstep.qrc">
<normaloff>:/tracking/data/images/information.svgz</normaloff>:/tracking/data/images/information.svgz</iconset>
</property>
</widget>
</item>
</layout>
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it *possible* for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module.
2017-08-29 14:00:37 +02:00
</item>
<item>
[tracking] Polish UI some more - Enable translations, substitute ShortProductName into string, - Simplify code for enabling tracking option blocks, - Set checkboxes based on configuration, - Read checkboxes when leaving page, - Don't stretch the tracking option blocks.
2017-11-08 10:25:36 +01:00
<widget class="QCheckBox" name="machineCheckBox">
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it *possible* for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module.
2017-08-29 14:00:37 +02:00
<property name="text">
<string>Enable machine-tracking</string>
</property>
</widget>
</item>
</layout>
</item>
</layout>
</widget>
</item>
<item>
[tracking] Polish UI some more - Enable translations, substitute ShortProductName into string, - Simplify code for enabling tracking option blocks, - Set checkboxes based on configuration, - Read checkboxes when leaving page, - Don't stretch the tracking option blocks.
2017-11-08 10:25:36 +01:00
<widget class="QGroupBox" name="userTrackingBox">
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it *possible* for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module.
2017-08-29 14:00:37 +02:00
<property name="title">
<string>User Tracking</string>
</property>
<layout class="QVBoxLayout" name="verticalLayout_6">
<item>
<layout class="QVBoxLayout" name="verticalLayout_5">
<item>
[tracking] Polish UI a bit - add icons for graphical display of actions - extend description of tracking options - add debug logging - enable next button - show/hide tracking options based on configuration
2017-11-06 16:12:41 +01:00
<layout class="QHBoxLayout" name="horizontalLayout_4">
<item>
<widget class="QLabel" name="userActionIcon">
<property name="maximumSize">
<size>
<width>64</width>
<height>64</height>
</size>
</property>
<property name="baseSize">
<size>
<width>64</width>
<height>64</height>
</size>
</property>
<property name="text">
<string/>
</property>
<property name="pixmap">
<pixmap resource="page_trackingstep.qrc">:/tracking/binoculars.png</pixmap>
</property>
</widget>
</item>
<item>
<widget class="QLabel" name="userExplanation">
<property name="text">
[tracking] Polish UI some more - Enable translations, substitute ShortProductName into string, - Simplify code for enabling tracking option blocks, - Set checkboxes based on configuration, - Read checkboxes when leaving page, - Don't stretch the tracking option blocks.
2017-11-08 10:25:36 +01:00
<string>Placeholder text</string>
[tracking] Polish UI a bit - add icons for graphical display of actions - extend description of tracking options - add debug logging - enable next button - show/hide tracking options based on configuration
2017-11-06 16:12:41 +01:00
</property>
<property name="wordWrap">
<bool>true</bool>
</property>
</widget>
</item>
<item>
<widget class="QToolButton" name="toolButton_3">
<property name="text">
<string>...</string>
</property>
<property name="icon">
<iconset resource="page_trackingstep.qrc">
<normaloff>:/tracking/data/images/information.svgz</normaloff>:/tracking/data/images/information.svgz</iconset>
</property>
</widget>
</item>
</layout>
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it *possible* for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module.
2017-08-29 14:00:37 +02:00
</item>
<item>
[tracking] Polish UI some more - Enable translations, substitute ShortProductName into string, - Simplify code for enabling tracking option blocks, - Set checkboxes based on configuration, - Read checkboxes when leaving page, - Don't stretch the tracking option blocks.
2017-11-08 10:25:36 +01:00
<widget class="QCheckBox" name="userCheckBox">
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it *possible* for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module.
2017-08-29 14:00:37 +02:00
<property name="text">
<string>Enable user-tracking</string>
</property>
</widget>
</item>
</layout>
</item>
</layout>
</widget>
</item>
[tracking] Polish UI some more - Enable translations, substitute ShortProductName into string, - Simplify code for enabling tracking option blocks, - Set checkboxes based on configuration, - Read checkboxes when leaving page, - Don't stretch the tracking option blocks.
2017-11-08 10:25:36 +01:00
<item>
<spacer name="verticalSpacer">
<property name="orientation">
<enum>Qt::Vertical</enum>
</property>
<property name="sizeHint" stdset="0">
<size>
<width>20</width>
<height>40</height>
</size>
</property>
</spacer>
</item>
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it *possible* for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module.
2017-08-29 14:00:37 +02:00
</layout>
</item>
</layout>
</widget>
[tracking] Polish UI a bit - add icons for graphical display of actions - extend description of tracking options - add debug logging - enable next button - show/hide tracking options based on configuration
2017-11-06 16:12:41 +01:00
<resources>
<include location="page_trackingstep.qrc"/>
</resources>
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it *possible* for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module.
2017-08-29 14:00:37 +02:00
<connections/>
</ui>
Reference in New Issue Copy Permalink