Got your attention with that magic word "Free" didn't I? I did use an asterisk, and since you are already here, please! read on.

I've been in contact with actual published authors recently. Once I got over the celebrity worship and envy, I wondered about the tools they use to get their thoughts down. This might be why I never quite get around to writing; I often get caught up in the what and how of the mechanics, rather than the actual doing. I also know that it is the truly rare and gifted writer that makes actual money from their efforts, and anything that can save money is a Good Thing.

I am rather familiar with word processing tools, after having written code-based document management systems embedded within the word processor itself, plus years and years of experience formatting document types to exacting specifications. You see, I am essentially lazy – as are most programmers – and instead of doing something repeatedly, I'll figure a way for the computer to do it for me. I leverage many of the existing tools in my work; it's easier than coding a function from scratch (again, I'm lazy) and there are a number of built-in features in most major word processors that – right out of the box – can greatly assist a writer in not only creating consistent format but consistent content as well. 

Since you've probably already forked out some money for the word processor (I say probably, because OpenOffice is free), here are some tips to get the word processor to do more of the work, making the tools themselves free. See how I did that?

I discuss primarily MS Word tools for a couple of reasons: (1) It's what I am using now, and (2) it's common, but these same features are found in OpenOffice and likely in most other major word processors as well, regardless of the platform. Let the easing of the wordsmithing process begin!

AutoCorrect:

 If you need more or totally need your trigger to be a real word not to be automatically corrected , read on about AutoText.

AutoText entries are somewhat similar to autocorrect with some significant added functionality – kind of like making them AutoCorrect’s bigger and much badder brother. In fact, you can bypass using autocorrect entirely and any of the entries you would have made using the autocorrect function instead. AutoText has a number of functionality advantages over autocorrect:

You can use it to create page layout changes on the fly, for example if you need to alter from portrait to landscape for an illustration and back. Oh, and have the font size and paragraph formatting different in the altered page. You can repeat the process of establishing the necessary breaks, and formatting, or you can do it once, save it as an AutoText entry, and re-use with only a few keystrokes. The hardest part is creating your block of formatted text - which you have to do anyway. Save it as an AutoText entry and you’re Ready to Rumble™ to use it again and again.

In the environment I am working, we use MS Word - customized to within a hairsbreadth of its life. Across multiple code templates that are loaded when Word starts, document/code templates that are available only when a particular document type is open, and even docm files that are documents that contain code, there is close to 100K lines of VBA code. That's a lot of code to manage. 

As part of the management process, changes and/or updates are necessary. That's pretty much what we do, most of the time, and add new functionality when users dream up something new. All good. The issues I was running into was the time spent looking for a particular function or module that I could leverage as is, or repurpose with limited modifications. 

The search ability built into the Visual Basic Environment is limited to open code documents and templates. And, unlike OpenOffice code, Word's code is not simple text files that can be searched via really handy tools such as GREP. It looked like I had to roll my own. No problem. VBA contains a self-referential method to examine the code itself. What I did was open all the code templates/documents, extract the contents of all the modules' subs and functions, and built a single searchable Word document, color coded and styled to identify template, subs, functions and comments.

After the initial code development and ensuring it all worked, I put it all in a portable docm, slapped an interface on the front and created a few bells and whistles to make using it easier. Now, all I need to do is open the codeoutput.docm file, and double click the start button on the document to launch the options dialog, click the appropriate generate button, and get a fresh cup of coffee while it grinds through all my templates and code documents.

There are a few options that I can select as shown in the image below. You can identify folders of code templates to include, and individual code templates/files to exclude. Both of those processes are point and click using the "+" and "-" buttons. To add, click the "=" and use the folder/file picker to make your selection. To remove, select an item in the list and click "-".

Clicking the "Sub & Fcn List" button generates a three-column table list of all your subs and functions, and includes the first line past the name of the sub or function and saves the file as "Sub_Fcns<yyyymmdd>.docx" in the location where you've indicated. Why the first line past the name, you ask? I includedi t, since I usually put a comment here that indicates the purpose of the sub/function. All public subs/functions are highlighted. Snip below.

Clicking the "All Text" button generates the whole enchilada. It creates and saves the file as "Code<yyyymmdd>.docx" in the location you've indicated in the form. What I did after that is convert the document to a chm file, so I didn't have to open the document for searching if I was knee deep in Word code. Launch the .chm, and keep it open for reference.  

Each module is styled as Heading1 and each sub or function is styled as Heading2. That way, you can collapse the document to an outline and speed around if you want, and, if you convert it to a .chm file, the styles can become TOC entries. What it looks like is shown below. 

Click the "Save Settings" button to save the folders to include, files to exclude and file types for the next time you need it. 

If you want to download the docm that does it and modify it for your own purposes, click below and have at it. I'm sure many can improve it. The code has a digital signature verified by Verisign. I'm legit!