Jump to content

cleobis

Member
  • Posts

    11
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by cleobis

  1. @JohnG, does this work for you? https://github.com/cleobis/alfred-cal/releases/tag/v1.6.1
  2. The fix is straightforward. Someone already suggested the fix shown at https://github.com/cleobis/alfred-cal/commit/ac32c70d6a0289ea3a5deb4a8212536f77808653. I will try to push out a release on the weekend. If you are impatient, the file that needs updating is osascript/open_fantastical.scpt.
  3. @iApple, the auto update functionality is provided by a helper library. The library has a number of hidden settings described at https://www.deanishe.net/alfred-workflow/guide/magic-arguments.html. Entering “cal workflow:noautoupdate“ should do it.
  4. @ravage123, Can you please provide more information on the failure? In what way does it not work? Open the workflow in Alfred preferences. Click the bug symbol in the top right corner to display the workflow debug messages. Run the workflow. Copy the debug messages and post them to the forum.
  5. I think I have it working now. The delay was due to the difficulty of either bundling the pyobjc dependency or requiring users to install it. In the end, I avoided the problem by porting the affected code to AppleScript. An updated version is available at the link below. I will remove pre-release marking once I hear that it is working from a few users. https://github.com/cleobis/alfred-cal/releases/tag/v1.6.0
  6. @vitor likely yes but it will be a while. I haven’t yet updated to macOS 12.3 so I am not yet running into the issue of python 2 being removed. Once I gupgrade, I will likely fix the plug-in. It will be a while as I don’t have much time to spend on the side project. The plug-in depends on the workflow library which I don’t think has been updated to python 3. For the system calls, they can be moved into an executable. I need to think about if the python runtime should be bundled with the plug-in or require users to install python 3.
  7. The formatting should be working now: https://github.com/cleobis/alfred-cal. Thanks to @deanishe for his tips.
  8. There is an old plugin (https://github.com/cleobis/alfred-cal) that I am attempting to rehabilitate. It used the clever trick of printing the perfect number of spaces in the results to create the illusion of a multi-column grid layout. To get the spacing right you need the font and font size for the active theme. The plugin parses the preference plist for older versions of Alfred to obtain this information. This no longer works in the current version of Alfred. I see that the theme id is available from the alfred_theme environment variable (https://www.alfredapp.com/help/workflows/script-environment-variables/). If the theme is "theme.custom.<id>", I then parse the corresponding file in $alfred_preferences/themes/theme.custom.<id>/theme.json. If the theme is "theme.bundled.*", I then need to parse the corresponding file in "Alfred 4.app/Contents/Frameworks/Alfred Framework.framework/Versions/Resources/*.alfredappearence". Two questions: i) Is there a portable way to find the location of Alfred 4.app? The best option I found is to call URLForApplicationWithBundleIdentifier() (https://developer.apple.com/documentation/appkit/nsworkspace/1534053-urlforapplicationwithbundleident) via the Python Objective-C bridge. ii) Is there a method to convert between between e.g. "theme.bundles.default" and the filename e.g. "Alfred 4.app/Contents/Frameworks/Alfred Framework.framework/Versions/Resources/Alfred.alfredappearence"? In the absence of information, it looks straightforward to reverse engineer the current options.
  9. I believe I have resolved the crash. Formatting is a bit wonky and still needs to be fixed. https://github.com/cleobis/alfred-cal
×
×
  • Create New...