<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: LOBK</title>
    <description>The latest articles on DEV Community by LOBK (@lobk).</description>
    <link>https://dev.to/lobk</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F351638%2F904cfde9-ceaf-422d-9724-7b2aa67d929e.png</url>
      <title>DEV Community: LOBK</title>
      <link>https://dev.to/lobk</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lobk"/>
    <language>en</language>
    <item>
      <title>Accessing OmniFocus Link in iOS</title>
      <dc:creator>LOBK</dc:creator>
      <pubDate>Tue, 17 Mar 2020 01:57:39 +0000</pubDate>
      <link>https://dev.to/lobk/accessing-omnifocus-link-in-ios-52b2</link>
      <guid>https://dev.to/lobk/accessing-omnifocus-link-in-ios-52b2</guid>
      <description>&lt;p&gt;Kourosh Dini's "Creating Flow with OmniFocus" recommends adding OmniFocus (referred to as OF from hereon) links to the note section of actions. This helps separate projects and the actual task required to complete the project. This segregation also helps with decluttering Forecast perspectives, because you can add a due date to the task associated with the project instead of a due date on the project. This means that your Forecast perspective won't be cluttered with 15 actions (which all live inside a project) all being due at once. &lt;/p&gt;

&lt;p&gt;This workflow was made easier due to OF3's 'Copy as OmniFocus Link' feature in the context menu. However, it is not as easy to do on iOS. While you can press the 'Share' function on any project or action and copy its OF link, any OF project or action can share up to 5 different outputs.  This means there are a lot of taps required just to access its link.&lt;/p&gt;

&lt;p&gt;In response to this, I created a shortcut that has served me well. It only has 4 actions, so I feel comfortable writing out the steps here (in the future, I may include screenshots. For now, I feel lazy).&lt;/p&gt;

&lt;p&gt;Get OmniFocus Link:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Accepts &lt;code&gt;Text and URLs&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Get &lt;code&gt;Item at Index&lt;/code&gt; &lt;code&gt;4&lt;/code&gt; from &lt;code&gt;Shortcut Input&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Show notification &lt;code&gt;Copied Text "Item from List"&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Copy &lt;code&gt;Item from List&lt;/code&gt; to clipboard&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;While Step &lt;code&gt;3&lt;/code&gt; may be considered redundant, I feel reassured I'm getting what I want every time I invoke the shortcut. It would be awkward if the shortcut was to break one day and I didn't know what content I was yanking to my clipboard.&lt;/p&gt;

&lt;p&gt;Sometimes, the best shortcuts are utility shortcuts. They don't do anything profound, but aid immensely with the creation of new shortcuts. I was only able to achieve Step &lt;code&gt;2&lt;/code&gt; because of a meta-shortcut called 'Output Inspector'. It previews the type and content of items being shared in the share menu. I will discuss its function in another post.&lt;/p&gt;

</description>
      <category>sirishortcuts</category>
      <category>ios</category>
      <category>omnifocus</category>
    </item>
    <item>
      <title>Creating Anki flashcards on iOS</title>
      <dc:creator>LOBK</dc:creator>
      <pubDate>Tue, 17 Mar 2020 01:42:37 +0000</pubDate>
      <link>https://dev.to/lobk/creating-anki-flashcards-on-ios-2i2m</link>
      <guid>https://dev.to/lobk/creating-anki-flashcards-on-ios-2i2m</guid>
      <description>&lt;p&gt;Creating Anki flashcards can be a clunky process on the desktop, more so on iOS. I have created a Siri Shortcut that grabs a list of questions, asks the user to answer each question and adds both the question and answer to Anki. I modified the shortcut so that I can also have the question and answer added automatically into Anki.&lt;/p&gt;

&lt;p&gt;The former is useful for reinforcing concepts before they are added into Anki. I've found that flashcards are more useful if I've already tried to learn the content first, rather than learning it after I've added it to Anki. However, there are times when I'm reading a textbook and creating flashcards at the same time. As a result, I prefer to have the answer saved so that I don't have to go back in the textbook to find the answer. &lt;/p&gt;

&lt;p&gt;The callback url (forgive me, I still don't know what the correct 'terminology' is for url schemes) for Anki is &lt;code&gt;anki://x-callback-url/addnote?profile=&amp;lt;USER&amp;gt;&amp;amp;type=Basic&amp;amp;deck=&amp;lt;DECK NAME&amp;gt;&amp;amp;fldFront=&amp;lt;CONTENT&amp;gt;&amp;amp;fldBack=&amp;lt;CONTENT&amp;gt;&amp;amp;tags=&amp;lt;TAGS&amp;gt;&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&amp;lt;DECK NAME&amp;gt;&lt;/code&gt; and &lt;code&gt;&amp;lt;USER&amp;gt;&lt;/code&gt; can be hardcoded into the URL because they don't change much. However, I decided to use Magic Variables instead of hardcoding them in case I want to switch decks in the future.&lt;/p&gt;

</description>
      <category>sirishortcuts</category>
      <category>ios</category>
      <category>anki</category>
    </item>
    <item>
      <title>Hello World</title>
      <dc:creator>LOBK</dc:creator>
      <pubDate>Tue, 17 Mar 2020 01:26:02 +0000</pubDate>
      <link>https://dev.to/lobk/hello-world-3i9c</link>
      <guid>https://dev.to/lobk/hello-world-3i9c</guid>
      <description>&lt;p&gt;This is a temporary (or maybe permanent? who knows) blog covering automation topics. I've been interested in automation for a while now, and I think it'll be a good idea to create a trail of my thoughts and automations.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
