No clue why, because the window is never shown. Does not seem to happen on Linux. Suggestions and fixes very welcome.

Is this a bug or a feature request?

Bug.

What Pext version are you running?

Pext v0.11.1-19-g4ca9d49

What OS are you using? (e.g.: Ubuntu 16.04, Windows 10, macOS High Sierra)

Arch Linux.

If this is a bug:

What did you do to run into this bug, step-by-step?

1. Open Pext and load radiobrowser
2. Close Pext
3. Open Pext in the terminal
4. Choose 'Close Active Module' in the 'Modules' menu
5. Observe the terminal

What did you expect would happen?

No terminal garbage.

What actually happened?

koz@Sebastian ~]$ pext
python3-opengl is not installed. If Pext fails to render, please try installing it. See https://github.com/Pext/Pext/issues/11.
Using locale: en_NZ 
Localization loaded: True
WARN: Module radiobrowser uses old process_response signature and will not be able to receive an identifier if requested
file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Desktop/TabViewStyle.qml:92:9: QML StyleItem: Cannot anchor to an item that isn't a parent or sibling.
file:///usr/lib/python3.6/site-packages/pext/qml/ModuleData.qml:200: TypeError: Cannot read property 'currentIndex' of null
file:///usr/lib/python3.6/site-packages/pext/qml/ModuleData.qml:200: TypeError: Cannot read property 'currentIndex' of null
file:///usr/lib/python3.6/site-packages/pext/qml/ModuleData.qml:200: TypeError: Cannot read property 'currentIndex' of null
file:///usr/lib/python3.6/site-packages/pext/qml/ModuleData.qml:200: TypeError: Cannot read property 'currentIndex' of null
file:///usr/lib/python3.6/site-packages/pext/qml/ModuleData.qml:200: TypeError: Cannot read property 'currentIndex' of null
file:///usr/lib/python3.6/site-packages/pext/qml/ModuleData.qml:200: TypeError: Cannot read property 'currentIndex' of null
file:///usr/lib/python3.6/site-packages/pext/qml/ModuleData.qml:200: TypeError: Cannot read property 'currentIndex' of null
file:///usr/lib/python3.6/site-packages/pext/qml/ModuleData.qml:200: TypeError: Cannot read property 'currentIndex' of null
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:258: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:343: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:110: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:111: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:132: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:133: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:187: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:188: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:354: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:76: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:93: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:76: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:93: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/FocusFrame.qml:64: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Desktop/FocusFrameStyle.qml:51: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:258: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:343: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:110: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:111: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:132: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:133: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:187: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:188: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:354: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:76: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:93: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:76: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:93: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/FocusFrame.qml:64: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Desktop/FocusFrameStyle.qml:51: ReferenceError: parent is not defined
file:///usr/lib/python3.6/site-packages/pext/qml/ModuleData.qml:145: TypeError: Cannot read property of null
file:///usr/lib/qt/qml/QtQuick/Controls/Private/Control.qml:90: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:258: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:343: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:110: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:111: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:132: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:133: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:187: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:188: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:354: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:76: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:93: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:76: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:93: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/FocusFrame.qml:64: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Desktop/FocusFrameStyle.qml:51: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:258: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:343: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:110: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:111: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:132: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:133: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:187: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollViewHelper.qml:188: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:354: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:76: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:93: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:76: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/ScrollBar.qml:93: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/FocusFrame.qml:64: ReferenceError: parent is not defined
file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Desktop/FocusFrameStyle.qml:51: ReferenceError: parent is not defined

This did not crash Pext.

Is there anything else you would like to add?

No.

qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: QSslSocket: cannot resolve SSLeay_version
qt.network.ssl: Incompatible version of OpenSSL
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init

This is why Debian needs libssl1.0-dev, not sure which exact package is needed for Fedora.

it would be nice if pext would list first commands that were already ran. this is what tools like rofi do and make them super useful...

Packaging Pext a bit better would be nice. It can already be installed under Linux just fine using setup.py, but on macOS, that support is very lacking. macOS support or maybe an AppImage or Snap or so would be awesome.

Edit: If you're here for Hacktoberfest, support for a single of the following formats would suffice:
macOS App
AppImage
Snap
Flatpak
Deb
RPM

Edit 2: title changed to Linux packaging because that's what's being done.

Currently, the update-checker checks for updates every time Pext is launched. This is not good for several reasons:

• It causes an unnecessary requests every time an user switches theme, profile or just restarts Pext for whatever reason.
• It doesn't notify users who leave Pext running for a very long time without restarting it, like those that do not shut down their laptop every day, which is an intended use case.

Due to these issues making the update checking unreliable for intended use cases of Pext, I consider this a bug.

The correct behaviour would probably be as follows:

• Write to a file when the last update check was
• Check this file when:
  • Launching Pext
  • Every X amount of time
• If the last check was too long ago, check for an update

An appropriate time to check for updates must be chosen. Every 24 hours? Something else?

Maybe make this i18n-able, maybe hide it completely from Pext (as most users will only use 1 profile anyway)

Unity had a really cool feature called HUD that allowed you to search through the application menus of the active application. It would be really cool if Pext could have a module for this too, but I haven't found any way to do this in Python.

Documentation: https://wiki.ubuntu.com/Unity/HUD
There also seems to be a KRunner extension for it: https://afiestas.org/appmenu-runner-meet-the-kde-hud/ (SSL seems broken, but the page works)
GNOME Shell plugin: https://github.com/p-e-w/plotinus
MATE app (seems most promising): https://github.com/ubuntu-mate/mate-hud

If anyone has an idea on how to do this, or even implement it themselves, that would be amazing. Please state any useful info in this issue.

Screenshots:
Unity

Hey everyone,

I'm starting to feel like automatically adding people (with their email) to the list of translators in the Pext about screen was not the right way to go about it. From now on, this translator list will be opt-in.

If you see this issue, and you want to be on the list, please tell me (and how you want to be referred to) and I will add you (if you have made a good translation contribution).

I'm pinging everyone who is currently considered a real translator, so you can make clear if you want to be on this list or not, and if you do, with what info: @VenomousDingo, @ata2001, @Vistaus, @s8321414, @comradekingu.

For (future) translators who do not have a GitHub account, you are free to contact me directly as well: https://hackerchick.me/#contact.

Is this a bug or a feature request?

Bug.

What Pext version are you running?

Pext v0.11.1-19-g4ca9d49 (according to pext --version)

What OS are you using? (e.g.: Ubuntu 16.04, Windows 10, macOS High Sierra)

Arch Linux.

If this is a bug:

What did you do to run into this bug, step-by-step?

1. Start Pext in the terminal and load radiobrowser
2. Start some music playin'
3. Go to 'By Most Tune-Ins' (I think - I don't exactly recall what triggered this)
4. Observe this lovely dump in your terminal

[koz@Sebastian ~]$ pext
python3-opengl is not installed. If Pext fails to render, please try installing it. See https://github.com/Pext/Pext/issues/11.
Using locale: en_NZ 
Localization loaded: True
python3-opengl is not installed. If Pext fails to render, please try installing it. See https://github.com/Pext/Pext/issues/11.
Using locale: en_NZ 
Localization loaded: True
WARN: Module radiobrowser uses old process_response signature and will not be able to receive an identifier if requested
WARN: Module radiobrowser caused exception list index out of range
Counting objects: 59, done.
Total 59 (delta 0), reused 0 (delta 0), pack-reused 59
Checking out HEAD
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/pext/__main__.py", line 593, in run
    self._process_tab_action(tab, active_tab)
  File "/usr/lib/python3.6/site-packages/pext/__main__.py", line 554, in _process_tab_action
    tab['vm'].context_menu_base = action[1]
IndexError: list index out of range

This did not force a module unload or crash Pext - music kept playing.

What did you expect would happen?

Terminal spew not occur, especially indicating out-of-range issues.

What actually happened?

See note above.

Is there anything else you would like to add?

No.

This would be useful, of course with user permission. It's easy to forget updates if you always have to check manually

Right now, modules can be translated, but the metadata file containing the description and so can't. Modules should be completely i18n-able.

While the pext_base and pext_helpers contain all the info necessary to write a module and the other modules can reasonably easily be used as examples, some proper documentation and guides would be good to have.

Look into software like Sphinx to document it, preferably the documentation should also be able to read the function and class comments of the helper files and put those in the generated documentation.

See https://travis-ci.org/Pext/Pext/jobs/295989017#L4811-L4822.

Pext should exit with an exit status != 0 when plugin installations fail. That'll make testing its functionality on build services like Travis a lot easier.

• Switch profile (done in e85b060)
• Open profile in new window (done in 396a9bd)
• Create profile (done in e34e266)
• Delete profile (done in e34e266)
• Rename profile (done in 5c60036)

These functions still can't notice if their request in Pext fails. Something needs to be found for that in the future.

Is this a bug or a feature request?

Bug.

What Pext version are you running?

Pext v0.11.1-19-g4ca9d49 (according to pext --version)

What OS are you using? (e.g.: Ubuntu 16.04, Windows 10, macOS High Sierra)

Arch Linux, with KDE as my DE.

If this is a bug:

What did you do to run into this bug, step-by-step?

Open Pext and looked at the logo with KDE's Breeze Dark theme.

What did you expect would happen?

The logo wouldn't look bad.

What actually happened?

Black text of 'Pext' on a dark grey background lacks contrast and looks bad.

Is there anything else you would like to add?

I think having a dark-theme-friendly logo would be ideal. While I understand dark theme detection isn't easy or even possible, this would be a great UI improvement.

Pext has gotten rather far and stable, so it's about time for a 1.0 release.

Checklist of things that should be supported before it:

• Internationalisation support for module metadata
• Moving selection_made calls into a thread so modules can't lock the UI up there (be very careful here to not break anything!) dd4056b
• Ensure the API can't crash Pext with bad input
• Update checking for Pext itself, at least to notify about new versions (possibly disable in AppImage due to native support) 0fcd40a

Great to have before the release but not required:

• AppImage (see #31)

• Working macOS .app (see #27)

• Windows installer

• Automatic module updates (on/off for checking and auto-updating in UI)

When all of the above (aside perhaps the great to haves) are done:

• Translations 100% (not required)

Modules get loaded into memory, so can keep running, but may try to use other files bundled with it, which would break horribly if it's uninstalled and the module tries to load it. It'd make the lives of module developers easier if they could assume that they files will just be there.

Well, this is extremely annoying, guess installing AND updating Pext modules is now broken on Debian.

libgit2/pygit2#644

Upstream bugs:
https://bugs.launchpad.net/ubuntu/+source/libgit2/+bug/1595565
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832798

This manifests in the following error:
_pygit2.GitError: Failed to resolve address for https: Name or service not known

It should be possible to change the theming without restarting. Research is needed on how to best do this. Info very welcome.

This already works on Linux and macOS, but Windows currently doesn't support the way this is done. Will need fixing at some point.

The problem is specifically around

Is this a bug or a feature request?

Bug.

What Pext version are you running?

Pext v0.11.1-19-g4ca9d49 (according to pext --version)

What OS are you using? (e.g.: Ubuntu 16.04, Windows 10, macOS High Sierra)

Arch Linux.

If this is a bug:

What did you do to run into this bug, step-by-step?

1. Attempt to install the openweathermap module from the menu.

What did you expect would happen?

No terminal spew.

What actually happened?

QXcbConnection: XCB error: 3 (BadWindow), sequence: 18474, resource id: 29563959, major code: 40 (TranslateCoords), minor code: 0

This did not crash Pext.

Is there anything else you would like to add?

No.

is there a way to change the colors and look of pext?

Due to an upstream Qt bug: https://bugreports.qt.io/browse/QTBUG-53189.

Like #31 and #27, but for Windows.

❤️ Pext, looks super useful!

What is a good place to collect ideas about potentially interesting modules (if some developers would like to pick them up and implement them or suggest improvements)? How about collecting suggestions in this issue + creating one issue per suggested module? Should this discussion happen here or should a separate repo be created for this?

Pext is written in Python3 so it needs dulwich for Python3. Unfortunately, both python-dulwich packages from AUR contain dulwich for Python2

You could just install it from PyPi using pip3 install dulwich --user

Add some settings menu with at least the following option:

Minimize when done:

• Minimize to tray (Linux default)
• Minimize normally (macOS default)
• Don't minimize (maybe? Not sure yet)

Preferably, also add:

• Show tray icon
• Language selector
• Clipboard selection

(Aka: everything that's currently CLI only)

These are purely UI changes. We can just fire off multiple *Requests, which will also neatly make use of multithreading.

Pext should probably mostly run on Windows (Python 3 + Qt5), but this has never been tested as I do not own a Windows machine. Getting the core to start on Windows with instructions would be great. It is acceptable if it does not install modules yet or crashes when trying to send a notification, as those are still hardcoded to notify-send and "git". It is also acceptable if this uses WSL, although the more "native" the better.

So, to summarize:

• Test if Pext can run under Windows
• Write instructions for the README on how to do so
• Document what works and what doesn't work yet

As I may not be able to have access to a Windows machine to verify your work (although I will try!), please add a video or screenshots as proof if possible. The main need is to make sure Pext at least launches on Windows, to hopefully invite further collaboration to ensure ongoing Windows compatibility, either by you or someone else.

Options for the sorting menu per module (especially Pass):
Alphanumerical (Ascending/Descending)
By Created (Ascending/Descending)
Last Modified (Ascending/Descending)
Last Used

Opening a tab with launcher fails (immediately closes the tab) and gives this error message in the bottom of the window:
launcher: Exception thrown: replace_command_info_dict

in the underlying console, Pext gives:
WARN: Module pass uses old process_response signature and will not be able to receive an identifier if requested

System info:

$ uname -a
Darwin [hostname] 15.6.0 Darwin Kernel Version 15.6.0: Tue Apr 11 16:00:51 PDT 2017; root:xnu-3248.60.11.5.3~1/RELEASE_X86_64 x86_64
$ python3 --version
Python 3.5.3
$ 

Any info is appreciated, thank you.

As title says, hope we can see translation version for this tool 😄

Either for running directly, a way to manage dependencies should be a minimum requirement for a software distribution like this.

It's about time this part of pure UI code gets moved into QML for consistency with literally everything else.

Hi,

Despite all dependencies being installed, I receive the following error when trying to run the app:

Pext/main.qml:18 module "QtQuick" version 2.5 is not installed

I'm running this on Debian Jessie.

All the dependencies have been installed correctly.
Installed using pip3 install . --upgrade.
Opens a blank window and throws the same errors multiple times in the terminal.

QOpenGLShaderProgram: could not create shader program
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
shader compilation failed:
""
QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked
QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked

This will be rather complex, and won't be any time soon, but will be basically the following:

• All modules should run in their own process
• There should be a file defining what a module can do (like where to read/write files)
• Jail the modules properly

Look into something like firejail, but cross platform.

Discussions and suggestions welcome.

Pext is long overdue on some CI. Travis is probably the most logical choice. Making sure Pext runs and the (code standard) tests are run would be the scope of this issue. Unfortunately we lack other unit tests.

I haven't quite figured out what Pext is, but it definitely needs online banking.

I have written a custom module, that executes a script returns some JSON. I parse the JSON and display results. I can select a result entry to examine. Pext renders my result entry when I select it. However there is not a good way (in the UI [that I can see]) to return to my result set. (A back button perhaps?)

I could create a "mlocate" module or similar to demonstrate the awkwardness of this use case.

Also what is the best way to reset your query? E.g. to start over. The best I have found is "ESC". A reset button might be useful to visually indicate you can reset your query.

Ideally, I would think every time you hit the "enter" key, the app should reload query results. But this doesn't seem to be the case. Perhaps because the project is still maturing? Or perhaps the behavior is intentional that your response does not change until you type "ESC".

Could you provide some more information about the dependencies.

I get the following error message:

ImportError: No module named queue

cheers.

Otherwise, removing will go wrong due to a "PermissionError" caused by a file lock. If the git directory is deleted, the module even becomes an "unremovable system module". Bad stuff...

Currently, macOS support is a bit lacking. As described in the README, py2app builds are currently aliased because the standalone build does not work. We need a way to make a proper stand-alone .app that people can download and install as-is, without having to keep the downloaded files or so around.

The current issue for standalone builds is documented on StackOverflow, but nobody ever answered and no solution was found: https://stackoverflow.com/questions/45364693/py2app-ignoring-local-packages.

Bonus points for shipping all dependencies in the .app as well!

It is okay to switch away from py2app to something else if it works better, as long as it's freely licensed.

A lot of things have improved since 0.8, so it seems time for a new release again

• Ensure translations are up-to-date:
  • Dutch
  • Spanish
  • Traditional Chinese
• Make sure there are no blockers or serious regressions (did you notice anything? Please report quickly!)

Pext is a beast which has a WAY too big coupling to the Window class in the Python code. Preferably, the added unit test would come along with a decreased coupling that everything has the Window class, but any useful unit test would be great.

Is this a bug or a feature request?

Bug.

What Pext version are you running?

Pext v0.11.1-19-g4ca9d49 (according to pext --version)

What OS are you using? (e.g.: Ubuntu 16.04, Windows 10, macOS High Sierra)

Arch Linux, with KDE.

If this is a bug:

What did you do to run into this bug, step-by-step?

1. Start Pext's radiobrowser module
2. Choose 'By Most Tune-Ins'
3. Wait for the station list
4. Hover over one

What did you expect would happen?

The text in each of the three segments to be consistent.

What actually happened?

Is there anything else you would like to add?

This is a UI quibble, but it seems odd.

Theming support uses https://doc.qt.io/qt-5/qpalette.html.

The theme.conf file in a Pext theme uses the following structure:

[QPalette ColorGroup]
QPalette ColorRole = r,g,b

See https://github.com/Pext/pext_theme_eggplant/blob/master/theme.conf as an example.

Theme development still needs to be documented in the Pext documentation.

Also see #10.