Jump to content

Search the Community

Showing results for tags 'shared workflow settings'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Blogs

There are no results to display.

Categories

There are no results to display.

Calendars

There are no results to display.

Forums

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

Categories

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

Categories

  • New Features
  • Other

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Twitter


Location


Interests

Found 1 result

  1. 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...