Jump to content

Search the Community

Showing results for tags 'workflow data'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Alfred 3
  • Make the Most of Alfred
    • Discussion & Help
    • Bug Reports
    • Alfred Feature Suggestions
    • Themes
  • Alfred Workflows
    • Share your Workflows
    • Workflow Help & Questions
  • Alfred v2 Themes
  • Alfred Remote for iOS
    • Alfred Remote Discussion & Help
    • Remote Connection Troubleshooting

Categories

  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Twitter


Website URL


Jabber


Location


Interests

Found 2 results

  1. Short story, I backed up my Alfred workflows in my google drive, and now when I try to download them, they all come in form of zipped files. I've read here that you can convert the .alfredworkflow.zip file back into an .alfredworkflow file which I've managed to do but when I try to install the workflow, none of the workflows have their respective pictures saved (if I tried to do this manually for ~ 40 - 50 workflows, it would take ages). Any thoughts on how to easily fix this / automate this? I've tried writing a Python script but even using the subprocess module to run bash commands messes up the workflow when trying to zip the info.plist file. I'd greatly appreciate any thoughts on this and any ideas! Even after doing this and I try to install through info.alfredworkflow, it complains and gives a message "The workflow you are trying to import is invalid." I'm honestly not sure what to do at this point. import os import subprocess # SINGLE os.chdir("...") # change to directory that contains the .alfredworkflow.zip files for f in os.listdir(os.getcwd()): if len(f.split(".alfredworkflow.zip")) == 2: path = os.getcwd() + "/" + f subprocess.run(["unzip", path, "-d", os.getcwd() + "/" + f.split(".zip")[0]]) dirs = list(filter(os.path.isdir, os.listdir(os.getcwd()))) # ZIP for folder in dirs: if len(folder.split(".alfredworkflow")) == 2: path = os.getcwd() + "/" + folder + "/info.plist" subprocess.run(["zip", path + ".zip", path]) # RENAME for folder in dirs: if len(folder.split(".alfredworkflow")) == 2: path = os.getcwd() + "/" + folder + "/info.plist.zip" subprocess.run(["mv", path, os.getcwd() + "/" + folder + "/info.alfredworkflow"])
  2. OK so I have been working on a new version of Clinton's "Tabs" workflow and it has got me thinking. Currently I have a requirement to be able to configure persistent settings for that workflow and several other workflows including: My new version of Tabs (details of that to come later... working with Clinton on that) Asana Quicktask (Mannie Schumpert) AlfredTweet (are a few that just come to mind). Currently these store preferences in the appropriate folder under ~/Library/Application Support/... etc However I am increasingly seeing a need for enabling workflows to have data that can be synced between computers. It would be great to just have ~Dropbox/AlfredSync/Workflow Data/{Same structure as under ~/Library/...} then enable workflows to use this location using something like {syncedData}/bundle.id/ (i.e. as a variable similar to {query} in each of the script workflow steps. The alternate way is every workflow that wishes to enable such behaviour has to write a feature separately to manage this, manually changing the folder of only it's config but it seems like something that would be far more logical to have Alfred do (and far easier than having to write manual workflow steps to manage/update the configuration as I am currently seeing in my future. Many thanks LOOOOOVE Alfred.. IT RULES! Stu
×
×
  • Create New...