-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ulauncher v6 #869
Comments
Blacklisted dirs ('If you still feel like you need this setting in Ulauncher v6, let us know'). I think I do need this. For, there are directories that contain executables (or links to them) that do not work on my system or that I do not wish to use. Also: could we have dark mode in the configuration windows, please? |
Then why do you have them in the dedicated directory for desktop entries to use for launchers and menu apps if I may ask?
That's not planned, and is not easy to implement, so very unlikely for v6. Hopefully later at some point. |
This comment was marked as outdated.
This comment was marked as outdated.
I just pushed a pre-release: https://github.com/Ulauncher/Ulauncher/releases/tag/v6.0.0-beta1. We still have work to do before the stable release, but this makes it easier for people to test without building themselves. The plan was to also make that publish to ulauncher-dev, for the Ubuntu/Debian users who opted for the experimental Ubuntu PPA. But apparently that part Either way the deb can be downloaded and installed manually in the meanwhile. |
https://github.com/Ulauncher/Ulauncher/releases/tag/v6.0.0-beta2 released and published to ulauncher-dev |
Working nicely in a Xubuntu VM, but I'm hoping someone will start making some RPMs soon. My main systems are Fedora and Tumbleweed. The Love the Ctrl+comma shortcut to open the preferences now. And the searching in the app "comment" or description appears to be working well also. Lots of good things happening. |
Version 6 sounds good! Where should bug reports for the beta of that version be posted, please? I add immediately here though the following two points (though neither are about bugs).
|
Yeah, that's because the old way relied on a library that relied on globally monitoring all keystrokes See #1256 and #991 (comment) (old behavior). I added support for Cinnamon too, but had to revert it because it wasn't possible to reload Cinnamon to apply the settings: 2a22711
🙏 |
v6.0.0-beta3 was released yesterday, but the ulauncher-dev ppa upload failed because of errors on their side. So the package wasn't pushed until some hours ago today. |
v6.0.0-beta4 was just released with a few fixes. The scope of the v6 release still isn't fully set in stone, but we only have a few remaining planned features/improvements now:
Most of the other unfinished tasks in the milestone are chores that relate to the release, extension site or documentation (these can still take time though). We would appreciate any help we can get with testing (trying to confirm the current behavior and narrow down where/why any issue happen). For example:
|
I see this as well on Fedora. From my understanding it seems that Ulauncher is regarded as as parent process. There must be a way to dislodge the Child from the Parent. In the shell I would use |
Actually from what I understand For Python, GPT-4 suggests this may be the best way to launch a process and have it be independent of the Python process that launches it: import subprocess
subprocess.Popen(['your_app'], start_new_session=True) I've never had occasion to use this
References to it found here: |
We have just released v6.0.0-beta5 which should fix the issue mentioned above (it also reintroduced #778 when running Ulauncher from a terminal) @euh2 @RedBearAK This is the first release for a while because most of what's been done in this period has been refactoring and build improvements, NixOS support and other things which didn't affect the app so much.
|
Suse might be an alternative: openSuse I'm curious about why I was tagged here. 🤔 |
Because this release should address your feedback in #869 (comment)
Feels like a better alternative for sure, but extremely high threshold to learn how to use it. I tried it twice. |
I forgot about that. Waiting eagerly for the stable v6. 🇺🇦 |
I continue to look forward to someone putting together an RPM installer. I spend most of my time on Fedora. I'm betting between openSUSE, OpenMandriva, Fedora, CentOS, RHEL and all the RHEL compatibles, the RPM-based distros are a decently large portion of the installed Linux user base. I tried just using the It also seems to be putting things in the "system" Python locations, which more and more distros are restricting in favor of wanting apps to use their own virtual environment to protect the system Python library. Seems like a good idea to sort that out before the final release. I had to go through that process with a project of mine about a year ago, and now it will install without any Python issues on about 6 different major distro types, using its own isolated |
@RedBearAK Thanks for the testing and the feedback. These are not priorities for us currently though. Also, system packages should use system dependencies unless it's a flatpak or something. I guess we could look into supporting https://help.ubuntu.com/community/CheckInstall though, but those uses the user package paths, not the system ones. |
Since the last updates here (beta4-5) we have done a lot of refactoring, fixes and added some features, but mainly the same bigger tasks remain. We have been trying to reduce the milestone by moving #1257 out of the V6 release so we can have a release candidate ready sooner.
The other unfinished tasks in the milestone are chores that relate to the release, extension site or documentation. We would still appreciate any help we can get with testing to ensure things are working in different environments. In particular if you can make detailed reports with error logs and/or submit PRs. |
This is a tracking issue for the upcoming v6 release that we have been working hard on. Subscribe to this issue to be notified of the v6 development, as we are closing issues as they get fixed for the v6 branch (now the main branch).
What has been done
git diff --shortstat
as of writing this says545 files changed, 11479 insertions(+), 29372 deletions(-)
To test Ulauncher v6, follow the instructions to set up and run.
To see what else is planned, see the: milestone (note that the milestone is subject to change, incomplete and doesn't include smaller things like updating our documentation, website and extension website).
Ulauncher application changes
--hide-window
CLI option is now renamed to--daemon
.--hide-window
is now an invalid option that will cause Ulauncher not to start. This is so that old XDG autostart files won't be conflicting with the new implementation (6f39063).ulauncher-toggle
is just a wrapper aroundgapplication launch io.ulauncher.Ulauncher
(Switch to Gtk.Application and makeulauncher
command "toggle" by default #988, feat: dbus activatable #1164, d90b89f and many more)ulauncher-toggle
command to always activate the window, rather then actually toggling it.%s
to access the argument, which means if you use%s
in your shell scripts code and don't want this you have to change to something else (like using f-strings in python) (Argument to shell commands get %s instead of the real argument #389)Ulauncher
can now take an optional argument to set the Ulauncher querygapplication action io.ulauncher.Ulauncher set-query "'hello'"
Theme changes
css_file_gtk
to target GTK 3.20+, rather than needing bothcss_file_gtk
andcss_file_gtk_3.20+
(old themes specifying both ways will remain to work the same way) (Simplify CSS themes by removing GTK 3.20 support #836).Extension changes
Most extensions that runs in Ulauncher v5 now should run in Ulauncher v6 as well. Almost all changes we made are backwards compatible. The exceptions are if the extension used APIs that were not meant for extensions to use.
apiv3
orapiv3.1
etc Completely remove versions.json support #1091Result
getter methodsget_name()
,get_keyword()
,get_icon()
. Just use the propertiesname
,keyword
,icon
directly if you need to access properties from the result (38e8792).Result
class now no longer support positional parameters (note that this feature was never documented to begin with, and I have found no extensions that used this).api.server.*
andapi.shared.action.LaunchAppAction
)self.preferences
). Previously they were loaded into the same property and format, but after the extension was initialized via thePreferencesEvent
. The PreferencesEvent still exists for backward compatibility, but we recommend to simply use the class__init__
now (see Load extension preferences directly in __init__ #1047)type
"keyword" in the manifest. But this was both confusing and a limiting factor for them. Implement triggers #1097on_input
that replacesKeywordQueryEvent
does not inherit the API suggestion: add event.get_keyword_id() #284 issue, and does not use any custom Ulauncher data type for the argument. Just "input text" and "keyword id" (both strings). For old extensions in Ulauncher v6 this issue has been solved in a different way: Rework extension keyword #1056ExtensionResultItem
andExtensionSmallResultItem
to justResult
(set the a propertycompact
toTrue
to use the smaller template. Merge Result classes (Result, SearchableResult, SmallResult, ExtensionResult, ExtensionSmallResult) #1118 Merge Result classes (and glade ui files) #1120ulauncher.api
(Rename *ResultItem to just *Result #934, 741ebae)text
type to show as a textarea (f8bc100)checkbox
andnumber
(d675036, 39811bb)required_api_version
is nowapi_version
(again)developer_name
is nowauthors
preferences
is now a dictionary Change manifest.preferences to a dictionary #1085 and optional as triggers (aka "type": "keyword") has been moved out to their own separate placetriggers
Implement triggers #1097query_debounce
is now specified directly in the manifest root asinput_debounce
because we no longer use the terminology "query" for the extension input triggersDoNothingAction
-->True
HideWindowAction()
-->False
SetUserQueryAction("string")
-->"string"
The text was updated successfully, but these errors were encountered: