Our DVD collection had long since overtaken the available shelf space, with cases piled up on the top shelf. Hardly an attractive look for the living room. Some while ago I bought compact sleeves from Samba Tech Limited into which I planned to transfer the DVDs. But first I needed to catalogue them, as with no visible spines finding individual films would be a challenge. Fortunately, I had been maintaining a database of the films using the superb Collectorz software, so it was simply a matter of deciding on categories and indexing the individual discs accordingly. I say simply, but in fact it turned out to be quite time consuming.
With a total of 511 recorded entries you will not be surprised to learn that there were a few errors in the data. A couple of DVDs had seemingly gone missing, probably lent out and never returned, while there were a number that I had omitted to add to the database when they were purchased. I decided that I should create a fair number of categories and limit the number of discs in each. Without visible spines, I needed to file them alphabetically, but not as one single collection. I therefore created categories with no more than about 60 DVDs in each. It has worked out very well, and because of the respective numbers in each section, it has been possible to retain the original cases for some DVDs, especially those containing two discs or with special cases.
You can buy folders that each house about 25 sleeves, but this adds to the cost and in our case would have used up the valuable space that we were trying to recover. As it is, the sleeves on their own, when viewed as a group, appear almost like a blank black space on the shelves between those DVDs that I've retained in their cases. The effect is quite aesthetically acceptable.
I can now use the iOS app version of the Collectorz software to look-up individual DVDs, but I've also created a paper listing by exporting the database into Excel, which has allowed me to customise the document to my own requirements, rather than just printing from the Collectorz database. There were a couple of hitches in doing this, the first being that accented characters (in French film titles) didn't appear correctly when the exported text document was opened in Excel 2016 for Mac. I resolved this problem by first opening the raw exported text document in TextEdit and then opting to 'Save As', while changing the Plain text Encoding to Western (Mac OS Roman) in the 'Save As' options. The second was to be careful not to re-sort by title while in Excel. The Collectorz database ignores the words 'A' or 'The' at the beginning of a title when sorting, whereas Excel doesn't. It's fine to sort on other fields, but not on the titles, which has allowed me to create a second listing based on category.
All in all a very satisfactory outcome.
After holding back for a while I finally updated my iMac to High Sierra this week. I had read about various problems affecting some applications and, of course, the more recent security scare that has been patched in 10.13.2. The update went without a hitch, although it took a while. I think the file had downloaded some time previously, as no sooner I had updated than I received another update message to install the latest version, which also took a while.
In launchpad a few applications were marked with the symbol indicating that they were no longer compatible. Final Cut Express was one such, but this wasn't an issue as I had long since abandoned it in favour of Adobe's Premier Elements. There was an associated application, LiveType, which was also shown as non-compatible, but was equally of no interest to me. Adobe Bridge also had to go, but again I never used it. I had already upgraded to Office Home and Student 2016, expecting problems with my 2011 edition. Luminar prompted for an update, but having installed it I then decided to go for their Holidays' offer and upgraded to the 2018 version.
All seemed well until I updated one of my managed websites using RapidWeaver. I had a minor rendering problem in Safari. This resolved itself after clearing all caches but there was a fair bit of head-scratching before I got to that point. Firefox behaved impeccably but in Google Chrome the navigation symbols were showing visual artifacts. No amount of cache clearing or resetting would clear the problem, and having visited some forums it became clear that there are indeed some issues with Chrome when used with High Sierra. Having effectively given up on this particular problem I downloaded the still 'early adopters' version of Chrome Canary. I don't use Chrome generally and really only wanted to see if the issue persisted in this 'bleeding edge' version. I'm pleased to say it didn't. So for the time being anybody viewing the website using the original Chrome with High Sierra will experience this problem, but my hope is that the number of people in this category will be small.
The only other issue I experienced was with Word. I keep all my data on a network drive and when I attempted to close a document after saving, I received an error relating to permission to access the temporary file that Word had created. These files should be removed when the document is closed, but this wasn't happening. Again, it took a while to find out what was going on, but I eventually found an explanation that suggested that this was a problem associated with network drives with Word on High Sierra. The fix was to uncheck 'Save Autorecovery info' in Word, which of course disables auto-recovery, but it seems to have cured the irritating error messages and the orphan folders that were being created.
There may of course be other issues awaiting me as I use applications that I've not yet launched but, as they say, so far, so good!
With Microsoft discontinuing support for Mac Office 2011, and suggestions that there may be problems with it should I upgrade to High Sierra, I took the plunge and bought Mac Office 2016. John Lewis were doing a £20 discount and I had some JL vouchers.
The first surprise, which shouldn't have been if I had read the product details fully, was that all I got was a pretty little box with a product key card inside. I would have preferred a disc. The instructions read that I should go to office.com/setup. This landed me on a web page that appeared very unlike what I would expect from Microsoft. Talk about Web 1, it looked like something a first time web builder would have knocked up. Totally misleading as to what one was supposed to do, and raising suspicions in my mind that it wasn't a site where I was going to enter my expensive product code.
After a bit of browsing I navigated to a much more official looking Microsoft site, where I was asked to open an account. So here we go, I've just paid good money for a product and I must open an account to get past go. Having done that MS emailed me to verify my email address, then I had to negotiate a captcha code, and finally I got to entering my product key. A file downloaded into my downloads folder. I opened it but nothing seemed to be happening. But then I noticed the download progress bar on the Safari menu bar. After a while an installer package appeared in the downloads folder and this launched the familiar (Mac) Office installation dialogue.
Everything installed, I opened Excel and was presented with the next hoop to jump through. I needed to sign in using the account details I had generated earlier. This done, I was ready to use the software. Why do Microsoft make software installation so complicated? What a performance.
I haven't started to play with the new ribbon layout yet, although it appears pretty much unchanged content wise. In keeping with recent trends the icons on the ribbons appear 'flatter', exhibiting a 'button' relief only when you hover over them. I think I may prefer the 2011 look, but no doubt I shall get used to the new one after a while. You can keep the previous version on the Mac; a fall-back if I really struggle! It may be imagination but it feels as if the individual applications open more slowly.
I'm really pleased that the only time I need to deal with Microsoft is in respect of the Office software.
With High Sierra now available I made the customary check to see what possible problems may result from installing it. What I found was a bit worrying. Not in respect of High Sierra itself, but the fact that the subsequent update is not going to support 32 bit apps. A quick check on how many 32 bit apps my Mac is running revealed a very long list, and they are not by any means all minor pieces of software. For example, Amazon Music, Audacity, BBC iPlayer, Kindle, Libre Office, MS Office 2011and many more, a lot of which I use regularly. Perhaps the respective developers will be producing updates before the fateful day, but I would imagine that rewriting 32 bit code into 64 bit code is no simple task.
As for MS Office 2011, I further discovered that MS are not going to support it on High Sierra, and in fact all support for this version will end on 10th October this year. With Microsoft limiting its basic Home and Student offering to one computer, replacing the copies on my Mac, my MacBook and my wife's machine would be very expensive. My existing Office 2011 came in a family pack with three licences. I may, therefore, initially only upgrade the copy on my Mac. My MacBook is still running El Capitan, being too old for Sierra, and fortunately my wife rarely uses Office.
Every so often Apple makes a move that renders a lot of legacy software, and sometimes hardware redundant. We are I fear approaching one such paradigm shift. The arrival of Snow Leopard cost me money and it seems that the post-High Sierra world will do likewise. But, on the other hand, this clean-out of arguably less efficient technology at least avoids the situation in which Microsoft finds itself, where the need to continue to support legacy programs has resulted in the Windows operating system containing far more code than it need do.
I use Rapidweaver for my own personal website and a few others that I manage. On my personal site some of the pages were text heavy and I thought that a 'Read more' feature would make them less off-putting. The trend seems to be to have minimalist content because web surfers are notorious for rejecting anything that looks like it will need time to digest. I think they're called the 'Now Generation'.
There are many third party developers that produce add-ons for Rapidweaver that allow a host of additional features without the need to code or have any detailed technical knowledge. So I thought it would be easy to find what I wanted. However, I was perhaps guilty of not doing my research deeply enough, as I had two false starts before getting what I wanted.
My first port of call was DooBox where I found Trunk8 (truncate - get it?), a 'stack' (an add-on) that limited the number of lines shown on screen with a 'Read more' link to see more. This seemed to fit the bill, but I should have been a bit more circumspect as the demo of the add-on showed how it can keep multiple columns the same length by fixing the number of lines displayed.
I bought the stack and tried it out, only to find that if I had any layout in the text, such as paragraph returns, these were completely ignored. So when applied to a page of text the resulting display showed it all concatenated. This wasn't what I wanted. A posting on DooBox's Slack forum elicited no response from the company, so I guess it does what it does and so tough! The £8.99 I paid is probably not wasted as I may one day want to do what the stack is designed for, but not today.
As I've explained previously, my blog is now on my personal website. By using the Armadillo stack in RapidWeaver not only can I post to the blog from any browser, but a facility exists to add a facebook share button to each blog post. However, I am running three other blog pages on this site, for cinema reviews, my golf diary and my fishing diary. Transferring these into Armadillo was not feasible without some sort of automated option, which isn't available. So these three 'blogs' remain as native RapidWeaver blog pages.
I thought it would be nice to add a facebook share button to each post in these blogs and set about trying to do this. My efforts weren't rewarded. The facebook developer pages allow you to generate code for the placement of a share button, involving three code snippets: one to be placed in the page's Head section, one in the Body section, and the third where you want the share button to appear. Having negotiated the difference between meta name tags and open graph meta tags, the latter being required by the facebook code, it soon became clear that the native RapidWeaver blog page applies the same Head and Body code to all the posts, because in effect the posts are sub-sections of one large page. This being the case it seemed to be impossible to generate a unique share button for each post. Well, that is the conclusion that I eventually came to.
I've been waiting for Sierra 10.12.1 before updating and this morning I took the plunge. It transpired that 10.12 had already downloaded to my machine so I ended up with the original version with a further update to 10.12.1 offered after the initial update.
Part way through the first update the progress display jumped to my second screen. I didn't worry too much but when everything rebooted I found that my second screen had become the primary display, with a desktop image different to that before the update, and my lovely iMac Retina Display had become the secondary display. My first attempts at resolving this via Google failed but then I noticed that the App Store was flagging the 10.12.1 update, which I hoped would resolve the issue. It didn't!
More targeted Googling (using primary/secondary screens as keywords) led me to a web page that gave me the solution. As usual, it was easy once you knew how. I had already visited the Display page in System Preferences, but what I didn't realise was that the white bar above the primary screen can be dragged to the other screen. This done and the problem was solved. In System Preferences/Display there is reference to moving the menu bar, but it's not immediately clear that this changes the default primary screen.
I have a copy of Windows on a Bootcamp partition on my MacBook. I put it on, as Windows 7, when I got the computer back in 2009. I saw it as a fall-back resource after moving over to the Mac platform on my desktop in 2008, just in case I needed to do something in Windows that I couldn't do on the Mac. That situation has never really arisen but I keep Windows updated and yesterday, after waiting an age for the update request to process, I was prompted to install the Windows 10 Anniversary Update. To be fair there weren't any real problems but boy oh boy it took an eternity to complete. It had been going well over an hour when I decided I couldn't wait any longer and took the dog out.
When I got back the computer had rebooted into OS X, as it will do if you don't intervene. I restarted and selected the Windows partition, and eventually everything finished off, leaving me with my new Anniversary Edition. I can't say that I noticed a great deal of difference but no doubt there are new things going on under the hood. The experience certainly didn't dent my conviction that moving to a Mac was the best thing I've ever done.
As part of the reorganisation of my web presence I have decided to add photo galleries to my personal website. I currently have a small portfolio of images at 500px, a site that offers images for purchase. I've no illusions about anybody wanting to buy any of my images so I've decided that I will unsubscribe from that site before my next renewal in July 2017. Thus the reason for establishing photo galleries here at Kilburnlad.
I had bought the Photo Stack from Nick Cates Design and had already implemented some galleries within my Fishing section, and on the Chatteris page. However, for my new photo galleries I've taken a warehousing approach for the images. This was new territory for me and while it's not terribly difficult, I had a couple of false starts. Basically, warehousing involves uploading the images to your host server and then calling the images as needed by the Photo stack. The main advantage of this is that the images are not embedded within the RapidWeaver project file, which means that they don't need to be rendered each time you re-publish your site, speeding up publishing and keeping your project file smaller.
I've managed to restore the light box galleries on the Chatteris, Best Fish and (Fishing) Places pages. I use the Nick Cates Photo stack and for some reason the images had vanished from the site. After a bit of experimentation I found that I needed to remove and then re-insert the Photo Base stack on each of the affected pages. Fortunately I didn't need to remove the individual Photo Group stacks, but I did need to re-drop all the images, which was a bit laborious. Everything should now be working.