The wall planner script cometh!

In my last article “My Calendar Caffuffle“, I’d mentioned that I was working on a wall planner script for a Christmas release, but due to many factors I was unable to release this script and instead opted for a smaller script that – for many regulars to this site – didn’t really feel like much of a Christmas gift.

To this end, I felt like I let my supporters down and had to make sure that amends were made in the new year. On that note, I was able to work through the issues that held back the script, and I can now release the script free to the public:

01-ui

This script will create a twelve month planner based on a start month and year, and to an output size in millimetres. There are one of four ways to display the planner based whether the months should appear in rows or columns, and whether the planner should be condensed or expanded. For example:

02-orientations

Before you say “I don’t like the colour”, note that the script creates the necessary styles so that the wall-planner can be tailored to your needs:

03-styles

Don’t fancy starting the calendar in January? That’s no longer an issue either, the planner can start on any month:

04-midyear

So that’s the free version of the script that can be downloaded from the downloads page now.

Want more? Well, I’m also working on a pro-version of the wall-planner script that will have additional features such as:

  • highlight school days from known dates, a customised range, OR a text file;
  • add events from a text file that contains the dates and events;
  • (in expanded format) begin the planner on any day, not just Monday;
  • highlight cells based on Find/Change or GREP searches;
  • additional formatting options (appearance of months and days).

Screen Shot 2018-03-03 at 22.46.50

06-proresult

Lastly, speaking of pro-versions, I’ve also been busy improving my long-popular Data Merge to Single Record script for its pro-version release. Don’t panic, the free version will remain, but to access features shown in the dialog box below, the pro-version will be a paid release.

07-sneakpeek

If you’re interested in the pro-versions of the scripts mentioned in this article, please contact me through the contact page.

Advertisements

My Calendar Caffuffle

UPDATE 2018-02-24: The script is now working and available from the downloads page. Click here to read more about the script in action.

Around this time of year, I usually get into the festive season by offering a new script for readers of the website. This year, I intended to release a free script that would generate a year planner based on the calendar year, page size and school term dates. After a weekend or so, I’d managed to create a proof of principle script using a Native InDesign Dialog and used it in a live project. Here are some shots of the first iteration of the script, along with the output:

01oldUI

02oldresult

While the script worked, it was not perfect, given that there was no error correction for the date fields, so if values were entered into date fields that weren’t the correct date syntax, the script would return an error. It was at this moment in time that I’d realised something very important:

There’s a difference between Native InDesign Dialogs and ScriptUI

Gabe Harbs has a brilliant write-up about the differences on the InDesign Scripting forums but ultimately it meant that the script would not allow for error correction unless it was rewritten using ScriptUI, something I was hoping to avoid. I’ve begun the re-write of the script but have not proceeded to far as I’m encountering a few issues. Here’s what I have now:

03newUI

For now, that’s as far as the script has progressed, and this leads onto the second issue:

A busy work schedule that included Adobe MAX

IMAG0547

Between October to December is usually very busy as there is seasonal work such as school diaries, yearbooks and other collateral that is wanted by the end of the Australian school year. In addition to this influx of work, I also had the opportunity to attend Adobe MAX 2017 in Las Vegas, Nevada, USA.

During MAX, I’d informed several of my peers about the upcoming script that I’d planned on releasing, only to realise the following:

Schools years, terms and holidays differ between countries

In Australia, the school year starts towards the end of January and ends in the second or third week of December. There are four terms and each state has their own term dates. Within this structure, private schools can also set their own dates, and this usually varies by a week or so of the Government schools. Given that I live in Australia, I’d created the script for use within the rules that apply for Australia.

However, I’d neglected the fact that users in the northern hemisphere have a completely different school year that starts in one calendar year and finishes in the next calendar year. This rendered my script of little to no use to most InDesign users, so for now the script sits on the shelf waiting for a quieter time before I revisit the idea.

I won’t leave you empty-handed!

Despite these setbacks, I still have a festive season gift to bestow: A day to a page planner script. Upon running this script, the user is asked for a start and end date range in ISO date format. When an appropriate date range is chosen and the OK button is clicked, a new InDesign document is made, creating threaded frames that contain a day to a page that contains the correct date.

04dotwmaker

05dotwmakerresult

The script can be downloaded from the downloads page of Colecandoo.

If you are interested in the year planner project discussed in this article, feel free to contact me via my contact page.

Check out the Youtube videos too!

Since 2015, I’ve also been preparing a series of short videos on Youtube that complement the articles already on the Colecandoo website. I plan to release more videos and if you haven’t seen the channel, check it out here.

 

Data Merge to Unique Names script updated for ID CC 2018

Just a quick note that if you are a user of the Data Merge to Unique Names script, please note that the script has been updated for InDesign CC 2018. If you have not downloaded the latest version, please do so from the downloads page.

The update fixes a bug that would prevent merging to InDesign files due to a packaging issue. That said, make sure to read the instructions prior to use, particularly if using fonts that are dependent on a Document fonts folder for font usage in the file.

Of interest: New Data Merge techniques and quote bug

In the latest Colecandoo Youtube episode, four Data Merge specific features are covered, namely:

  • Adding faux-returns to a data merge field to split over lines, and subsequent limitations of this technique;
  • Using GREP styles to swap a character for a glyph during a Data Merge;
  • Highlighting field codes so that they are easier to see when not showing live data; and
  • A bug that occurs when a double-quote is at the start of any field in a Data Merge text file.

Faux returns within a field

The faux-returns technique is written about elsewhere, so rather than spoil their presentations, please read the articles directly from the appropriate sources:

I’m a fan of this trick, but emphasise that this is a workaround rather than a long-term solution, given that formatting is limited and there are more appropriate ways of accomplishing this task such as dedicated plug-ins or an XML workflow.

Swap characters for glyphs

Daniel Solis also features a clever trick to swap phrases with glyphs during a Data Merge that uses both GREP styles and ligatures. Again, rather than simply repeat the technique, please see his original video here.

A similar method can be employed using Indiscripts’ Indyfont script, but rather than swapping phrases with glyphs, will swap single characters.

Highlight Field Codes

The video also shows a method for highlighting field-codes when Data Merge is not in the preview mode. It relies on the [Basic Paragraph] style using a GREP style that contains a large highlight, and that any other styles in the document are based off of the [Basic Paragraph] style. It also means the document has to be styled correctly.

I’d demonstrated this technique following a real-world example of a live file where fields were very hard to see, and the file had to have an offset shell printed with variable data printed afterwards, so making sure the shell had no variable data on it was crucial. Using this technique would make finding the field codes much easier to see.

Double Quote bug

Also featured in the video was an issue that once again arose from a real-world example where a customer had provided a database that had double-quotes at the beginning of fields, but no closing quotes, resulting in rather unusual results.

 

%d bloggers like this: