FSNotes

[gingerbeardman]

Quote

 

This Alfred workflow offers the following functions:

 

• fsf Open... (choose from list of files in FSNotes default storage folder, required)
• fsi Import... (matches filename or phrase, required)
• fss Search... (matches filename or phrase, required)
• fsc Create from Clipboard... (specify title, optional)
• fsn Create... (specify title, optional)

 

To choose from a list of all functions use the fs keyword.

 

 

• Author: I'm the author of this workflow
• Alfred Forum: https://www.alfredforum.com/topic/12934-fsnotes-alternative-to-nvalt-workflow/
• Main page: https://github.com/glushchenko/fsnotes/wiki/Alfred-Workflow
• Dependencies: none

 

Screenshot:

 

• it would be much nicer if all screenshots were taken using the default Alfred theme?
• They're going to be a real mishmash of themes as it is. The below screenshot uses a custom theme.

 

Edited December 30, 2022 by gingerbeardman
screenshot

[vitor]

1 hour ago, gingerbeardman said:

it would be much nicer if all screenshots were taken using the default Alfred theme?

Disagreed. Different people like different themes and will use different workflows. It’s positive to highlight you’re not limited to one look.

 

Plus, some workflows are fun to present with certain themes. E.g. Microphone Control and Ignore in Alfred.

 

2 hours ago, gingerbeardman said:

They're going to be a real mishmash of themes as it is.

Each Gallery page shows one workflow at a time, and within that, the theme is consistent. I don’t think people are going to be confused by that.

[gingerbeardman]

I knew you would disagree. 

 

🤷‍♂️

[iandol]

@vitor — I was curious as to how workflows auto-update? At least with your updater it utilised the ability to track github releases, but that doesn't seem to be a requirement for hosted workflows anymore?

[vitor]

@gingerbeardman It’s a friendly disagreement, though! I’m interested in knowing why you disagree if you have a specific usability concern. If it’s just an aesthetic preference, I think we can agree everyone will have their own. One important consideration is that if every page used the same theme and you didn’t like the choice, then you’d feel stuck with it. At least this way there’s something for everyone.

 

@iandol GitHub itself provides feeds. Go to a releases page and append .atom to the URL. That’s not the only way, but it is common. When a change is detected, the update is reviewed and updated in the Gallery.

[iandol]

OK, so in this case IINM the workflow is not contained in a release, but is an attachment: https://github.com/glushchenko/fsnotes/files/10324668/FSNotes-AlfredWorkflow-22.zip — i.e. there is no release page or atom feed that can be used?

[vitor]

Indeed. Even if the workflow was just a file in the repo one could still get a feed for it.

In this case (beeing a wiki page) it’s not really feasible, especially because the URL changes with each update. Either the distribution method changes or we’ll need to get a ping by someone whenever there’s a new version. Doesn’t seem like it gets a ton of updates and it’s now a codeless workflow which calls their URL handler, so doesn’t look like an issue.

Another option would be to have the changelog as a separate hosted file. Basically anything which only changes with new releases is a good candidate.

[iandol]

Yes, the workflow itself is unlikely to change much at all, so perhaps a manual solution would be enough. But I think @gingerbeardman could add this as a public github repo, and this may make things a bit easier down the line?

[vitor]

So the author of the FSNotes app is glushchenko, but @gingerbeardman builds and maintains the workflow, and @iandol recently submitted updates to it? Nice collaboration!

 

An individual repo might make sense in that regard. If gingerbeardman hadn’t mentioned being the author, with that page I’d have assumed glushchenko. But it’s up to gingerbeardman to change the method or keep as is, the choice won’t affect inclusion (I’ll prepare it shortly).

 

But do please let us know of eventual new releases or if you ever switch to another release method which can be auto-checked.

[gingerbeardman]

I'll sort out a repo for it soon, no worries. 

 

Probably best to include it as it is for now if it's easy to transition to a Repo. 

Edited January 3 by gingerbeardman

[vitor]

2 hours ago, gingerbeardman said:

if it's easy to transition to a Repo.

 

It is, no worries. Jus give me a ping when it happens and I’ll make the change. But adding soon with the current page.

[vitor]

This is pretty much ready to go in, but I’ve noticed something: fsf says it searches the FSNotes default folder and its scope is set to ~/Library/Mobile Documents/iCloud~co~fluder~fsnotes/Documents. However, when downloaded from GitHub FSNotes defaults to ~/Library/Containers/co.fluder.FSNotes/Data/Documents. Is the former the default for the version available in the Mac App Store? Shouldn’t both be included in the scope?

 

Also, what’s the way for one to send a pull request or suggestion? There is an fsc keyword to add a note with the current clipboard contents, but a Universal Action would make it considerably more versatile (adding a note from selected text or any clipboard entry, not just the most recent). Ditto for the import (fsi), in which a Universal Action or File Action (to limit the matching file types) would allow users to add from what they have selected in the Finder or Alfred’s navigation.

 

Edited January 13 by vitor

[gingerbeardman]

I'll make a priority of setting up a repo. We can then address all this. 

[gingerbeardman]

OK!

 

https://github.com/gingerbeardman/fsnotes-alfred-workflow

 

Regarding Scope, the path is `~/Library/Mobile Documents/iCloud~co~fluder~fsnotes/Documents` on my Mac.

 

At `~/Library/Containers/co.fluder.FSNotes/Data/Documents` I do see some example documents but they are not my files.

 

So, I'll ask at FSNotes.

 

 

Edited January 18 by gingerbeardman

[gingerbeardman]

Quote

 

Default path for Mac App Store version is iCloud Drive ~/Library/Mobile Documents/iCloud~co~fluder~fsnotes/Documents

 

Default path for notarised version (from GitHub and brew) is ~Library/Containers/co.fluder.FSNotes/Data/Documents

 

 

So, I have issued a new version of the Workflow to include both in scope.

[vitor]

Pull request submitted.

[gingerbeardman]

Thanks for the PR!

 

Merged and new release issued.

[vitor]

Live in the Gallery!

 

Edited January 20 by vitor

[gingerbeardman]

Ace! Thanks.

 

Gallery will be a real benefit to users.

[iandol]

Thank you @gingerbeardman for the repo and @vitor for the nice updates!!! 😍

Edited January 21 by iandol

[gingerbeardman]

You know, I don't think I knew about custom Universal Actions until now. I only use the built-in ones. 

Edited January 21 by gingerbeardman

[gingerbeardman]

v2.5

• Added: weekly journal triggers `fsj` keyword and `Cmd+Alt+J` hotkey

 

Cheers

Edited January 25 by gingerbeardman

[vitor]

2 hours ago, gingerbeardman said:

v2.5

 

Will be live in the Gallery soon.

 

2 hours ago, gingerbeardman said:

and `Cmd+Alt+J` hotkey

 

Note hotkeys are always stripped on import, to avoid conflicts. That is to say it’s fine to suggest a hotkey, but users won’t have that one by default.

[gingerbeardman]

I updated to gallery 2.5 and my keyboard shortcut stayed. So is it only on the initial import?

 

In that they need to map their own hotkey, or add the entire hotkey node back into the workflow?

 

 

thanks

Edited January 26 by gingerbeardman

[vitor]

9 minutes ago, gingerbeardman said:

So is it only on the initial import?

Yes. The customisations already in place remain, unless you untick the migration box on the bottom left.

 

10 minutes ago, gingerbeardman said:

In that they need to map their own hotkey

Yes, just that.