Since these scripts are cross-platform, you could put the Plug-In inside your OmniOutliner iCloud folder, perhaps. However, you could use any folder you like.
Hitting the green Code button, and then Download ZIP should do it. After decompressing the .zip file, you’ll find the file. That Plug-In should go inside one of your linked folders.
Several options, there.
Clicking on the Automation menu, and then the desired Plug-In.
1 - I don’t have an iCloud folder; so I created ‘Omni Automation’ in ~/Library/Application Support.
2 - I put everything in that folder; although it didn’t actually include a specific file, .omnioutlinerjs in that zip - even accounting for the fact that it begins with ‘.’… I used the command line. Am I missing something, please?
I can now see how to run an Automation; and yours to reveal the parent directory of the selected item works perfectly, and is much appreciated!
Just to clarify, in this partícular case, the file had .omnijs extension. It can target any Omni application. Files with .omnioutlinerjs extension are restricted to OmniOutliner.
That’s strange. An OmniFocus iCloud folder is automatically created in the installation of OmniFocus, I think.
As I say, I’m new to Omni Automation - so thanks for your patience :-) .
I ask that because the help text on your GitHub page says to:
*Locate the desired .omnijs, .omnifocusjs or .omnioutlinerjs file.
after I’ve unzipped the file in question. So I was looking for any one of those three - and found one - with the right extension. Am I correct?
I have OF as well as OO (love them both!); but can’t see a folder readily identifiable as ‘iCloud’ for either/any Omni app in my user hierarchy, or in iCloud drive etc.
But if the files you kindly supplied are OK where I’ve put them, that’s OK, isn’t it?
I should clarify that in the repository — thanks for the question. Plug-Ins for OmniOutliner can have .omnijs or .omnioutlinerjs extension; the ones for OmniFocus, .omnijs or .omnifocusjs… and so on.
That’s interesting. They were automatically created, in my case:
Yes, of course. However, as that isn’t a location synced with the cloud, those plug-ins aren’t going to be available on your iOS devices (in case you have any).
Thanks. Got it. To anyone familiar with Automation, that much is obvious - as it is to me, now :-)
My apologies for not looking more carefully. I think I was expecting an additional ‘base’ file which would allow all the others to work. But I understand completely now.
Maybe it was/is an option that I chose not to use?
I do have OF and OO on two macOS devices and OF on my iPhone.
Perhaps I should create it?
Any harm in doing so manually?
Can’t immediately see any documentation; this comes close.
So really it is an advantage! Can I just create a folder called something like ‘Omni’ in my iCloud Drive hierarchy, Gabriel?
I think I’ve made some progress: in each of OF and OO I went to Automation > Configure.
In each case there is a location (folder, pseudo folder?), ‘OmniOutliner in iCloud Drive’ and ‘OmniFocus in iCloud Drive’.
Significantly, I can see now only see a Finder folder in Locations > iCloud Drive for OF.
Then ‘Reveal in Finder’ showed the respective OF and OO folders where the plugins were expected.
So I dragged the scripts one by one from their locations in the filesystem into the ‘proper’, target (pseudo/virtual) folders as indicated in each of OO’s and OF’s Configuration dialogues.
Thanks so much, Gabriel. I really appreciate your understanding and re-assurance!
The only odd thing (I think) is that I can only see the OmniFocus folder under iCloud Drive - and not an OmniOutliner one.
Yet in each case Automation > Configure > Reveal in Finder does show that the plugins are in the iCloud Drive hierarchy.
Although for OmniOutliner, they are in a parent directory, ‘Plug-ins’.
iCloud Drive > Plugins is not visible in the Finder.
So should I move Convert to Project (Here).omnijs and Focus Parent of First Selected Row.omnijs up into a new directory which I’d create in iCloud Drive, ‘Omni Outliner’? Do we have the ‘freedom of choice’ to make such changes in the filesystem outside the Omni Automation environment.
That’s strange. Could you show me a screenshot ? In case of OF/OO, plug-ins should be inside iCloud Drive/OmniFocus/Plug-Ins or `iCloud Drive/OmniOutliner/Plug-Ins, respectively.
I wouldn’t advise you to do that. The ‘OmniOutliner in iCloud Drive’ is automatically created by the software. If you do not have it, the easiest way to get OmniOutliner to re-create this folder would be to try installing an automation plug-in into the iCloud location.
Attempting to install a .omnioutlinerjs file should trigger a prompt to install it. Here, you can choose the iCloud location.
I made a dummy .omnioutlinerjs file, so you can try:
Something a little strange going on - mainly, I now believe - about the visibility of my OO iCloud (Plug-Ins) folder!
Firstly, I moved the plugins into their respective ‘Plug-Ins’ folders manually. But I can only do this (navigate to the folder in question) by OO’s Automation > Configure > Reveal!
Here is a screenshot of your test file (thanks) being installed:
Arranged by name (alphabetically) ‘OmniFocus’ is there preceded by ‘Numbers’ and immediately after comes ‘Pages’. But no sight of ‘OmniOutliner’ in iCloud Drive!
So I can explain the first puzzle about OO’s Plug-ins being in the wrong directory. I put them there because I cannot see an OmniOutliner directory in iCloud Drive.
And everything seems to be working. But there remain two anomalies:
why didn’t/hasn’t OO created the folder in the right place?
why can’t I see it in the Finder… ~/Library/Mobile Documents appears to be a pseudo directory of some sort: although I can open it - to reveal only OmniFocus (and its Plug-ins) - in the Finder it appears to have no subfolders
