Jump to content

Manuel Rauber

Member
  • Posts

    4
  • Joined

  • Last visited

Everything posted by Manuel Rauber

  1. Ok, found out its much easier putting everything into OSAScript with JavaScript and do all transformations there.
  2. Hi! I am currently rewriting my Workflow for the Gallery. I'll allow the user to make some configurations, some of them are checkboxes. Alfred outputs a checkbox either as "1" (checked) or "0" (unchecked). However, the program I'm feeding the final workflow to requires "true" and "false". So I need to transform all checkboxes and replace 1 with true and 0 with false. This is my current workflow. On the bottom left there's a single trigger. At the top, there are two "Arg and Vars" simply mapping a variable to {query}: After that, two replace items are doing the replace from 0 and 1 to false and true. And after that, a "Arg and Vars" writes back the query to the variable: However, in the debug node the transform is not visible. I only get the output from the bottom path with Run Script. If I remove all connections to the debug node and only use a single connection from one of my variables, it works as expected. My question is, how can I transform multiple variables as described above, combine everything together and feed the result to the debug node? Thanks!
  3. Hi, I created my first simple workflow to use ray.so a bit more easily. Invoke the workflow with ray or ray <language> whereas <language> is one of ray.so's supported languages. The workflow will use the current clipboard as source for the code, transform it and opens your standard browser with ray.so with your code. It uses the standard settings of ray.so. Take a look at the global variables in the workflow to change the standard settings, as well as the default language (which currently is csharp). Transformations As mentioned above, the workflow will do some transformations of your code before opening ray.so. Remove leading and trailing blank lines Tries to count leading empty space (spaces and tabs) in the first line of your code and then trim all lines with that count. It will fail on code that has keywords that are not intended, for example in C# with #pragma I may resolve or make this feature optional in a later version. Dependencies The workflow only uses some built-in things from Alfred as well as bash scripting. So there are no dependencies. Download GitHub Download
×
×
  • Create New...