e-
{NOTE: As of 5/16/2012, these instructions are a little out of date, but still quite
useful. Brent (the creator of the T3 software) has created an updated module program
called “eSword Scripture ToolTip Tool NT” -
For more information on how to use T4 -
The e-
This page is going to focus on only two important features of T3:
But understand this: T3 also can make
By the way -
If you’re interested in building these other modules, you’ll want to study the help materials at the download page for T3, which is right here.
Brent Hildebrand is the creator of this 8th Wonder of the World! And his download
page includes lots of help information, including a .pdf file, a powerpoint presentation,
sample .rtf files, and nice online instructions with graphics. Take the time to review
his materials -
The Visible Elements of T3
First, notice that there are two windows: the upper window is where all of the editing of text will occur; the lower window is where T3 reports ToolTipping results.
Secondly, you’ll also notice that the interface is similar to a word processor. T3
is basically a glorified word processor -
Third, on the editing bar, find the color button. T3 will use whatever color is currently active for new typing and editing. For the typical user, you’ll only use two colors: black for editing text, and forest green for ToolTipping. There is no need to use most of the other colors for the vast majority of T3 work.
Fourth, you’ll find the menu options across the menu bar -
Finally -
Using .rtf Files
You can try copying and pasting from your word processor directly into T3's upper editing window, but T3 will directly open Rich Text Format (.rtf) files.
Just about every word processor on the market can easily convert it’s unique code to .rtf. Here’s how:
1. Choose “Save As” instead of “Save” from the File menu
2. Change file type to “.rtf”
3. Name it something unique
4. Make sure you put it in a folder you’ll easily remember. I keep all of my .rtfs
that I’m currently working on right on the desktop in a folder called “eS Tools”.
Inside that folder is another called “Modules Under Construction” -
5. Once you’ve created your .rtf file, simply “Open” it in T3.
T3 Codes
This section is the hardest part of using T3. Study it carefully: it will reap rich dividends when understood and implemented!
[When kindly proofreading this chapter for me, Brent Hildebrand sent me this note
on 2/9/2010 -
CODES FOR BUILDING .TOPX MODULES
1. Building The Prefix
If you are going to build a .topx module with more than one chapter, you are going to want to utilize Brent’s “prefix codes.” At the top of the document, include this line:
#def prefix=A #2
In this code:
**“A” is whatever text you want to have in each chapter title of the eSword drop
down box. In this example, chapters will look like -
00.1-
00.2-
01-
02-
etc.
In practical application, this part of the code will not be used for most users.
In other words -
#def prefix=#2
**The “#” symbol calls for numbering of chapters to happen automagically. Brent has
designed this very nicely; if there are more than 9 chapters in the document, it
will automagically place a zero placeholder in all chapter numbers lower than 10.
That way, e-
**The number immediately following the second “#” symbol (in this example, “2”) tells
how many preliminary chapters there are prior to the text’s “Chapter One” -
Here is an example of building a .topx module with an Introduction, Copyright, Table of Contents. We are not interested in repeating any text at the beginning of the drop down box.
#def prefix=#3
This example will create three preliminary chapters (00.1, 00.2, & 00.3), to be followed by as many chapters as I want to include.
2. Setting Chapter Marks
T3 uses marks to automagically create chapter titles in e-
To set a mark on any given line, go to the menu: “Marks ?Set Mark” (or Ctrl+m). You’ll
see the mark at the beginning of the line (a division symbol outlined in red; NOTE
-
T3 will convert every section separated with that ✡? into it’s own chapter; and the line that has the ✡? beginning will become the entry for the eS drop down box. Here’s an example:
#def prefix=#3
✡?Introduction
blah, blah, blah
✡?Copyright Information
This file was originally copyrighted in 1417. It is now public domain.
✡?Table of Contents
1. Blah, Blah 1
2. Blah, Blah 2
3. Blah, Blah 3
4. Blah, Blah 4
✡?Blah, Blah 1
As much text of chapter 1 as there is -
✡?Blah, Blah 2
Chapter two text
✡?Blah, Blah 3
Chapter 3 text
✡?Blah, Blah 4
Chapter 4 text
When this text is converted to an e-
CODES FOR BUILDING .DEVX MODULES
1. Building the Prefix
If you are going to build a .devx module you’ll need to utilize Brent’s devotional “prefix codes.” There are 5 lines that go at the very beginning of the document:
#def description=
#def abbreviation=
#def comment=
#def version=
#def startday=
In this code:
#def description=
What comes after the “=” is what is displayed in the yellow popup box when the mouse hovers over the name tab in the Daily Devotional section of eSword.
#def abbreviation=
What comes after the “=” is the Tab Name of the Daily Devotional
#def comment=
What comes after the “=” is not visible in eSword and is for your use only
#def version=
What comes after the “=” is not visible in eSword and is for your use only
#def startday=
What comes after the “=” is the day before the day of the year the devotional will start. To start on January 1, use “0”. To start on February 1, use “31”. To start on March 1, use “59”, etc.
So, let's take a look at an example.
#def description=A year long devotional by Dr. David S. Thomason
#def abbreviation=D4
#def comment=second half of year needs some work
#def version=1
#def startday=0
In the above example,
The tab name for this devotional will simply be D4.
When the mouse hovers over the “D4” tab, the yellow popup banner will show “A year long devotional by Dr. David S. Thomason”
This devotional will begin on January 1 (which is the day after Day 0 in the year).
Comment and Version are for my use only! They will not be seen by any eS users.
2. Setting Chapter Marks
Marks are set identically as .topx modules; but each mark creates a different daily devotional. For a one year devotional module, you’ll need to create a file with 365 ✡? marks. Each ✡? will be followed by that day’s title on the same line as the mark. Then you will write the body of the daily devotional. Double space, and create the next day.
Example:
#def description=A year long devotional by Dr. David S. Thomason
#def abbreviation=D4
#def comment=second half of year needs some work
#def version=1
#def startday=0
✡?The Bible Stands
[...several paragraphs of devotional text....]
✡?The Christian Stands
[...several paragraphs of devotional text....]
✡?The Savior Stands
[...several paragraphs of devotional text....]
This will produce a .devx module called “D4” which will start on January 1. The entry for that day will be called “The Bible Stands.” January 2's entry will be “The Christian Stands,” and January 3's entry will be “The Savior Stands.” Of course, each day will have “[...several paragraphs of devotional text]”!
T3 Options
Make Sure You Understand These -
Under the "Options" menu you will find some helpful settings. Let's take a look at the Five most helpful optional settings you can use to "ToolTip" your document.
SEARCH THROUGH LINE BREAKS
T3 arrives with this option OFF (unchecked). For the most part, leave it off.
What this option does (if turned on) is take two lines of text, like this:
John 3:
16
and removes the "Line Break" -
When using this feature, you will find some weird formatting results (not T3's fault, but the document's fault!!).
If you formatted your text using your own word processor, you'll definintely want this setting OFF.
UNDERLINE TOOLTIPS
This feature comes ON (checked). eSword standard ToolTips are green and underlined. For the most part, this option should be left on (unless you want your ToolTips to be not underlined).
REMOVE BOOK REFERENCES {}
This feature comes OFF. Here is what Brent Hildebrand told me about this option (2/11/2010):
Remove Book References {}, is a very specialized option.... Suffice it to say, a lot of the work Shirley has done has references in for form of {COL 415.1}. COL being the book name abbreviation, 415 is the page number of the original printed work, and .1 being the first paragraph on the page. Turning on this option removes braces {}, and everything in between.
In other words, for the typical user, leave this feature OFF.
DOUBLE PASS
When working with multiple Scripture references, T3 will initially underline an entire block with just one line; a second (double pass) will make each individual reference underlined.
This option comes ON, and the typical user will use it exclusively in the ON position.
ARITHMATIC PROGRESSION
This option comes ON, and let's leave it on! This very cool option will connect a string of disconnected references and ToolTip them together. Example: it will take this string of verses:
John 3:16, 17, 18, 20
and make these ToolTipped references: Joh_3:16-
Nice, huh? T3 will even ToolTip across one chapter. Example: it will turn this
2Ti 3:16-
into this -
Really nice, huh?!!
Using T3 To Create a .topx Module
There are two basic methods for creating a .topx module using T3 (these names are mine, not Brents!):
"Cut and Paste" is probably a little easier to use for the beginner or computer novice; but once you learn how to do the "Whole File" method, it will be so much faster, you won't want to cut and paste ever again!
"Cut and Paste" Method
Here are the steps for "cutting and pasting" an eSword .topx module using T3.
1. Develop the text (see "Chapter 08 -
2. Open eSword. In e-
3. Select your word processor and open your first chapter (or the document that
contains the first chapter). “Highlight” the first chapter, and then “copy” it (Ctrl-
4. Select the Scripture Tooltip Tool. Inside the top window, "paste" (Ctrl-
[NOTE: if you are using this method, you will not have to use any of the T3 Codes discussed above....]
On the "options" menu confirm that the default "Highlight Color" is forest green. If not, select the appropriate grid. Go back to "options" and confirm that "Underline Tooltips" is set as default; if not, make it so.
At the bottom of the page, click "e-
If you need to make edits to the actual text, make sure you choose font color to be “black” before making text edits. If you have to run the ToolTip Tool again, make sure you choose “forest green” just prior to doing so.
PROBLEM: The tooltip tool occasionally makes mistakes -
So, it may be necessary to "clean up" after running T3. Make a careful scan of all of your ToolTipped references in the bottom window. Here's a note from the T3 Creator, Brent Hildebrand:
When you click the ToolTip function, the bottom window will show you all the references. The last digit, will be 1 or 0. 1 means it is a valid scripture reference. 0 means it sure looks like a scripture reference, but either the number of chapters or verses is not valid. While not foolproof, it is helpful for finding errors. (Personal email correspondence from 2/1/2010.)
You can double-
So once you’ve “tooltipped” a section, give it a careful scan, to make sure all of the tooltips are correct.
5. Take a look through the body of the text. You won't need to proofread again (the only text that is changed are Scripture references), but you will need to check that A) The Tooltips are correct; and B) paragraph white spaces are still intact. Once this formatting has been verified, "select all" and then "right click" for a menu. In that menu choose "Copy as RTF".
You are now ready to build the module in e-
Follow the above steps for every individual chapter in your .topx module.
The “Whole File” Method
This method is only slightly more complicated than the “Cut and Paste” method -
1. Develop the text (see "Chapter 08 -
2. Convert your developed text to .rtf by using your Word Processor “Save As” and “File type” features (see above notes for how to do so).
3. Open the e-
4. Insert all of the T3 “codes” and “marks” for your module (see above sections
on “T3 Codes” for a complete explanation -
5. Just prior to ToolTipping, confirm that the “text color box” is green. Then,
at the bottom of the page, click "e-
If you need to make edits to the actual text, make sure you choose font color to be “black” before making text edits. If you have to run the ToolTip Tool again, make sure you choose “forest green” just prior to doing so.
PROBLEM: The tooltip tool is not without it’s errors -
So, it may be necessary to "clean up" after running the tooltip tool. Make a careful scan of all of your tooltipped references in the bottom window. Here's a note from the Tooltip Creator, Brent Hildebrand:
When you click the ToolTip function, the bottom window will show you all the references. The last digit, will be 1 or 0. 1 means it is a valid scripture reference. 0 means it sure looks like a scripture reference, but either the number of chapters or verses is not valid. While not foolproof, it is helpful for finding errors. (Personal email correspondence from 2/1/2010.)
You can double-
So once you’ve “ToolTipped”, give it a careful scan, to make sure all of the ToolTips are correct.
6. Take a look through the body of the text. You won't need to proofread again (the only text that is changed are Scripture references), but you will need to check that A) The Tooltips are correct; and B) paragraph white spaces are still intact.
7. Once your “Whole File” is proofread and the layout is exactly how you want it,
you are ready to actually do the module build -
From the “Modules” menu, choose “Topics ➥? Save TOPX File”. Navigate to the folder
where you want to make your .topx module (most users will choose “C:\...\My Documents\e-
AuthorLastName, AuthorFirstName AuthorMiddleInitial. -
Examples
T3 will automatically append the “.topx” suffix to the end of the file.
8. Open eSword (close it first if it was already open, and then reopen it), and verify that your brand spanking new .topx module is available. Proofscan every chapter for proper formatting.
The hardest part about the “Whole File” method is the prefix codes. Once you’ve got that figured out, it really is “easy as pie.” Apple Crunch Pie, that is!! (mmmmmmmmmm!!)
Don't forget to upload the file to the internet for worldwide publication! See Chapter
"08 -
Using T3 To Create a .devx Module
This method is very similar to creating a .topx module using the “Whole File” method. Here are the basic steps:
1. Develop the text (see "Chapter 08 -
2. Convert your developed text to .rtf by using your Word Processor “Save As” and “File type” features (see above notes for how to do so).
3. Open the e-
4. Insert all of the T3 “codes” and “marks” for your module (see above sections
on “T3 Codes” for a complete explanation -
5. Just prior to ToolTipping, confirm that the “text color box” is green. Then,
at the bottom of the page, click "e-
If you need to make edits to the actual text, make sure you choose font color to be “black” before making text edits. If you have to run the ToolTip Tool again, make sure you choose “forest green” just prior to doing so.
PROBLEM: The tooltip tool is not without it’s errors -
So, it may be necessary to "clean up" after running the tooltip tool. Make a careful scan of all of your tooltipped references in the bottom window. Here's a note from the Tooltip Creator, Brent Hildebrand:
When you click the ToolTip function, the bottom window will show you all the references. The last digit, will be 1 or 0. 1 means it is a valid scripture reference. 0 means it sure looks like a scripture reference, but either the number of chapters or verses is not valid. While not foolproof, it is helpful for finding errors. (Personal email correspondence from 2/1/2010.)
You can double-
So once you’ve “tooltipped” a section, give it a careful scan, to make sure all of the tooltips are correct.
6. Take a look through the body of the text. You won't need to proofread again (the only text that is changed are Scripture references), but you will need to check that A) The Tooltips are correct; and B) paragraph white spaces are still intact.
7. Once your “Whole File” is proofread and the layout is exactly how you want it,
you are ready to actually do the module build -
From the “Modules” menu, choose “Devotional ➥? Save Devotional File”. Navigate to
“C:\Program Files\e-
AuthorLastName, AuthorFirstName AuthorMiddleInitial. -
Examples
T3 will automatically append the “.devx” suffix to the end of the file.
IMPORTANT NOTE: Windows Vista and 7 may not allow you to save a file directly to the “Program Files” folder. If this is an issue for you, here is a simple “Texas Two Step” to get around this:
1. Instead of saving the file to the “Program Files” folder, save it right to the desktop.
2. Open Windows Explorer and navigate to C:\Program Files\e-
3. Open eSword (close it first if it was already open, and then reopen it), and verify that your brand spanking new .devx module is available. Proofscan every chapter for proper formatting.
Congratulations! You’ve now created a devotional module! Make sure you read “Chapter
08 -