Software History

Continuing with my little spate of sharing workflows for the iOS app known as Workflow, I’ve decided to share another simple action extension workflow that allows you to save web pages as a simplified style PDF Whilst I personally use Evernote as my snap shot repository and page cleaner of choice, sometimes I want to be able to send other people a snap shot of a page and Workflow provides a relatively easy way to do this.

TextExpander is one of my most frequently used Mac utilities and I have all sorts of snippets that help me with all sorts of tasks. From correcting my seldom perfect typing and inserting standard sets of boilerplate text through to more advanced ones that produce fill-in forms and carry out conversions of clipboard text. This focus of this post certainly falls into the latter, but does so in doing something surprisingly simple. It takes plain text and simply adds HTML paragraph tags in at the appropriate locations.

During my career I’ve encountered dozens of processes, agreements, work packages, projects and changes that have, for one reason or another, failed. Whilst the contributing factors varied, there was one that has almost always appeared somewhere in the chain of events responsible for the failure. A deficiency in communication.

In Q1 of 2015, Nakisa released the latest iteration of their visualisation suite (VSN) of applications - version 4.3. With 4.2 being an interim release for Nakisa’s Performance and Goals product or perhaps an internal working version, 4.3 can probably be considered an upgrade from the 4.1 SP2 release. As well as rolling in various bug fixes and general performance improvements, version 4.3 includes some great feature enhancements.

Smile Software have just released a new update to their TextExpander product that brought a particularly interesting new feature. The option to run JavaScript based snippets. At first this may appear unremarkable given that the previous OS X snippets could take advantage of AppleScript, or shell script based options such as BASH, Perl and Python (to name just a few). The exciting thing to me however was that the JavaScript based snippets could also run on the iOS version; whereas AppleScript and shell script based snippets cannot. As an initial foray into using JavaScript snippets on my iOS devices I decided I’d try recreating one of my existing snippet groups.

Workflow app is one of my favourite iOS apps.  As well as being incredibly innovative and useful in so many ways, it is also something I enjoy exploring and tinkering with.  In fact I’ve pitched in on Twitter several times to give people a hand figuring out how to do what they want in Workflow.

Recently I was working for a client who had particularly strict controls around access and tools that I could use. Whilst the bulk of the work I was carrying out on their Linux box could be managed using vi, I found it a little limiting when analysing some of the log files the work was producing. On the Windows machine I was using to access the files I only had Windows notepad and this really doesn’t handle Linux file endings well. As a result I put together a quick VBScript to help with this.

Workflow is a fantastic iOS automation app that allows you to do many wonderful, amazing and even crazy things. One of the problems for me through has been controlling process flow can be quite cumbersome - particularly with the larger and more complex workflows as well as workflows that I’d like to loop in some way or re-use. The programmer in me has certainly been pining for this sort of feature. Of course workflow being workflow there is a way to work around this limitation - at least to an extent which has improved workflow creation vastly for me.

Since the release of the Workflow application for iOS I’ve written quite a few workflows and as time as permitted I’ve been sharing many of them out to the world via this site. They’ve taken the form of full blog posts describing how the more complex workflows work through to simpler example workflow posts where I’ve just posted a description of what the workflow is intended to do. As part of these posts I’ve been creating full screen shots of the workflows which a number of people have asked me about. In this post I’ll be revealing how I create them along with some details of a workflow that I developed out of these blogs and has enabled me to fairly quickly put together the example workflows.

Part of my blogging about Workflow workflows involves me capturing some basic details about the workflow. This includes the name of the workflow and the link to download it. As part of my reference system these are both key items that I wanted to make available in a text file in my Workflow folder in Dropbox. This is the first workflow step in my blogging process.

This workflow I don’t tend to use as part of the process of creating my blog post information. Rather it is a way of giving myself a backup of the workflow in case I need to restore it and find for some reason that the online page is unavailable. Remember it is easy and painful to not have enough backups and only slightly more effort and a lot less pain to have enough … I’ve yet to meet someone who has too many. Also since this runs as a fully automated part of my blog post preparation process it really is no effort to have it included and run.

One of the elements I use in my blog posts (among other places) are workflow icons. I try and choose meaningful pictographs for the icons (though the set could do with a significant expansion) and I try to use the base icon colour in a meaningful way. Within my blog posts I often use them as the intro image - as I do in this post and so having a copy of the icon image ready and waiting for me when I blog is a real boon.

A big piece of my workflow blogs (and something readers have commented on many times) are the workflow screen shots I produce. As detailed in the Blogging About Workflows blog post I take several overlapping screen shots and use an iOS app to stitch them together into the mega-length screen shots that you’ll see scattered through the workflow related blog posts on this site. However the images that it creates include parts that I don’t which to use. These are the top bar that shows my time, battery level, etc. (which many people including Federico Viticci and Dr Drang find a need to remove - ref. MacStories) and the workflow bottom bar (Actions and Workflow buttons). I’ve automated the cropping of the screen shot with a workflow to do exactly this. It also saves the file into Dropbox for me and offers to delete it from my device camera roll.

The final part of my blogging about Workflow workflows is focussed on tidying up. When I produce the composite screen shot described in the Blogging About Workflows blog post I almost always end up with a small stack of screen shot files sat on my device. Once the final cropped image is produced, I have no further need for them and this workflow is used for deleting them, but it will work stand alone just fine; deleting any screen shots generated in the last twenty minutes.

Since the release of TextExpander 5 on OS X and TextExpander Touch 3 on iOS I’ve been updating and revising my TextExpander snippets to take advantage of some of the new functionality and to get some of the contents better aligned for sharing online with the public. Today I’m happy to say I’ve taken a significant step forward with a new update to the Thought Asylum TextExpander snippets groups.

I was recently having a discussion on Twitter about how to get into creating workflows for the amazing iOS app known simply as Workflow. It allows you to use Automator style actions to put together simple yet sophisticated sequences of actions to carry out an operation such as manipulating a photograph or sending a message out on social media channels. Unfortunately the problem currently is that the available resources can be difficult to find.

Today I was using one of my TextExpander snippets that utilises form fields to add some content to this site. I’m one of those people who still typically works in HTML when working with a content management system (sometimes it is the only way to get things how I want them) and when I was adding HTML content into one of the form fields I noticed that the double quotes for the attributes were being automatically being turned into smart quotes rather than staying as the nice simple dumb quotes I needed. It wasn’t something I’d noticed before and it was incredibly frustrating to correct after using the form field each time. After a bit of digging around in TextExpander preferences, etc. I finally found the rather simple solution.

A while back I refreshed and expanded upon my TextExpander snippet groups and promised to start covering some of the inner workings of what the snippets actually do. Today I found a bit of time to make a start on that and I’m beginning with some of the snippets related to underlining.

In my work I regularly work with software that (unfortunately) has a dependence on Adobe Flash Player. There can be compatibility issues with particular version combinations and so occasionally I find myself needing to verify Flash player versions. Normally I’m able to do this by visiting any of a variety of web sites that can query the version number of Flash player. However I recently found myself in a position where I was remotely accessing a client machine, but it had no Internet provision meaning I couldn’t query it from any of the usual sites I use. Instead I employed a simple trick to work out the Flash player version.

Whilst I have knowledge of coding languages is reasonably broad my knowledge of spoken and written languages is rather limited. English is pretty much my only language though I can probably get away for asking directions or buy a coffee in a handful of others. It therefore isn’t really a surprise that from time to time I come across information that’s in a language I don’t understand well enough to translate it myself. When I’m at a laptop or desktop computer with an Internet connection I use an online translations service like Google Translate. Sometimes however I’m on an iOS device and whilst I can use such services I decided to put together a little Workflow app workflow to try and speed up the process.

Happy new year everyone. We’ve passed another year’s end so once again it’s time to take a look back at what’s been most popular on thoughtasylum.com in the past twelve months and what’s I’ve been up to.

On 12 January 2016 Microsoft officially ended support for all remaining versions of its Internet Explorer browser prior to Internet Explorer 11. As a result Microsoft will no longer provide security updates or technical support for versions prior to Internet Explorer 11. This can potentially leave users vulnerable to yet to be discovered security vulnerabilities and as history bears out this is a very real risk.

As regular readers of this site may know I’m a big fan of the Workflow application on iOS. It’s an application that allows you to build up sequences of actions to carry out some sort of automation. I use it for many little helpful things on the go and one of those is combining together images into a single collage image which is what I’m sharing today.

Club MacStories is a membership value add option provided by the rather popular MacStories.net web site. I’m a Club MacStories member and as such receive the weekly newsletter which contains lots of additional Apple related material and articles. In last week’s newsletter (issue 24) one of the user questions was around automatically attaching and detaching DMGs and whilst a partial solution was provided, the response also invited readers to round it out to complete the last part. I figured I’d give it a go and share what I came up with.

Keyboard Maestro is one of my favourite Mac utilities. It’s like having a Swiss Army knife that includes not only a simple blade but also a scalpel, chainsaw, electron microscope and a suit of armour. If I can’t easily do something in another utility chances are there’s a way to use Keyboard Maestro to get the job done.

Any Mac user interested in things such as automation and productivity will no doubt have come across TextExpander, Smile Software’s utility that allows you to instantly replace a string of text with a different string of text. This can be used to auto correct typographic errors, insert boiler plate chunks of text or even trigger scripts or fill-in forms that can return more dynamic sets of text. Like so many others who start using it I now find it indispensable.

In my last post I described a method for tagging temporary TextExpander snippets with a date stamp and using some scripting to automatically remove expired snippets. In that post I mentioned that I use Keyboard Maestro to schedule the expired snippets clean-up script and that I also used it to help me in setting up those temporary snippets. In this post I’m going to provide some details on exactly how I’m using Keyboard Maestro to help with this.

I haven’t posted about Workflow for a little while, but it remains one of my favourite applications on iOS and I’m still actively creating and revising workflows. In fact I’m currently clocking in at 176 workflows on my devices. Today I thought I’d clear up the dry spell on Workflow related posts and put something together around one of my text manipulation workflows. This particular one manipulates the character case of text on the device clipboard.

I was reading through issue 33 of the MacStories newsletter (to which I’m a paid subscriber) and I spotted an interesting request from one of the readers to do with efficiently creating presentations to have multiple outputs for a small variety of uses. The reader was hoping to find a way to maintain multiple versions automatically when updating source material. The MacStories team called out to other readers for suggestions on addressing this. In this post I’m going to outline my approach to the issue.

The majority of configuration in Visualization Solutions by Nakisa (VSN) applications is achieved via the changing of settings in the AdminConsole, Nakisa’s standard administration interface. For a typical configuration this is all that you would require. Unfortunately all too often, typical is not what a client wants and so we have to look beyond the current capabilities of AdminConsole. There are other occasions too where perhaps it is a laborious or inefficient task to do a particular piece of configuration in AdminConsole compared to another method. In those situations I turn to configuring the underlying configuration files directly.