-
Notifications
You must be signed in to change notification settings - Fork 283
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
Update plugins for Apple Silicon #2634
Comments
A script I whipped up to download and compile in parallel is here: <
#2543 (comment)
Many of them build without issue on M1.
I'm still unclear on what to do *after* that -- even if no code changes are
necessary, I assume pushing a universal-binary compiled version somewhere
is still necessary.
Should be able to do some work on this tomorrow.
PS Updating the `Plug-in Development Reference` link from <
https://qsapp.com/wiki/Developer_Information> from <
http://projects.skurfer.com/QuicksilverPlug-inReference.mdown> (-> 301 to
https:// -> 502) to
https://github.com/quicksilver/PluginDevelopmentReference/blob/master/QuicksilverPlug-inReference.mdown
|
Nice, this is similar to my script below. The extra steps you're missing are:
I suggest we refine your/my script and add it to Tools in Quicksilver for folder in QSPlugins/*/; do
cd $folder
// bump version number
INFOPLIST_FILE=$(find . -name Info.plist -maxdepth 1)
/tmp/QS/Tools/bltrversion
git commit -a -m "Update version number for M1 build"
git push origin master
// build (taken from the default Xcode Github action: https://github.com/quicksilver/Quicksilver/new/master?filename=.github/workflows/objective-c-xcode.yml&workflow_template=objective-c-xcode)
scheme_list=$(xcodebuild -list -json | tr -d "\n")
scheme=$(echo $scheme_list | ruby -e "require 'json'; puts JSON.parse(STDIN.gets)['project']['targets'][0]")
echo Using default scheme: $scheme
filetype_parameter="project"
file_to_build="`ls -A | grep -i \\.xcodeproj\$`"
file_to_build=`echo $file_to_build | awk '{$1=$1;print}'`
SETTINGS=$(xcodebuild -configuration Release -scheme "$scheme" -project "$file_to_build" -showBuildSettings | sort -u)
xcodebuild clean build -quiet -configuration Release -scheme "$scheme" -"$filetype_parameter" "$file_to_build"
FULL_PRODUCT_NAME=$(echo ${SETTINGS} | grep "FULL_PRODUCT_NAME" | sed 's/[ ]*FULL_PRODUCT_NAME = //')
// do codesigning stuff
/path/to/qs-push-plugin -c “<ul><li>Updated for Apple M1 Silicon</li></ul>" "/tmp/QS/build/Release/$FULL_PRODUCT_NAME"
echo “Built and uploaded $FULL_PRODUCT_NAME successfully"
done |
Out of curiosity -- those aren't valid comments. Is this just an example of what your script looks like? What shell do you use? |
It looks like all of the EDIT: |
For a couple of them, the issue is that the |
Figuring out what some of these do is kind of rough.
Based on the last updated date, it looks like the latter is the one providing the "Calendar Plugin," but I don't see much in the info pane to clue me in. It might be helpful at some point to have a link to the source in the info pane. Seems like some should probably just be deprecated / archived?
|
This may be it: https://github.com/lloyd/yajl |
Yeah, maybe when we’re done building and releasing what can still be built, I’ll go through the database and just disable those with an update date before this year. |
I'm not getting anywhere fast, again running into this issue, which I never really figured out why it went away last time. Working on https://github.com/quicksilver/QSOmniFocusPlugIn-qsplugin -- can't get it to build,
$ fd 'qsobject\.h' /tmp/QS
/tmp/QS/build/Debug/QSCore.framework/Versions/A/Headers/QSObject.h
/tmp/QS/build/Debug/Quicksilver.app/Contents/Frameworks/QSCore.framework/Versions/A/Headers/QSObject.h
/tmp/QS/build/Release/QSCore.framework/Versions/A/Headers/QSObject.h
/tmp/QS/build/Release/Quicksilver.app/Contents/Frameworks/QSCore.framework/Versions/A/Headers/QSObject.h
/tmp/QS/build/Release/dmg/Quicksilver.app/Contents/Frameworks/QSCore.framework/Versions/A/Headers/QSObject.h I think I have Checkpoint on a couple scripts -- to download the plugin repos in parallel: #!/usr/bin/env python3
import asyncio
import json
from pathlib import Path
from urllib.request import urlopen
def scrape(outfile):
page = 1
repos = []
while True:
with urlopen(
"https://api.github.com/orgs/quicksilver/repos?per_page=100"
f"&page={page}"
) as req:
data = json.loads(req.read().decode())
repos.extend(data)
if (link := req.headers.get("link")) and "next" in link:
page += 1
else:
break
outfile.write_text(json.dumps(repos, indent=4))
return repos
async def clone(sem, repo):
async with sem:
await asyncio.subprocess.create_subprocess_exec(
"git",
*[
"clone",
"--recurse-submodules",
repo["ssh_url"],
Path("QSPlugins") / repo["name"],
],
)
async def clone_many(repos):
sem = asyncio.Semaphore(10)
coros = [
clone(sem, repo)
for repo in repos
if (url := repo.get("ssh_url")) and "qsplugin" in url.lower()
]
await asyncio.gather(*coros)
def main():
outfile = Path("repos.json")
if outfile.is_file():
repos = json.loads(outfile.read_text())
else:
repos = scrape(outfile)
asyncio.run(clone_many(repos))
if __name__ == "__main__":
main() and to build the plugin: #!/bin/bash
set -Eeuf -o pipefail
log() {
echo "$*" > /dev/stderr
}
err() {
log "error: $*"
exit 1
}
json() {
input=$1
target=$2
tr -d '\n' <<< "${input}" | ruby -e "require 'json'; puts JSON.parse(STDIN.gets)${target}"
}
main() {
local plugin_name
plugin_name=$1
# Workaround for no mapfile in bash 3, preserving compatibility with /bin/bash
target_plugin=()
while read -r -d '' target; do
target_plugin+=("${target}")
done < <(
find QSPlugins \
-maxdepth 1 \
-mindepth 1 \
-type d \
-iname "*${plugin_name}*" \
-print0
)
if [[ "${#target_plugin[@]}" -ne 1 ]]; then
err "possible matches for plugin ${plugin_name} ${target_plugin[*]}"
fi
plugindir="${target_plugin[0]}"
pushd "${plugindir}"
git stash
git pull origin master
git submodule update --init --recursive
INFOPLIST_FILE=$(find . ./Resources -maxdepth 1 -name Info.plist -print -quit)
if [[ -z "${INFOPLIST_FILE}" ]]; then
err "no plist"
fi
PYTHONPATH=/tmp/QS/Tools/python-support \
INFOPLIST_FILE=${INFOPLIST_FILE} \
QS_BACKWARDS_COMPATIBILITY_BREAK=4001 \
QS_BUNDLE_VERSION=4026 \
/tmp/QS/Tools/bltrversion
project=$(find . -maxdepth 1 -name '*.xcodeproj' -not -iname "*test.xcodeproj" -print -quit)
if [[ -z "${project}" ]]; then
scheme_list=$(xcodebuild -list -json || true)
else
scheme_list=$(xcodebuild -list -json -project "${project}")
fi
if [[ -z "${scheme_list}" ]]; then
err "unable to determine scheme list"
fi
# build (taken from the default Xcode Github action: https://github.com/quicksilver/Quicksilver/new/master?filename=.github/workflows/objective-c-xcode.yml&workflow_template=objective-c-xcode)
scheme=$(json "${scheme_list}" "['project']['targets'][0]")
log "Using default scheme: ${scheme}"
filetype_parameter="project"
# Absence of a project can still build, but will error if `-project` is specified
if [[ -z "${project}" ]]; then
SETTINGS=$(xcodebuild -configuration Release -scheme "${scheme}" -showBuildSettings -json)
xcodebuild build -quiet -configuration Release -scheme "${scheme}"
else
SETTINGS=$(xcodebuild -configuration Release -scheme "${scheme}" -project "${project}" -showBuildSettings -json)
xcodebuild build -quiet -configuration Release -scheme "${scheme}" -"${filetype_parameter}" "${project:-}"
fi
FULL_PRODUCT_NAME=$(json "${SETTINGS}" '[0]["buildSettings"]["FULL_PRODUCT_NAME"]')
log "Built ${FULL_PRODUCT_NAME} successfully"
while :; do
read -r -p "push changes? [y/n]: " response
case "${response}" in
Y | y) break ;;
*)
echo "bye"
exit 0
;;
esac
done
git commit --all --message="Update version number for M1 build"
git push origin master
log "Pushed ${FULL_PRODUCT_NAME} to master"
"${QS_REPO}/Quicksilver/Tools/qs-push-plugin" \
--changes "<ul><li>Updated for Apple M1 Silicon</li></ul>" \
--password "${QS_PLUGIN_PASS}" \
"/tmp/QS/build/Release/${FULL_PRODUCT_NAME}"
log "Pushed ${FULL_PRODUCT_NAME} to main QS repo"
}
main "$@" |
I vaguely remembered Rob writing about updating archaic plugins - here’s what he said: https://github.com/quicksilver/PluginDevelopmentReference/blob/master/QuicksilverPlug-inReference.mdown#plug-in-clean-up-and-modernization
What you’ve talked about seems similar to what we’ve seen in the past.
… On 16 Feb 2022, at 07:34, Nathan Henrie ***@***.***> wrote:
I'm not getting anywhere fast, again running into this issue <#2543 (comment)>, which I never really figured out why it went away last time.
Working on https://github.com/quicksilver/QSOmniFocusPlugIn-qsplugin <https://github.com/quicksilver/QSOmniFocusPlugIn-qsplugin> -- can't get it to build,
'QSCore/QSObject.h' file not found
$ fd 'qsobject\.h' /tmp/QS
/tmp/QS/build/Debug/QSCore.framework/Versions/A/Headers/QSObject.h
/tmp/QS/build/Debug/Quicksilver.app/Contents/Frameworks/QSCore.framework/Versions/A/Headers/QSObject.h
/tmp/QS/build/Release/QSCore.framework/Versions/A/Headers/QSObject.h
/tmp/QS/build/Release/Quicksilver.app/Contents/Frameworks/QSCore.framework/Versions/A/Headers/QSObject.h
/tmp/QS/build/Release/dmg/Quicksilver.app/Contents/Frameworks/QSCore.framework/Versions/A/Headers/QSObject.h
I think I have QSFrameworks (/Applications/Quicksilver.app/Contents/Frameworks) and QS_SOURCE_ROOT set correctly.
Checkpoint on a couple scripts -- to download the plugin repos in parallel:
#!/usr/bin/env python3
import asyncio
import json
from pathlib import Path
from urllib.request import urlopen
def scrape(outfile):
page = 1
repos = []
while True:
with urlopen(
"https://api.github.com/orgs/quicksilver/repos?per_page=100"
f"&page={page}"
) as req:
data = json.loads(req.read().decode())
repos.extend(data)
if (link := req.headers.get("link")) and "next" in link:
page += 1
else:
break
outfile.write_text(json.dumps(repos, indent=4))
return repos
async def clone(sem, repo):
async with sem:
await asyncio.subprocess.create_subprocess_exec(
"git",
*[
"clone",
"--recurse-submodules",
repo["ssh_url"],
Path("QSPlugins") / repo["name"],
],
)
async def clone_many(repos):
sem = asyncio.Semaphore(10)
coros = [
clone(sem, repo)
for repo in repos
if (url := repo.get("ssh_url")) and "qsplugin" in url.lower()
]
await asyncio.gather(*coros)
def main():
outfile = Path("repos.json")
if outfile.is_file():
repos = json.loads(outfile.read_text())
else:
repos = scrape(outfile)
asyncio.run(clone_many(repos))
if __name__ == "__main__":
main()
and to build the plugin (WIP):
#!/usr/bin/env bash
set -Eeuf -o pipefail
set -x
json() {
input=$1
target=$2
tr -d '\n' <<< "${input}" | ruby -e "require 'json'; puts JSON.parse(STDIN.gets)${target}"
}
main() {
while read -r plugindir; do
pushd "${plugindir}"
# bump version number
INFOPLIST_FILE=$(find . -maxdepth 1 -name Info.plist)
PYTHONPATH=/tmp/QS/Tools/python-support \
INFOPLIST_FILE=${INFOPLIST_FILE} \
QS_BACKWARDS_COMPATIBILITY_BREAK=4001 \
QS_BUNDLE_VERSION=4026 \
/tmp/QS/Tools/bltrversion
# git commit --all --message="Update version number for M1 build"
# git push origin master
# build (taken from the default Xcode Github action: https://github.com/quicksilver/Quicksilver/new/master?filename=.github/workflows/objective-c-xcode.yml&workflow_template=objective-c-xcode)
scheme_list=$(xcodebuild -list -json)
scheme=$(json "${scheme_list}" "['project']['targets'][0]")
echo "Using default scheme: ${scheme}"
filetype_parameter="project"
file_to_build=$(find . -maxdepth 1 -name '*.xcodeproj')
SETTINGS=$(xcodebuild -configuration Release -scheme "${scheme}" -project "${file_to_build}" -showBuildSettings -json)
xcodebuild clean build -quiet -configuration Release -scheme "${scheme}" -"${filetype_parameter}" "${file_to_build}" || {
popd
echo "${plugindir}" >> fail.log
continue
}
FULL_PRODUCT_NAME=$(json "${SETTINGS}" '.[0]["buildSettings"]["FULL_PRODUCT_NAME"]')
# do codesigning stuff
/path/to/qs-push-plugin -c "<ul><li>Updated for Apple M1 Silicon</li></ul>" "/tmp/QS/build/Release/${FULL_PRODUCT_NAME}"
echo "Built and uploaded ${FULL_PRODUCT_NAME} successfully"
popd
echo "${plugindir}" >> success.log
done < <(find QSPlugins -maxdepth 1 -mindepth 1 -type d)
}
main "$@"
—
Reply to this email directly, view it on GitHub <#2634 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABEXH7DDS5H4L4UUK4HLHLU3LPJJANCNFSM5OILQHFQ>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.
|
Very helpful, thanks for the reminder. I know I've read through it before, but reviewing it helped resolve the first few errors. (Hopefully some of these keywords will be easy issue search terms for other contributors / new devs.) |
OK, I think I figured out my issue -- at least in part -- and why it seemed to suddenly fix itself last time as well. I cloned the recently updated I knew the plugin build depends on the quicksilver build, which creates What I discovered, is that when I (out of habit) run the clean action (cmdshiftk) from the Plugin, I can no longer successfully build the plugin. I have to return to the Xcode window building Does this sound right? I didn't expect a |
Hmmm. That doesn’t sound right. I feel like I used to do that all the time, but it’s been a while. |
I noticed this a few days back. I just had to re-build the QS project and it was all fine. I also just experienced the Scheme switch from “Quicksilver Distribution” to “Quicksilver”. Xcode seems really quirky.
… On 16 Feb 2022, at 21:46, Rob McBroom ***@***.***> wrote:
Does this sound right? I didn't expect a clean run from the plugin project to be removing necessary build artifacts from the Quicksilver build.
Hmmm. That doesn’t sound right. I feel like I used to do that all the time, but it’s been a while.
—
Reply to this email directly, view it on GitHub <#2634 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABEXH6G2KAVXML322D7PALU3OTFHANCNFSM5OILQHFQ>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.
|
With the script above, these seem to succeed without further effort (I imagine most already done by @skurfer -- should have filtered by last push date):
Failing:
EDIT: remove |
Here's a ranking of top 45 plugins by all-time downloads. Looks like most are already re-build and released. Let's make sure the these are re-built before we announce 2.0.0. iTunes is number one - we should update that to work with Music I guess.
|
I've updated the original post to split those we're yet to build, but need to build for 2.0 |
Using
Looks like these have not been updated but can probably just get scripted:
As a test run, I built EDIT: To be more explcity -- @skurfer, do I need a password to use |
@n8henrie - Yes, you need a password for I've updated the 1st post to mark my name next to plugins I will test and update. We have two options here: just blindly update a plugin to work on Apple Silicon, or test functionality and fix any broken plugins. I vote for the latter. So e.g. for the |
The iTunes plug-in won’t work at all. See #2495 I think all we need to do is
The catch is that I think the app has to be properly signed in order to be allowed access to |
I see where it says that, but it seems to run without any extra effort in swift. (I imagine it might also in objc, I just can't whip up a test case.) // swift-tools-version:5.5.0
import iTunesLibrary
let library = try ITLibrary(apiVersion: "1.1")
let playlists = library.allPlaylists
for playlist in playlists {
for item in playlist.items {
print("\(item.title) by \(item.artist?.name ?? "<blank>") from playlist \(playlist.name)")
}
} $ swiftc itunes.swift
$ ./itunes | tail
I Get It by Chevelle from playlist Workout
Judith by A Perfect Circle from playlist Workout
Set Me On Fire (Original) by Killaflaw from playlist Workout
This Is The New Shit by Marilyn Manson from playlist Workout
Like A G6 by Far East Movement from playlist Workout
Forgot About Dre by Dr. Dre from playlist Workout
Blue Monday by Orgy from playlist Workout
The Hand That Feeds by Nine Inch Nails from playlist Workout
Burn It Down by Linkin Park from playlist Workout
Party Rock Anthem by Lmfao from playlist Workout |
The updated 1.7.0 that I got together with other updates today gets installed but isn't working with QS 1.6.1 on OS 10.12.6: Not reacting to cmd-L, pref-pane empty. (I am not using other plug-ins much, but likewise installed new Contacts-plugin seems to be working.) If you (understandably enough) don't want to support 10.12 any more there should be a block for the updates or a warning. Also a link to the earlier versions of the plugins from https://qsapp.com/plugins.php would be good to have. |
Clipboard history?
Can you send a screenshot? I'm confused about 1.7.0 vs 1.6.1 -- which are you using? |
yes! (edited the name out again, sorry)
https://www.dropbox.com/s/kwohurxupg86q47/Screen%20Shot%202022-02-18%20at%2016.14.25.png?dl=0
QS 1.6.1, the plug-in states its version as 1.7.0 https://www.dropbox.com/s/g9cc9k4axqasjyg/Screen%20Shot%202022-02-18%20at%2016.15.10.png?dl=0 Plugin version 1.5.0 from my backup still working nicely. |
Ok, so this is specifically the clipboard plugin? If you can confirm I think we should make a separate issue. Mine is showing version clipboard plugin version 1.6.2 -- can you refresh and see if that is available? |
yes, as far as I can see the other updated plugins work, but, as I said, I hardly use most of them apart from Contacts and Clipboard. The Dictionary plugin comes up when evoked, but doesn't seem to send the word to the dictionary app though. But I wouldn't know if it did earlier as I didn't use it.
After reverting to 1.5.0 the update dialog offers only 1.7.0: https://www.dropbox.com/s/cpr2z5zuy5l0pqo/Screen%20Shot%202022-02-18%20at%2017.51.37.png?dl=0 |
Thanks for the report @floriandk - v1.7.0 of the clipboard plugin was just released for Apple Silicon. If you're on 10.12, then you should stick with the previous version. I have updated our system to not offer you the v1.7.0 version now. Stick to the 1.5.0 version of the plugin, and you should be all good! Thanks |
Edit: I already upgraded and pushed the websearch plugin as I made that guide. |
Back in town, but will be a busy week at work. I incorporated @pjrobertson's
Unfortunately, I'm getting a warning with double-click to install: Have you guys been seeing this? |
Got Twitter building on GA (had to add a new secret for I get the same warning as in the post above, and it's a bit of a pain with right clicking -> open, relaunch, it repeats this a few times, I eventually get the "do you really want to open" dialog. I wasn't getting this before, wonder if it's because I updated to MacOS 12.3 last night? 🤦♂️ But it works! After installing the GA build: https://twitter.com/n8henrie/status/1505235750110986243?s=20&t=9Hpm9yq4Zgv_QReKZUjg0A EDIT: I pushed the new plugin, it should be live. |
Tweaked the signing action a bit to give the artifact for the signed plugin* a pretty name (so one's
Any concerns with these? * Only pretty-naming the signed plugin artifact for now because there is a little more "doing" involved with the unsigned artifact, since the signing step depends on the unsigned artifact, and the signed version doesn't have access to the plugin name at the point of downloading the artifact -- rather than dealing with a dynamically named dependency, it seems a lot easier to just leave this as |
@pjrobertson -- Just curious, is $ ls -d ~/Library/Application\ Support/Quicksilver/Plugins/*Calc*
/Users/n8henrie/Library/Application Support/Quicksilver/Plugin/com.blacktree.quicksilver.TSCalculatorPlugin.23A.qsplugin In the plugin repo: $ git grep TSCalculator
CalculatorPlugin.xcodeproj/project.pbxproj: PRODUCT_BUNDLE_IDENTIFIER = com.blacktree.quicksilver.TSCalculatorPlugin;
CalculatorPlugin.xcodeproj/project.pbxproj: PRODUCT_BUNDLE_IDENTIFIER = com.blacktree.quicksilver.TSCalculatorPlugin;
Info.plist: <string>com.blacktree.quicksilver.TSCalculatorPlugin</string>
$ git log -G TSCalculator
commit abe5c598e52c951afc27437c36304a8c67a5c8db
Author: Patrick Robertson <robertson.patrick@gmail.com>
Date: Fri May 6 10:16:03 2016 +0800
Upgrade project (Xcode defaults)
commit 9ff5bbbc048999eb1f74cd70c09ab2018388eeb1
Author: Etienne Samson <tiennou7@gmail.com>
Date: Mon Feb 11 23:09:11 2013 +0100
Documentation + s/Module/Plugin/ + remove unused files.
commit 1ba53debc6c1bb743e8656798a90f57f79caab61
Author: Patrick Robertson <robertson.patrick@gmail.com>
Date: Sun Jul 10 19:05:48 2011 +0100
initial commit |
Regarding #2634 (comment), here's what I'm seeing when I try to install the codesigned plugin, after clicking "Relaunch":
|
Reviewing https://support.blackfire.io/en/articles/3669492-issues-with-macos-catalina: $ xattr Calculator\ Plugin.qsplugin/
com.apple.macl
com.apple.quarantine
$ xattr -cr Calculator\ Plugin.qsplugin/
$ xattr Calculator\ Plugin.qsplugin/ It then installs without this problem. I'll add to the GA for Calculator and retest. |
$ xattr Calculator\ Plugin.qsplugin
com.apple.macl
com.apple.quarantine Just removing the quarantine flag seems to be sufficient: $ xattr -d com.apple.quarantine Calculator\ Plugin.qsplugin Oddly, it seems like it installed from the QS interface just fine, even though it still has quarantine flags:
¯\_(ツ)_/¯ So for the moment it seems that separately downloading and double-click-to-installing is a minor problem. So I guess this might end up being a documentation issue -- people manually downloading and installing will likely face this issue. Hopefully people installing via QS will not have trouble. |
I think documenting this on https://qsapp.com/plugins.php is sufficient. I don’t know if anyone ever installs that way these days, unless there are unofficial plug-ins out there somewhere. |
No idea how that happened, I think it could be a typo, 6 years ago so... :P My guess (just a guess) is that the calculator plugin can't be signed because it's using a private framework, something that's probably not allowed. I can't find anything to support my guess though. I also can't find a decent alternative for the |
Great! I've marked it off in the 1st post. Just MiniInterface and 1Password left now. |
Has the Flashlight plugin been updated? It doesn't work for me (except under Rosetta). Thanks |
It hasn't been updated yet, but I'll work on a new build and get it out in the next 1-2 days. Thanks |
Terrific, thanks very much
…On Sat, Apr 16, 2022 at 9:24 PM Patrick Robertson ***@***.***> wrote:
It hasn't been updated yet, but I'll work on a new build and get it out in
the next 1-2 days.
Thanks
—
Reply to this email directly, view it on GitHub
<#2634 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGIMGTDVCL3SD3BSILXNIDVFNR37ANCNFSM5OILQHFQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi @jbaraban, Please update to the latest version of the Flashlight plugin from within Quicksilver, it's now been updated to work with Apple Silicon :) |
Thanks - I updated and it works natively. Any chance of reverting to the
upper left hand corner placement (or allowing the choice between that and
the center)? Thanks very much!!
…On Mon, Apr 18, 2022 at 7:20 PM Patrick Robertson ***@***.***> wrote:
Hi @jbaraban <https://github.com/jbaraban>,
Please update to the latest version of the Flashlight plugin from within
Quicksilver, it's now been updated to work with Apple Silicon :)
—
Reply to this email directly, view it on GitHub
<#2634 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGIMGXVNUQCQK3PNOHUICTVFXU3HANCNFSM5OILQHFQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Done, and thanks for your support! |
Perfect, thanks so much!
…On Fri, Apr 22, 2022 at 10:52 PM Patrick Robertson ***@***.***> wrote:
Any chance of reverting to the upper left hand corner placement
Done, and thanks for your support!
—
Reply to this email directly, view it on GitHub
<#2634 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGIMGVW6SJGOZRR4IXAAY3VGNQVZANCNFSM5OILQHFQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
the calculator plugin can't be signed because it's using a private
framework
I see the same issue with the Twitter plugin. Like I mentioned, removing
the xattrs resolves the issue, so it may just be because it's downloaded.
I could probably include a little help file into the artifact that tells
people the workaround ("show in finder" -> right click -> open).
|
By the way, the last Calculator plugin update (2.3.5) caused a problem with
the Flashlight interface - you can't see the formula you're typing in
anymore (see picture below). If that can be fixed, I would really
appreciate it. Thanks!
[image: image.png]
…On Tue, Oct 11, 2022 at 11:01 AM Nathan Henrie ***@***.***> wrote:
> the calculator plugin can't be signed because it's using a private
framework
I see the same issue with the Twitter plugin. Like I mentioned, removing
the xattrs resolves the issue, so it may just be because it's downloaded.
I could probably include a little help file into the artifact that tells
people the workaround ("show in finder" -> right click -> open).
—
Reply to this email directly, view it on GitHub
<#2634 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGIMGXH4VTFUYIJDXO3Q4DWCUNGLANCNFSM5OILQHFQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Are you sure it was an update to the calculator plugin that caused it? Looks like Flashlight was updated about the same time: https://github.com/quicksilver/Flashlight-qsplugin |
I've just reset both the flashlight and calculator plugins to a commit from ~6 months ago (the most recent commit after a long hiatus in both cases), and unfortunately I see the same behavior. |
I was sure it was the calculator plugin update, since I installed the
Flashlight plugin update first and the problem didn't start then, but
rather only when I installed the calculator plugin update. Please let me
know if there's anything I can do to help diagnose the issue. Maybe there
was a QS update involved as well? Thanks
…On Wed, Nov 9, 2022 at 11:59 PM Nathan Henrie ***@***.***> wrote:
I've just reset both the flashlight and calculator plugins to a commit
from ~6 months ago (the most recent commit after a *long* hiatus in both
cases), and unfortunately I see the same behavior.
—
Reply to this email directly, view it on GitHub
<#2634 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGIMGQY2AHVYKXJH52VIEDWHQNDVANCNFSM5OILQHFQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@jbaraban -- would you mind creating a separate issue for the flashlight / calculator issue? |
Sure, done:
[Bug]: Calculator plugin input text obscured in the Flashlight interface
#2936
…On Wed, Dec 14, 2022 at 9:33 AM Nathan Henrie ***@***.***> wrote:
@jbaraban <https://github.com/jbaraban> -- would you mind creating a
separate issue for the flashlight / calculator issue?
—
Reply to this email directly, view it on GitHub
<#2634 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGIMGWPGO65PFKUBUP4C7TWNFZ35ANCNFSM5OILQHFQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Here's a list of all plugins in the Quicksilver Organisation on Github. Let's tick them off one by one as they get updated for Apple Silicon. I think all those with a last commit of 5th Feb have already been done by @skurfer
Outstanding for 2.0:
2.1.0 and up:
GrowlNotifier-qsplugin (last commit: 2012-01-22) DiscontinuedApple Mail (last commit: 2014-09-09) Broken: see Apple Mail Plugin not available or doesn't work #2648QSOmniFocusPlugIn-qsplugin (last commit: 2011-07-26)Builds and installs, can list projects, but the plugin doesn't actually do anything AFAICT, needs updating for OF3. Will work on this eventually -n8henrieCode used to compile the list:
The text was updated successfully, but these errors were encountered: