Jump to content

CJK

Member
  • Content Count

    79
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by CJK

  1. Hi @JDG, Having had a look on the Logos website, I can't see any references to AppleScript in their Mac support pages. My guess is that the app is not scriptable. You can determine this definitively by opening Script Editor and executing this single line of code: tell application "Finder" to get has scripting terminology of (path to application "Logos 7") replacing "Logos 7" if the name of the application is different to this (go by either the application filename, or the name that sits in the menu bar in the top-left of the screen when you use the application). Script Editor will either return true or false. Working for now on the assumption that it's going to return false, I believe you have two options: ① As @deanishe suggested, UI scripting could possibly (probably) achieve what you need, but it's a real sledgehammer of a technique that isn't always going to work seamlessly (but it's better than nothing). The barrier I see to this option is that—I assume—you don't have much AppleScripting knowledge, and UI scripting is virtually impossible to do unless one has the application to work with on one's own system (which makes someone else's help dependent on them both knowing AppleScript and having the Logos software). ② Their web app might be a more accessible way of retrieving data that you would otherwise get from the desktop application, especially if you use Safari or Chrome. As both Safari and Chrome are scriptable, this presents some possibilities for automation, either by way of http queries or by way of JavaScript. But, again, one needs an account with FaithLife to access the web app. I'll let you contemplate on this.
  2. I think you will have you use some scripting for that, i.e. AppleScript. What is it you actually want to achieve ?
  3. *facepalm* You'll want to take another look at the workflow I uploaded for you. Yes, it so happens that I (randomly) chose the workflow's action to open up a folder in Terminal, but No, the workflow itself does not employ any scripts or the use of *Terminal* in order to search through folders within Alfred. You're asking: and that's exactly what a File Filter does, and what my workflow demonstrates.
  4. Unfortunately, you didn't post a screenshot of the workflow in action, perhaps just after you had typed f in the search bar, and began to enter the first few letters of a folder name. Did you set a search scope for this filter ? I've uploaded a workflow here that uses the File Filter to allow you to select a folder, the location of which will be the working directory of a new Terminal window that opens up. To use, open the Alfred search bar, type cd <space> then the start of a folder name, e.g. cd vol which, on my system, brings up /Volumes, Kill Bill Volume 1. soundtrack folder, etc. If this workflow doesn't work for you, then this might be a symptom of a bigger problem.
  5. I went ahead and created the workflow for you using dummy data. You can download it here. As per your description, it's triggered using the keyword `wcp`, which accepts a single argument, currently `product1`, `product2`, ... , `product55`. Upon selection, the URL referenced by argument entered gets passed to the next action. There's an Open URL action waiting on the workflow's workspace, not yet connected to the trigger. Instead, a Large Type output receives the URL, allowing you to preview the URL fully for testing purposes.
×
×
  • Create New...