Update icons

Readme.md

@@ -38,12 +38,15 @@ The hierarchical view allows for a quick understanding what is going on on your
 ![screencast](https://user-images.githubusercontent.com/7721625/52979302-3f073b80-33d5-11e9-9953-b70ebb349439.gif)
 
 ## Performance
-This App is optimized to handle thousands of topics and at least hundreds of thousands messages per minute.
-So don't worry if you got >=30k topics and >=100.000 messages per minute.
 
-One can also subscribe to custom topics insted of the "root wildcard #", therefore limiting the amount of messages.
+This App is optimized to handle thousands of topics and at hundreds of thousands messages per minute.
+
+In very large productive environments brokers may handle an exteme load of topics.
+Subscribing with a wildcard topic is in this scenario not adviced.
+To avoid a scenario where the MQTT-Explorer would have to handle millions of updates, one can set up custom subscriptions in the "Advanced" connection settings.
 
 ## Develop
+
 PRs and issues are welcome
 
 Install with `npm run install`, build with `npm run build`
@@ -53,22 +56,27 @@ Start with `npm run start`
 The `app` directory contains all the rendering logic, the `backend` directory currently contains the models, tests, connection management.
 
 ## Automated Tests
+
 To achieve a reliable product automated tests run regulary on travis.
+
 - Data model
 - MQTT integration
 - UI-Tests (The demo is a recorded ui test)
 
 ## Telemetry
-The App sends telemetry and error reports, this enables me to quickly react on bugs/errors I produced.
-This is a difficutlt task since this App runs on three different operating systems and architectures.
+
+No personal data is processed, sent or stored.
+
+The app sends telemetry and error reports, this enables me to quickly react on bugs/errors and understand what's going on.
+The app runs on winows, linux and mac and has thousands of users. Responding quickly to bugs is essential.
+This greatly helps to improve the software quality and reliability.
 
 It basically sends: app version, processor architecture, operating system, used memory, user interactions and error stacks.
 
-This greatly helps to improve the software quality and reliability.
-No data about you or your data is send or stored.
-Even thoug the data is purely technical, an option to disable telemetry is planned. [#52](https://github.com/thomasnordquist/MQTT-Explorer/issues/52)
+<details>
+<summary>Example telemetry</summary>
+<p>
 
-Example telemetry:
 ```javascript
 { system: { arch: 'x64', platform: 'darwin' },
   appVersion: '0.0.7',
@@ -84,5 +92,10 @@ Example telemetry:
   transactionId: '53bf9aac-e695-40cc-9a81-b1cf3398843d' }
 ```
 
+</p>
+</details>
+
+Even thoug the data is purely technical, an option to disable telemetry is planned. [#52](https://github.com/thomasnordquist/MQTT-Explorer/issues/52)
+
 ## License
 [AGPL 3](./LICENSE)

Readme.tpl.md

@@ -4,6 +4,8 @@
 [![Build_Status](https://travis-ci.org/thomasnordquist/MQTT-Explorer.svg?branch=master)](https://travis-ci.org/thomasnordquist/MQTT-Explorer)
 [![Build status](https://ci.appveyor.com/api/projects/status/c35tkm29rm4m5364/branch/master?svg=true)](https://ci.appveyor.com/project/thomasnordquist/mqtt-explorer/branch/master)
 
+<img src="./icon.png" height="48" />
+
 ### Version {{ version }}
 
 A MQTT Tool to get a quick overview of your MQTT topics and integrate new devices/services more efficiently.
@@ -38,12 +40,15 @@ The hierarchical view allows for a quick understanding what is going on on your
 ![screencast](https://user-images.githubusercontent.com/7721625/52979302-3f073b80-33d5-11e9-9953-b70ebb349439.gif)
 
 ## Performance
-This App is optimized to handle thousands of topics and at least hundreds of thousands messages per minute.
-So don't worry if you got >=30k topics and >=100.000 messages per minute.
 
-One can also subscribe to custom topics insted of the "root wildcard #", therefore limiting the amount of messages.
+This App is optimized to handle thousands of topics and at hundreds of thousands messages per minute.
+
+In very large productive environments brokers may handle an exteme load of topics.
+Subscribing with a wildcard topic is in this scenario not adviced.
+To avoid a scenario where the MQTT-Explorer would have to handle millions of updates, one can set up custom subscriptions in the "Advanced" connection settings.
 
 ## Develop
+
 PRs and issues are welcome
 
 Install with `npm run install`, build with `npm run build`
@@ -53,22 +58,27 @@ Start with `npm run start`
 The `app` directory contains all the rendering logic, the `backend` directory currently contains the models, tests, connection management.
 
 ## Automated Tests
+
 To achieve a reliable product automated tests run regulary on travis.
+
 - Data model
 - MQTT integration
 - UI-Tests (The demo is a recorded ui test)
 
 ## Telemetry
-The App sends telemetry and error reports, this enables me to quickly react on bugs/errors I produced.
-This is a difficutlt task since this App runs on three different operating systems and architectures.
+
+No personal data is processed, sent or stored.
+
+The app sends telemetry and error reports, this enables me to quickly react on bugs/errors and understand what's going on.
+The app runs on winows, linux and mac and has thousands of users. Responding quickly to bugs is essential.
+This greatly helps to improve the software quality and reliability.
 
 It basically sends: app version, processor architecture, operating system, used memory, user interactions and error stacks.
 
-This greatly helps to improve the software quality and reliability.
-No data about you or your data is send or stored.
-Even thoug the data is purely technical, an option to disable telemetry is planned. [#52](https://github.com/thomasnordquist/MQTT-Explorer/issues/52)
+<details>
+<summary>Example telemetry</summary>
+<p>
 
-Example telemetry:
 ```javascript
 { system: { arch: 'x64', platform: 'darwin' },
   appVersion: '0.0.7',
@@ -84,5 +94,10 @@ Example telemetry:
   transactionId: '53bf9aac-e695-40cc-9a81-b1cf3398843d' }
 ```
 
+</p>
+</details>
+
+Even thoug the data is purely technical, an option to disable telemetry is planned. [#52](https://github.com/thomasnordquist/MQTT-Explorer/issues/52)
+
 ## License
 [AGPL 3](./LICENSE)

package.json

@@ -1,6 +1,6 @@
 {
   "name": "MQTT-Explorer",
-  "version": "0.2.1-alpha6",
+  "version": "0.2.1-alpha7",
   "description": "Explore your message queues",
   "main": "dist/src/electron.js",
   "scripts": {
@@ -23,10 +23,12 @@
     "appId": "mqtt-explorer",
     "nodeGypRebuild": false,
     "mac": {
-      "category": "de.t7n.apps.mqtt-explorer",
+      "appId": "de.t7n.apps.mqtt-explorer",
+      "category": "public.app-category.developer-tools",
       "publish": [
         "github"
-      ]
+      ],
+      "provisioningProfile": "res/MQTT_Explorer_Store_Distribution_Profile.provisionprofile"
     },
     "linux": {
       "category": "Development",

src/spec/scenarios/connect.ts

@@ -6,6 +6,8 @@ export async function connectTo(host: string, browser: Browser<void>) {
   await writeTextToInput('Username', 'thomas', browser, false)
   await writeTextToInput('Password', 'bierbier', browser, false)
 
+  await browser.saveScreenshot('screen1.png')
+
   const connectButton = await browser.$('//button/span[contains(text(),"Connect")]')
   clickOn(connectButton, browser)
 }

src/spec/scenarios/showJsonPreview.ts

@@ -3,6 +3,6 @@ import { expandTopic, sleep } from '../util'
 
 export async function showJsonPreview(browser: Browser<void>) {
   await expandTopic('actuality/showcase', browser)
-
+  await browser.saveScreenshot('screen3.png')
   await sleep(1000)
 }

src/spec/scenarios/showMenu.ts

@@ -9,6 +9,8 @@ export async function showMenu(browser: Browser<void>) {
   // moveToCenterOfElement(brokerStatistics, browser)
   await sleep(2000)
 
+  await browser.saveScreenshot('screen4.png')
+
   const topicOrder = await browser.$('#select-node-order')
   await clickOn(topicOrder, browser)
   await sleep(1000)

src/spec/scenarios/showNumericPlot.ts

@@ -5,7 +5,7 @@ export async function showNumericPlot(browser: Browser<void>) {
   await expandTopic('livingroom/temperature', browser)
 
   await clickOnHistory(browser)
-
+  await browser.saveScreenshot('screen2.png')
   await sleep(1000)
   await expandTopic('livingroom/humidity', browser)
 }