Automating Equipd from Editorial

With the new x-callback-url scheme, I modified my Editorial workflow to use it. I have this in my toolbar on my iPad and when the speaker says a scripture, I enter it on a new line and hit the button! I used this for our latest RC and it really impressed me.

Here is the link: http://www.editorial-workflows.com/workflow/5829258328932352/PNi7LI9StBI

It will strip the spaces out of the link and use the basic scripture format for the URL.

Hope you like it!

 

Nice, thanks.

I'm also one who uses Editorial for note taking and study.

I have a similar script that converts the selected scripture into a launch able URL from the preview page. I write with the aim of producing an ePub for later review, so clickable links are useful.

It has basic error checking, to see if the selected text might be a scripture, but is not foolproof.

I'll post it when I get back home.

I also have an Editorial script that lets you select text and then search WOL. It has a bit stronger error checking, and a dialogue box that asks for the searche scope (sentence, paragraph, etc).

I was wanting to combine what I have learned to create a script that makes sure that the selected text is a scripture (not just jim 6:23, or 4 Timothy 18:99), launches Equipd, searches for the scripture, copies it, and pasts it back into Editorial with a clickable link back to Equipd.

I'm working on the error checking, but copying and returning will have to wait for Equipd to support it.

 

Personally I'd say I wouldn't need the UI. If I wanted the UI I could use a different action/URL.

 

I would think that Equipd would just return a null string for any scripture that was not found. It already appears to do some kind of checking already.

 

I'd agree with Jonathan. The current URL scheme you have already allows launching the UI. We can still use that if we need to.

If we just want to pull a scripture for a quote there is no need to launch the UI.

And no problem with this not being high priority. It's a "nice to have" not a "must have" feature.

 

I'm actually talking about creating a link, not looking up a scripture.

It turns "Prov 17:22" into [Prov 17:22](equipdbible://bible/Prov17:22) which would then become a clickable link when I compile my notes. I want to catch errors before I compile.

 

Ah yes. That was actually going to be my next project. Actually, I may do a combination in adding the scripture as a linked footnote, much like how the KM ePubs are done.

 

Ok..well I am completely lost, reading the above dialogue just proved to myself, that I completely do not know nor understand many many things, about what I can do with the Equipd bible app and other apps. So I must research, now to find the time.

Just to help me get the basic gist of it for now, in order to make up my mind to get this app, so this Editorial app, I'm basic terminology, is a search tool of sorts, it searches what ever you have, (apps, documents, so forth) on your iPad or iPhone, and brings it to one place so you can either save if for a purpose or to read it and leave it as is? Sharing of sorts between apps..yes? I so hope I am understanding a tiny bit, real sorry if it comes across clueless, as I am, but I love to know of what else I am able to have on my iPad to improve or enhance my theocratic study.

 

Hi there Mikel... no, Editorial is a text editor. It has a ton of automation features built in though, so you can script things (like looking up scriptures). If you ever used macros in Word or VBA in Word, you'll think of ways this can help. If you haven't... well, maybe you don't need it so much. Unless you have a geek on hand that will make scripts for you.

It uses a text-entry style called Markdown, that is basically plain text with a few hints that make fancy formatting much easier. If you're curious about that, you can grab Nocs for free and try it out. It doesn't have any fancy workflow automation features though.

 

Thank you so much Matthew and Jonathan, for your detailed explaination.

I do understand macros in word, so I get it, but I never really became a proper geek, I personally enjoy using computers, and I worked in an IT help desk (due to me being a patient person, as you can get rude customers who want things done 10 mins ago) hence I learned quite a fair bit, and I also helped set up a computer intergrated phone system in a job role, so I am able to do most fixes if a windows computer is playing up and understand the background of what to do to fix an issue, but I didn't get into the deep workings of codes, algorithms and programming.

I can call myself a semi-geek, as I understand the basics and can get away with making things work for me and others, so reading up on new things, wether it be an app, or a program that will enhance my time, I do love and will try. I was reading up on the new Equipd Bible app, and browsing through the forum I got to your discussion, (and it intrigued me, hence my comment) in order to be able to help the ones I introduced to Equipd in my congregation, so if they get stuck in using the new app, I have some kind of knowledge about it. So off I go to research some more, and I am going to try and use the Editorial app too!

Agape

Mikel

 

Cool, sounds like you'd enjoy it.

One thing about editorial, as opposed to Drafts or Workflow (similar tools) is the really good documentation.

 

Works really well in MS Word on iPad as well, very impressed

Thanks!

 

I have been using this as an excuse to learn more Editorial scripting, and I came up with another one.

http://www.editorial-workflows.com/workflow/5897579380342784/eXDf9nJJg6M

It will pull all of the scriptures in parentheses from the current paragraph and present them in a list for your selection. Handy if you paste in something like the daily text or a Watchtower excerpt. Hope it works for you!

 

It works beautifully! An excellent workflow! What you are learning about Editorial scripting is benefiting all of us. Thank you for your hard work.

 

I thought of one more small change I needed to do. Now if there are multiple scriptures in the parentheses (separated by ';') it will split them into list items. The URL above will still work, you may have to delete the old one and reinstall this one.

I might see if I can pull out non-parenthetical scriptures, but that's a fair bit more work. Maybe @niall can give me hints.

 

The previous workflow separated out (Joh 1:14; 3:16, 18) as Joh 1:14; 3:16, 18, which did not result in a lookup operation as no one scripture reference was distinct and separate. This is a very nice improvement, since it now separates (Joh 1:14; 3:16, 18) to
Joh 1:14
3:16, 18
Being that there is no Bible book specified in the text for 3:16, 18, the lookup operation can't be carried out, but now John 1:14 can be looked up. Very helpful!

Once again, thank you!