This wiki entry has been graciously submitted with the permission of Gerrit Bruijnes. '''''It's currently a work in progress, trying to maintain the essential content and flavor of the original version.'''''

+

This wiki entry has been graciously submitted with the permission of Gerrit Bruijnes.

A book on Scribus 1.4.1 and publishing, in Netherlands language (Dutch), by Gerrit Bruijnes, [http://www.ipaa.nl www.ipaa.nl]

+

−

+

−

''Assumptions:'' You’re proficient in the operating system that you use. You use Scribus 1.4.1 (language: English – British) and you are familiar with this program at a reasonable advanced level. We do not explain here at length how to perform common tasks such as defining a new document, typing text in a text frame and applying properties, drawing lines, using the properties box and so on. If, on the other hand, you’re an experienced programmer you may find this article rather verbose.

+

−

+

−

'''PDF forms - Contents'''

+

−

* PDF-tools

+

−

* Design

+

−

* JavaScript

+

−

* Add pdf-controls

+

−

* Events

+

−

* Button with button face

+

−

* Setup Fields

+

−

* Add program snippets

+

−

* Programming terms

+

−

* Calculations in a form

+

−

* Test the form

+

−

* Form results

+

+

A book on Scribus 1.4.1...1.4.3 and publishing, in Netherlands language (Dutch), by Gerrit Bruijnes, [http://www.ipaa.nl www.ipaa.nl]<br>''Some editing has been done to modify the source Scribus file for consistent English language content, so that new screenshots could be obtained.''

+

{| style="background:#dde2ff" |

+

|-

+

|''Assumptions:'' You are proficient in the operating system that you use. You use Scribus 1.4.1...1.4.3 (language: English) and you are familiar with this program at a reasonable advanced level. We do not explain here at length how to perform common tasks such as defining a new document, typing text in a text frame and applying properties, drawing lines, using the properties box and so on.<br>If, on the other hand, you’re an experienced programmer, you may find this article rather verbose.

+

|}

===PDF forms===

===PDF forms===

PDF forms are designed so that a user, viewing them online or locally on a computer, can add data to a form, after which the user may print it or return it to you by e-mail.

PDF forms are designed so that a user, viewing them online or locally on a computer, can add data to a form, after which the user may print it or return it to you by e-mail.

Line 121:

Line 108:

Now take the time to let the next sentence sink in:

Now take the time to let the next sentence sink in:

−

''If no programming is connected to an event, then nothing will happen when the event occurs. If a program is connected to an event, then it will be executed every time the event takes place!''

+

<blockquote>''If no programming is connected to an event, then nothing will happen when the event occurs. If a program is connected to an event, then it will be executed every time the event takes place!''</blockquote>

In our form we will add a button that will print the form when the user clicks the button. We will use the mouse down event (the mouse button is clicked when the mouse pointer is positioned over the button) to program the fragment that will execute this task. If the user was to click the button let’s say ten times, the form would be printed ten times. This programming method is called event-driven programming. All currently available operating systems for computers such as Apple OS X, OS/2, Linux, Windows and others, are constructed around this principle. You’re already used to working with it, now you will acquaint yourself with the backside of this technique and program it yourself.

In our form we will add a button that will print the form when the user clicks the button. We will use the mouse down event (the mouse button is clicked when the mouse pointer is positioned over the button) to program the fragment that will execute this task. If the user was to click the button let’s say ten times, the form would be printed ten times. This programming method is called event-driven programming. All currently available operating systems for computers such as Apple OS X, OS/2, Linux, Windows and others, are constructed around this principle. You’re already used to working with it, now you will acquaint yourself with the backside of this technique and program it yourself.

Line 144:

Line 131:

===Icon on a button===

===Icon on a button===

Buttons can be enhanced with a little image on them. We call this an icon. Alternatively you might just add a short text to the button face. Adding text to a button in Scribus is comparable to adding text to a text field. An icon for a button is also quite doable.

Buttons can be enhanced with a little image on them. We call this an icon. Alternatively you might just add a short text to the button face. Adding text to a button in Scribus is comparable to adding text to a text field. An icon for a button is also quite doable.

−

# Use a drawing program. The images in this example were made using Windows’ Paint (Dutch version).

+

# Use a drawing program, such as Windows’ Paint (Dutch version) &ndash; ''used for the author's book example''.

# Define the canvas (size of the drawing) which should fit the size of the button. It doesn’t need to be very big, 200 x 100 pixels should be more than sufficient. You may find this in any program under Properties in the menu File.

# Define the canvas (size of the drawing) which should fit the size of the button. It doesn’t need to be very big, 200 x 100 pixels should be more than sufficient. You may find this in any program under Properties in the menu File.

# A drawing program will allow you to add text, use a font like Wingdings or Symbol to add special signs such as a computer keyboard, an arrow and an envelope.

# A drawing program will allow you to add text, use a font like Wingdings or Symbol to add special signs such as a computer keyboard, an arrow and an envelope.

Line 177:

Line 164:

{| border=0 style="background:#DDE2FF" |

{| border=0 style="background:#DDE2FF" |

|-

|-

−

|Names assigned to fields enable us at ‘the backside’ of the form to perform certain tasks through program snippets. The user’s side, ‘the front’ and programmer’s side, ‘the back’ of the form need not look the same.

+

| colspan="4" |Names assigned to fields enable us at ‘the backside’ of the form to perform certain tasks through program snippets. The user’s side, ‘the front’ and programmer’s side, ‘the back’ of the form need not look the same.

In practice generic names are cumbersome, because they are also used to present the results of a form when it is send by e-mail. It’s much nicer to receive a result that looks like this:

In practice generic names are cumbersome, because they are also used to present the results of a form when it is send by e-mail. It’s much nicer to receive a result that looks like this:

−

|}

−

{| border=0 style="background:#dde2ff; width:100%" |

|-

|-

| width=100px |

| width=100px |

Line 207:

Line 192:

|ON

|ON

|

|

−

|}

−

{| style="background:#dde2ff; width:100%" |

|-

|-

−

|A much less clear result with generic names would look like this:

+

| colspan="4" |A much less clear result with generic names would look like this:

|

|

−

|}

−

{| style="background:#dde2ff; width:100%" |

|-

|-

| width=100px |

| width=100px |

Line 229:

Line 210:

|ON

|ON

|

|

−

|}

−

{| style=background:#dde2ff; width:100%" |

|-

|-

−

|Naming can be in a language that differs from the language used in the form, because the results may be processed by employees who, in this case, do not speak English. Anyway, it is not necessary and you may use anything you want.

+

| colspan="4" |Naming can be in a language that differs from the language used in the form, because the results may be processed by employees who, in this case, do not speak English. Anyway, it is not necessary and you may use anything you want.

Programmers often use a different type of naming, the so called Hungarian Notation. The type of object is mentioned in the name (we call a field an object or control). In this case English is the predominant language and names would look like this:

Programmers often use a different type of naming, the so called Hungarian Notation. The type of object is mentioned in the name (we call a field an object or control). In this case English is the predominant language and names would look like this:

−

|}

−

{| style="background:#dde2ff; width:100%" |

|-

|-

| width=100px|

| width=100px|

Line 248:

Line 225:

|btnPrintForm

|btnPrintForm

|

|

−

|}

−

{| style="background:#dde2ff; width:100%" |

|-

|-

−

|The prefix '''chk''' makes it immediately clear that we are dealing with a check box, '''txt''' would denote a textfield, and '''btn''' refers to a button.

+

| colspan="4" |The prefix '''chk''' makes it immediately clear that we are dealing with a check box, '''txt''' would denote a textfield, and '''btn''' refers to a button.

|}

|}

Line 314:

Line 289:

* If you can’t get it to work, [[File:PDF_form_-_completed.sla.gz | this form]] is a fully-fledged version so you can still check out how it works.

* If you can’t get it to work, [[File:PDF_form_-_completed.sla.gz | this form]] is a fully-fledged version so you can still check out how it works.

===The check boxes===

===The check boxes===

−

First we’re going to fix the check boxes. Most teachers are females so that’s we tick off the check box F (see previous table).

+

First we’re going to fix the check boxes. Most teachers are females so that’s why we tick off the check box F (see previous table).

* Double click check box M.

* Double click check box M.

* Select the tab Action in the dialog box Properties.

* Select the tab Action in the dialog box Properties.

Line 341:

Line 316:

{| style="background:#dde2ff" |

{| style="background:#dde2ff" |

|-

|-

−

|The meaning of the abbreviation var is variable. A variable is a random name, by using this name we can refer to something. In the code snippets above, it refers to the fields with the names M and F respectively. These are the fields we have placed in the form right next to the text fields M(ale) and F(emale). Value is a property of an object. The object is the field. Every object has properties, like in real life where for instance a car possesses a property Color and a property NumberOfDoors. While programming, properties can always be read an often set as well.

+

|The meaning of the abbreviation '''var''' is variable. A variable is a random name, by using this name we can refer to something. In the code snippets above, it refers to the fields with the names M and F respectively. These are the fields we have placed in the form right next to the text fields M(ale) and F(emale). Value is a property of an object. The object is the field. Every object has properties, like in real life where for instance a car possesses a property Color and a property NumberOfDoors. While programming, properties can always be read an often set as well.

|-

|-

|An event occurs when something happens like clicking with the mouse on a button or moving the mouse over an object such as a text field or a check box.

|An event occurs when something happens like clicking with the mouse on a button or moving the mouse over an object such as a text field or a check box.

Line 347:

Line 322:

|''Note that the variable v shows that the name of the variable in JavaScript doesn't have to match the field name.''

|''Note that the variable v shows that the name of the variable in JavaScript doesn't have to match the field name.''

|}

|}

+

===Code snippets for the combo box===

===Code snippets for the combo box===

The combo box utilizes two programming fragments. One is active when the user clicks the box and supplies the box with the list of possible courses, thus presenting a number of choices . We ought to do this at the time the form is loaded into the PDF reader, but this outside the scope of this article, so we do it this way.

The combo box utilizes two programming fragments. One is active when the user clicks the box and supplies the box with the list of possible courses, thus presenting a number of choices . We ought to do this at the time the form is loaded into the PDF reader, but this outside the scope of this article, so we do it this way.

Line 360:

Line 336:

f.setItems( ["Choose course!", "Basic", "Intermediate", "Advanced"]);

f.setItems( ["Choose course!", "Basic", "Intermediate", "Advanced"]);

</pre>

</pre>

−

It is possible to change the settings of a field using programming code. Here we deny the user the possibility to fill in a non-existing training (f.editable = false;) It ís possible to allow this, but in that case the whole thing gets a lot more complicated, because we would also have to check the supplied user info. Spelling check is also disabled because we will add the correct names of trainings ourselves.

+

It is possible to prevent a change in the settings of a field using programming code. Here we deny the user the possibility to fill in a non-existing training (f.editable = false;). If we allowed editing, the whole thing gets a lot more complicated, because we would also have to check the supplied user info. Spelling check is also disabled because we will add the correct names of trainings ourselves.

−

The combo box will be filled with four possibilities, the first being Choose course! It cues the user into what information is required. The other three entries describe the available courses. You can add as many as you want, but then you will have to adjust the following code snippet!

+

The combo box will be filled with four possibilities, the first being '''Choose course!''' It cues the user as to what information is required. The other three entries describe the available courses &ndash; you can add as many as you want, but then you will have to adjust the following code snippet!

* Choose Save and Exit in the editor’s File menu.

* Choose Save and Exit in the editor’s File menu.

* Select the next event, Event: On blur (this denotes the clicking with the mouse in the box or using the Tab key to hop the cursor into the combo box). Copy this fragment:

* Select the next event, Event: On blur (this denotes the clicking with the mouse in the box or using the Tab key to hop the cursor into the combo box). Copy this fragment:

Line 369:

Line 345:

var c = this.getField("Cost");

var c = this.getField("Cost");

switch (t.value){

switch (t.value){

−

case 'Basic': {

+

case 'Basic': {

−

c.value=250;

+

c.value=250;

−

}

+

}

−

break;

+

break;

−

case 'Intermediate': {

+

case 'Intermediate': {

−

c.value=275;

+

c.value=275;

−

}

+

}

−

break;

+

break;

−

case 'Advanced': {

+

case 'Advanced': {

−

c.value=325;

+

c.value=325;

−

}

+

}

−

break;

+

break;

−

default: {

+

default: {

−

c.value=0;

+

c.value=0;

−

}

+

}

}

}

</pre>

</pre>

−

Variable c refers here to the text field with the name Cost. Depending on the choice that was made in the combo box, an amount is written to this field. There is a default , 0 (zero) , which is valid as long as no choice has been made.

+

Variable '''c''' refers here to the text field with the name Cost. Depending on the choice that was made in the combo box, an amount is written to this field. There is a default , 0 (zero) , which is valid as long as no choice has been made.

+

===Calculations===

===Calculations===

There is one thing left to take care of. It’s the calculation needed to multiply the number of participants with the cost of the course.

There is one thing left to take care of. It’s the calculation needed to multiply the number of participants with the cost of the course.

Line 429:

Line 406:

|Color

|Color

|Output Intended For:

|Output Intended For:

−

|Screen/Web

+

|Screen / Web

|}

|}

* Now click the button Save.

* Now click the button Save.

Line 461:

Line 438:

|Normally all fields will be printed one after another. In the previous image we have put them each on their own line for clarity. They are given in the same order as they were placed on the form. If you have used a different order, then this will be reflected in the result. This should not present a very big problem because the fieldnames have also been added to the file, all the more a good reason to name your fields with care and not use the standard names.

|Normally all fields will be printed one after another. In the previous image we have put them each on their own line for clarity. They are given in the same order as they were placed on the form. If you have used a different order, then this will be reflected in the result. This should not present a very big problem because the fieldnames have also been added to the file, all the more a good reason to name your fields with care and not use the standard names.

|-

|-

−

|[[File:Props_level.png | center]]

+

|[[File:Props_level.png | center ]]

|-

|-

−

|The order of the fields can be changed in the Scribus’ environment. Use the Properties box and on the tab X, Y, Z you can change the order with the button Levels. Upon selecting a field you will see the field’s rotating number. The field’s name can also be found on this tab at the top ánd can be changed here as well!

+

|The order of the fields can be changed in the Scribus’ environment. Use the Properties box and on the tab X, Y, Z you can change the order with the button Levels. Upon selecting a field you will see the field’s rotating number. The field’s name can also be found on this tab at the top ánd can be changed here as well!<br>''Note: This may not be true. It appears from the above example that the order relates to an alphabetical listing based on the field name. For instance, the Name variable was at Level 1 in the Scribus document.''

A book on Scribus 1.4.1...1.4.3 and publishing, in Netherlands language (Dutch), by Gerrit Bruijnes, www.ipaa.nlSome editing has been done to modify the source Scribus file for consistent English language content, so that new screenshots could be obtained.

Assumptions: You are proficient in the operating system that you use. You use Scribus 1.4.1...1.4.3 (language: English) and you are familiar with this program at a reasonable advanced level. We do not explain here at length how to perform common tasks such as defining a new document, typing text in a text frame and applying properties, drawing lines, using the properties box and so on.If, on the other hand, you’re an experienced programmer, you may find this article rather verbose.

PDF forms

PDF forms are designed so that a user, viewing them online or locally on a computer, can add data to a form, after which the user may print it or return it to you by e-mail.

What does a PDF form consist of?

Since it is at bottom a PDF, you can add anything you like to it: text, images, shapes, in short anything that Scribus has to offer. If you are going to make a PDF form, you must also learn how to use the special PDF Tools. You will find them in the PDF-toolbar. From left to right we see:

PDF-Button – A button is used to trigger some action. In the example that we’ll make shortly, we will create two buttons: one to print the form and one to send it as an e-mail. A button can be enhanced with a button face which we call ‘icon’. An individual button may use up to three different icons, which enable us to show a button-press-effect and even an icon that is shown when the mouse moves over the button.

Text Field – A text field is comparable to a text frame, but with the possibility to use numbers, think of numbers that are represented as dates or that a have a particular number of decimals or which are shown as a percentage.

Check Box – A familiar little box that shows a tick mark [×] when we click it. In our example we’ll use this box to denote a male or a female applicant for a course.

Combo Box – A combo box is a drop-down list with choices presented in a folded-in form. The user opens the list to make a choice.

List Box – A list box is also used to present choices, but in this case at least some elements from the list are always visible. The user can scroll the list, but does not have to open it first.

Text Annotation – This is a text field with notes. An annotation is in principle not visible in the pdf-form. You cannot only use it to add text to the form but also links to locations elsewhere in the document or to websites on the internet.

Link Annotation – Also used for links to locations in the document in which case even the exact coordinates can be used in point, according to the measurement systems used in Scribus. Also links to external websites can be used.

How do we go about making a PDF form?

When designing a PDF form, we need to consider these features:

A lay-out – Try to design your form in advance. You can add text frames, tables, images and shapes, in short anything that Scribus can produce. These items will be used to represent the house style which your company or organization uses. Furthermore it will be necessary to show on the form what information is expected from the user.

PDF fields – You will have to use the available fields that Scribus has to offer, and as you have seen there are several types. Keep in mind that not everything has been implemented yet in Scribus 1.4.1! It’s an ongoing development effort.

Set up – You will have to familiarize yourself with the many possible tweaks for the fields. You can set up the fields in several dialog boxes. There are many possibilities, but not all are functioning properly yet.

Validations – It is possible to set limits for entries made in a field. For instance you may restrict input of a number to certain boundaries, something which we do in this example.

Calculations – In a dialog you can set up a certain calculation for a field. Possibilities are adding the contents of two or more fields or multiplication and so on. It is possible to have highest or lowest values calculated of even an average of the values in a great many fields. Other more complicated calculations are also possible but that requires more significant programming.

Programming – If you want to add intelligence to your form, you will have to familiarize yourself with programming in JavaScript. This is a programming language not only used in PDF-forms but also on websites. If you have never programmed before, expect to take some months to become somewhat proficient. The next box will present you with some hints and tips where to find more information on JavaScript.

JavaScript

Java is a programming language which was marketed in 1995 by Sun Microsystems. The responsible developers, James Gosling, Mike Sheridan and Patrick Naughton spent about four years to develop the language. The story goes that the gents drank a lot of coffee, something you are bound to do when you take up programming! The coffee brand came from the island of Java, hence the name of the programming language and the Java icon showing a styled coffee cup.

JavaScript took many conventions and naming definitions from Java but yet has a different set up. Originally the language was used on the client side in browsers. If you surf the internet and have a peek at a page that the server offers you, you are the client. The language was developed in 1995 by Brendan Finch who worked for Netscape. This company designed a well-known browser that has given Microsoft’s Internet Explorer tough competition for a considerable time.

JavaScript for Acrobat

The software company Adobe laid out the PDF standard. You will probably find Acrobat Reader on your PC, since it is a reader for PDF documents and used worldwide. Therefore it is no surprise that this company goes at great lengths to explain how JavaScript is utilized best in PDF-forms. You can find many examples and tutorials at this website:

It is somewhat challenging to find out how much Scribus 1.4.1 “understands” as far as JavaScript and forms is concerned. You can find some examples in the wiki, unfortunately not all of them are working correctly or are not fully explained. Let’s say everybody tries hard. Here you’ll find more about Scribus and JavaScript in pdf-forms:

The PDF Form

The next image shows the form that we’re going to build step by step, as it appears in Scribus. The red circles are simply markers to denote the following form elements.

Everything else, such as the header and the lines are regular Scribus objects. There are also some simple text frames – those with M and F, Cost (euro), Nr attending, and Totals (euro) are simply labels for the adjacent form elements.

Text fields

Check Boxes

Combo Box

Annotation field

Buttons

Below we see the form as it appears in Adobe Reader. Except for the buttons, the light blue shows the areas where some input can be entered in the form. The word Name is a default entry that also indicates the type of input, so you would delete that and enter your name to fill out this form.

It’s important that you realize that while the design of a form is done in Scribus, it cannot be tested in this environment! In other words, all the form elements are nonfunctional in Scribus. So every time you have taken a step in the design process and you want to check if it works, you will have to take the following steps:

Save the form in Scribus as .sla-file.

Export the form in the PDF format.

Find the resulting PDF file and open it in Adobe Reader.

Test the form.

If you find any mistakes or want to continue the design, you close Adobe Reader and return to the Scribus environment.

Make changes or expand the form.

Save it again in Scribus, export the PDF and overwrite the previous PDF version! This may seem an obvious thing to do but in reality it is often forgotten, thus leading to many different versions and absolute confusion on your part as you try to figure out which is the “true” final version.

Repeat these steps as often as necessary until the form performs exactly as you envisioned. With some experience you will become comfortable with the various form elements, and not find it necessary to recheck the PDF after every change.

Layout

For our example we will make an imaginary enrollment form for a particular type of training for teachers of English as a foreign language (EFL), who want to qualify in a certain methodology.

Prepare a new document A4 size. (US Letter is similar.)

We need some text frames. At the top the name of the institute is placed. Colors will be applied later. We will take the color from the color in the button face. We will design our own icon for the buttons, using a simply drawing program such as Paint (if you run Windows).

In the lower left hand corner we will use two small text frames that will read M(ale) and F(emale).

On the right we find three text frames with the texts ‘Cost (euros)’, ‘Nr attending’ and ‘Totals (euro)’. Height of the frames is 5,5 mm approx., font is Arial, 12 pt and anything similar. (The examples here on the wiki created on Linux use DejaVu Sans Condensed.)

We’ll lower the text in the frames a wee bit, it gives a better look. Click in the Properties box under Text on Columns & text distances and apply 1 mm spacing above (the Top setting).

Two thick lines are added. The results so far are shown in the next image. The positions of the guides are not so important, an estimate will do. Note that their main purpose is to help align various objects and create some balance of the layout.

Adding PDF form elements

The next step will be to add the PDF form elements – seven text fields, two check boxes, one combo box and two buttons. Each has its own method:

Text field – The person using the form can fill in information in a text field. In this example we will add default text, showing the user which information is expected. In the next image you’ll see two completed text fields on the left and one that still has to be filled with a suitable text. You may type text directly into the text fields, just as you are used to with regular text frames. Select a text field and click on the button Frame Contents or use the Story editor.

Check boxes – There are two fields that can be filled with a tick mark. We use them to denote the sex. It is hard to be a woman and a man at the same time, therefore the form should only allow for one tick mark in one of the boxes. With a small piece of programming we will make sure that a tick in one of the boxes removes the tick mark from the other box. In some other situations, we might have a list of non-exclusive options that a user could choose from, and since there would be more than one choice to make, we wouldn't need this restrictive programming.

Combo box – We will fill the combo box with a number of training options. The filling of the box will be performed momentarily by a little program when the user clicks the box. Once a choice has been made to enlist in a particular training, the cost will be filled in one of the text fields. This also requires a bit of programming. The way we will do it here, a result will be entered only when the user clicks in another field. We will force the user to do so by filling in zero for the number of applicants. The user will have to change that and thus the program will be executed; check the next box titled ‘Events’.There are other ways of doing this, but they lay outside the scope of this introduction into programming pdf-forms .

Buttons – By clicking a button one can initiate an action. As an experience software user you are accustomed to this. The most well-known button that we all use daily is the OK-button. Scribus also allows us to add such a button to a form. Behind the button for printing the form we find a program snippet that performs this action for us. The button to send the form does not need any programming because this action can be set in a dialog box.

Events

Clicking a button or clicking in a text field is an event. Also if you fill in something in a text field, or if you make a choice in a list box or a combo box and consequently click in another field, we call this an event. An event is connected to a text field, a button or any other control in a PDF form. Every event that is detectable, offers the possibility to add a program snippet to it.

Now take the time to let the next sentence sink in:

If no programming is connected to an event, then nothing will happen when the event occurs. If a program is connected to an event, then it will be executed every time the event takes place!

In our form we will add a button that will print the form when the user clicks the button. We will use the mouse down event (the mouse button is clicked when the mouse pointer is positioned over the button) to program the fragment that will execute this task. If the user was to click the button let’s say ten times, the form would be printed ten times. This programming method is called event-driven programming. All currently available operating systems for computers such as Apple OS X, OS/2, Linux, Windows and others, are constructed around this principle. You’re already used to working with it, now you will acquaint yourself with the backside of this technique and program it yourself.

Copy this field three times (Windows: Ctrl + C and then Ctrl + V). Position the copies neatly below one another.Note that you might also use Item > Multiple Duplicate for a task like this, either by making a series of copies with a certain vertical spacing, or creating a number of rows, with your set spacing.

Click in the first text field and choose in the popup menu Edit text… The next image just shows this for the field that will have to contain the postal code.

The Story editor is opened, type the text, then choose Edit text and close in the File menu. The text will appear in the text field.

Repeat this procedure to add the following texts to the next four fields: Name, Address, Postal code and City.

Draw two square check boxes next to the text frames that read M and F respectively.

On the right hand side of the form we need the following pdf controls:

On top a combo box.

Three text fields below the combo box, to the right of the three already present text frames.

Below this group you draw two buttons.

The next image shows you what it should look like so far. Note that the selected frame (outlined in red) is not mentioned above, but is a Text Annotation frame.

Icon on a button

Buttons can be enhanced with a little image on them. We call this an icon. Alternatively you might just add a short text to the button face. Adding text to a button in Scribus is comparable to adding text to a text field. An icon for a button is also quite doable.

Use a drawing program, such as Windows’ Paint (Dutch version) – used for the author's book example.

Define the canvas (size of the drawing) which should fit the size of the button. It doesn’t need to be very big, 200 x 100 pixels should be more than sufficient. You may find this in any program under Properties in the menu File.

A drawing program will allow you to add text, use a font like Wingdings or Symbol to add special signs such as a computer keyboard, an arrow and an envelope.

Add some background color and a few thick lines in a slightly darker shade will add a sense of a shadow effect.

Save the button face drawing and switch to Scribus.

The actual graphic you see above was created entirely in Scribus, using Dingbats font, grabbed with a screenshot program, then saved as a PNG to be used for the form. There were actually 3 frames here, in the front a text frame with no background color and the symbols, underneath an empty copy of the text frame with orange background, and in between a small frame with a white background so the envelope would be white. So as you can see, Scribus qualifies also as a “drawing program”

Set up fields

The next task that awaits us is to set up all fields through the dialog box Field Properties. Let’s start with the one of the buttons.

Double click the button on the right. The dialog box Field Properties will be opened.

Assign a name to the field. If you skip that all controls on the form will receive a generic name consisting of the type of field and a number. It’s not very clear. Rather go to the tab Appearance and assign a name that clearly states the purpose of the field behind Name.

At Visibility we choose No Print. After all, if the user decides to print the form it will not be necessary to print the buttons now, will it?

Select the tab Options and click the button Normal.

The dialog box Open will be opened and you select the button face (icon) that you have just prepared.

Take into account that you can use up to three icons: Normal (what is visible most of the time), Pressed (what is visible when the button is clicked) and Roll over (visible when the mouse pointer hovers over the button. In this example we stick to just one icon.

Click the tab Action and select at Type: Submit form.

Type the url in the box Submit to url:. The image below to the right shows how an e-mail address is used. Adobe Acrobat Reader will try to open a mail client on the user’s computer. If this fails a dialog with choices will be shown.

The button’s set up is complete now.

The left button, which deals with printing of the form, can be enhanced with an icon in the same way. We just used the Story editor here to add a text; see the next images.

If you use a background color for the button that e-mails the form results just like we did, you may use Scribus’ Pipet tool to add this color to the document’s colors and use it to enhance the form’s title and the two lines that we added earlier.

Naming Conventions

Names assigned to fields enable us at ‘the backside’ of the form to perform certain tasks through program snippets. The user’s side, ‘the front’ and programmer’s side, ‘the back’ of the form need not look the same.

In practice generic names are cumbersome, because they are also used to present the results of a form when it is send by e-mail. It’s much nicer to receive a result that looks like this:

Name

G. Bruijnes

Address

Langstraat 6

Postal code

1234 AA

City

Stadje

Female

ON

A much less clear result with generic names would look like this:

Text22

G. Bruijnes

Text37

Langstraat 6

Text42

ON

Naming can be in a language that differs from the language used in the form, because the results may be processed by employees who, in this case, do not speak English. Anyway, it is not necessary and you may use anything you want.

Programmers often use a different type of naming, the so called Hungarian Notation. The type of object is mentioned in the name (we call a field an object or control). In this case English is the predominant language and names would look like this:

chkFemale

txtAcqAddress

btnPrintForm

The prefix chk makes it immediately clear that we are dealing with a check box, txt would denote a textfield, and btn refers to a button.

Set up other fields

You know now that you can set up the fields by double clicking them in order to make choices in the dialog box Field properties. The next table gives you all necessary information:

Remarks

When defining the field NrAt you will see that we use a validation. This means that as long as the number 0 (zero), the form is considered to be not completed correctly. Thus we force the user to fill in a number equals to or larger than 1. By doing so the price of the training selected in the combo box will be processed in the text field Cost.

Check out the other possible links in the Annotation field. You’ll see that it is also possible to refer to particular locations inside the document. This completes the setup of the fields.

Adding programming (code snippets)

As I have explained before we use JavaScript to automate certain events. There is no need for you to have any specific programming experience to be able to understand the code snippets that we use here. If you want to make more pdf forms yourself, there will be no escape, you’ll have to foot it and learn the language, not meaning English here!

Remember:

A correct working piece of programming can only be obtained by using all kinds of special characters which very often have a special meaning. Every semicolon (;) and every equals sign (=) is essential. Sometimes even a space can make the difference!

Copy all examples in exactly the same way, maintain the same lay-out.

JavaScript uses braces abundantly. Use the right type { (open) or } (close) in the correct spot.

Check your code snippets on correct spelling of the words. One misplaced letter and the fragment will not perform its task without any warning.

The check boxes

First we’re going to fix the check boxes. Most teachers are females so that’s why we tick off the check box F (see previous table).

Double click check box M.

Select the tab Action in the dialog box Properties.

Choose Type: JavaScript.

Choose Event: Mouse up.

Click the button Edit.

Copy the following code snippet:

var v = this.getField("F");
v.value="Off";

How to interpret this? The snippet is located in the Mouse up event of the check box M. So if some clicks here as a result a tick mark will be placed in the box. This means however that the standard tick mark in checkbox F must be removed. In the code snippet we first point to the field F. Once we have established this, we can turn its value “Off”.

If you’re done, you chose File > Save and Exit… in the Editor’s menu.

Now you will see the code snippet in the dialog box.

Click the OK button in the Field Properties dialog.

Double click check box F.

Select the tab Action and add the same set up as you did with check box M.

The code snippet is comparable, but a little bit different. A user may make a mistake or change his mind so we also have to be able to remove the tick mark from check box M:

var m = this.getField("M");
m.value="Off";

Programming terms

The meaning of the abbreviation var is variable. A variable is a random name, by using this name we can refer to something. In the code snippets above, it refers to the fields with the names M and F respectively. These are the fields we have placed in the form right next to the text fields M(ale) and F(emale). Value is a property of an object. The object is the field. Every object has properties, like in real life where for instance a car possesses a property Color and a property NumberOfDoors. While programming, properties can always be read an often set as well.

An event occurs when something happens like clicking with the mouse on a button or moving the mouse over an object such as a text field or a check box.

Note that the variable v shows that the name of the variable in JavaScript doesn't have to match the field name.

Code snippets for the combo box

The combo box utilizes two programming fragments. One is active when the user clicks the box and supplies the box with the list of possible courses, thus presenting a number of choices . We ought to do this at the time the form is loaded into the PDF reader, but this outside the scope of this article, so we do it this way.

It is possible to prevent a change in the settings of a field using programming code. Here we deny the user the possibility to fill in a non-existing training (f.editable = false;). If we allowed editing, the whole thing gets a lot more complicated, because we would also have to check the supplied user info. Spelling check is also disabled because we will add the correct names of trainings ourselves.

The combo box will be filled with four possibilities, the first being Choose course! It cues the user as to what information is required. The other three entries describe the available courses – you can add as many as you want, but then you will have to adjust the following code snippet!

Choose Save and Exit in the editor’s File menu.

Select the next event, Event: On blur (this denotes the clicking with the mouse in the box or using the Tab key to hop the cursor into the combo box). Copy this fragment:

Variable c refers here to the text field with the name Cost. Depending on the choice that was made in the combo box, an amount is written to this field. There is a default , 0 (zero) , which is valid as long as no choice has been made.

Calculations

There is one thing left to take care of. It’s the calculation needed to multiply the number of participants with the cost of the course.

Click the field behind the text frame reading ‘Totals’.

Select the tab Calculate.

Click the radio button Value is the and select product in the list.

Click the button Pick… and take care that the fields Cost and NrAt in the box on the right; see the next image.

Close all dialogs with OK.

Test the form

This is the moment of truth, let’s test the form. Here is an overview of the process:

Save your work in Scribus.

Export the file as a pdf.

Save the file again in Scribus so changes you made to the way Scribus export pdf’s will also be saved.

Find the pdf on disk and open it with Acrobat Reader or any other pdf reader.

Check if everything is working correctly.

If changes area required, close the pdf, make changes in the Scribus environment and repeat the above steps.

Let’s do it shall we?

First go to Scribus, open the menu File and choose Save.

Go back to the menu File and choose Export. Choose Save as PDF…

You only have to make changes on just a few tabs:

Tab

Change

Remark / setting

General

Output to File:

Use a name and a location that will make it easy for you to find the file afterwards.

Compatibility

At least PDF 1.4 (Acrobat 5)

Fonts

Fonts to embed

Click: Embed all

Color

Output Intended For:

Screen / Web

Now click the button Save.

Open Explorer (Windows) or any other appropriate file manager for the operating system that you use, e.g. Nautilus (Ubuntu) or Finder (Apple). Find the pdf and open it. You might just run Adobe Reader and open the file from it.It may be possible that the reader will display a warning. This warning is obvious, the form is capable of e-mailing data.

Check if everything is working as it is intended. Click the combo box, select a course. Also test the function of the Print form button.

If an e-mail client (e.g. Outlook for Windows) is installed, the form results will be processed directly. In case of an online mail service like Yahoo or Gmail, the pdf has to be saved first (only possible with Adobe Reader version 9 or higher) and then the results can be sent via e-mail.

When saving you can choose several file types:

.fdf

Adobe’s form file format, only the data in the fields is saved. In this case it is necessary that the receiver also has a copy of the original form. The data sent by e-mail will then be automatically added to the form.

.xfdf

The extended form file format. It is capable of showing more options.

.xml

A file format that is capable of showing data in the appropriate fields on a webpage.

.txt

In this case data is save as a simple text file that can be opened and read with any simply word processor or text editor available on your system.

Results

Here is what the results look like as an FDF file:

Form results

Normally all fields will be printed one after another. In the previous image we have put them each on their own line for clarity. They are given in the same order as they were placed on the form. If you have used a different order, then this will be reflected in the result. This should not present a very big problem because the fieldnames have also been added to the file, all the more a good reason to name your fields with care and not use the standard names.

The order of the fields can be changed in the Scribus’ environment. Use the Properties box and on the tab X, Y, Z you can change the order with the button Levels. Upon selecting a field you will see the field’s rotating number. The field’s name can also be found on this tab at the top ánd can be changed here as well!Note: This may not be true. It appears from the above example that the order relates to an alphabetical listing based on the field name. For instance, the Name variable was at Level 1 in the Scribus document.