RagTime divides opinions. Some give up after a few weeks because much of it seems too unfamiliar to them. Others approach learning and experimenting completely without prejudice. Then it increasingly happens that new solution paths open up. We would like to encourage the former to become a bit more familiar with the peculiarities of RagTime. To the latter, we simply wish further successful experiences.
With every book that is intended for learning and advancement, the first question that arises is: At what level do we begin? For the first steps, RagTime has a well-compiled manual available. In addition, introductory examples are provided. Therefore, we assume that you are familiar with the basic functions and have dealt with the training examples. With our book, we attempt a small balancing act: on the one hand, we give tips and useful hints to those who have not been working with RagTime for too long. On the other hand, we show experienced users what can be optimized and improved – or what is worth rediscovering.
RagTime runs on both Mac and Windows. The structure and functions of the program are the same on both platforms. Only some window and palette arrangements differ – usually only insignificantly. Of course, some keyboard shortcuts are also a bit different. But that's where the differences end. Therefore, we have refrained from duplicating all illustrations. We have done this only where there are marked differences. We designed the first chapter, which deals with the “organizational basics” of RagTime (Foyer, Inventory, help folder, etc.), using Windows screenshots, and the remaining chapters using screenshots of the Mac interface. In the appendix, the palettes and keyboard shortcuts for both platforms are listed separately. Since you can really create great work simplifications with keyboard shortcuts, this topic is described in more detail in the appendix B “Keyboard shortcuts”.
As everywhere: Completely without theoretical backgrounds, it usually remains trial and error in practice. Because one can sometimes err in theories as well, it should be interjected here that we are all too aware of our fallibility. Despite multiple checks, errors could have remained. And perhaps you will think of a more optimal solution for one or another task example than the one we have shown. In both cases, your feedback is very welcome. If generally useful hints result from this, we will publish them on the Pumera websites.
But back to the structure of the book: Especially in chapters that mainly deal with formulas, theoretical explanations are indispensable. Otherwise, we have tried to proceed as practically as possible. This has led to us essentially setting ourselves tasks. Tasks that we know from our practice or problems that repeatedly appear in the RagTime web forum. In doing so, the examples were prepared in such a way that they are easy to follow. Where it was appropriate from the topic, small “excursions” to RagTime program peculiarities were inserted. For example, on the topic of lines or on the topic of colors and reproduction.
The three main chapters describe tasks that can arise in a private school, a foundation, or a market research institute. We have always taken care in the selection of the questions that the solutions shown are transferable to as many areas of application as possible. For example, the topic of mail merge will certainly not only be important for a private school. Organizational charts and schematic drawings will exist almost everywhere, and infographics (so-called business graphics) are hardly significant only for a market research institute.
Precisely because we understand our book in such a way that it should invite testing in small sections, we have dispensed with complicated cross-references. Most examples are structured so that they are understandable in themselves. On the other hand, this means that there may be repetitions from chapter to chapter. Where cross-references are present, they are in most cases intended as a supplement to the topic – or as a suggestion to take up the indicated topic next.
We have excluded some areas of application. These include the connection to databases via «RagTime Connect» or the connection for architects (CAD programs). We have also deliberately left aside the link to system-native address book tools as well as the special geographic-statistical representations that become possible with «GeoInsight».
We have treated other things less extensively because there are already competent documents about them. This concerns above all the professional work with PDF documents. Otherwise, we understand the book as a kind of continuing story. Where, when and in what form this happens, we must still leave open. But that is also why we are grateful for any exchange with you as RagTime users. We look forward to correction notes, suggestions and all kinds of tips. Because although we have now – after more than 15 years of practical work with RagTime – dealt with RagTime particularly intensively for another two years: some things still remain hidden from us. And admittedly: some things still mysterious. Occasionally, we have also deliberately not chosen the direct path for a solution because we wanted to illustrate a certain solution possibility. We are therefore not hurt in our pride if you find a more optimal solution in one or another case.
…who have helped us in the preparation of this book. Numerous experienced RagTime users have helped us with their knowledge and good tips. Above all, we thank Jürgen Schell from RagTime for his hints and generally RagTime in Hilden for the benevolent accompaniment. A big thank you also to the team of Pumera Publishing for the almost boundless trust and endless patience. And finally, thanks to our life partners, who patiently endured and morally supported us especially in the intensive phase of completion.
Despite careful editing, errors can never be completely avoided. Publisher and authors are grateful to you for suggestions and hints.
Neither the publisher nor the authors assume any liability for the consequences that are due to incomplete or incorrect information in this book or to the use of the described software.
All images and logos used are the property of the authors, except for the logos of Pumera and RagTime. The hardware and software products treated in this book are almost all also registered trademarks or should be treated as such.
The photos Fig. 3.121/Fig. 3.122 show the sculpture “La grande bouffe” from the sculpture exhibition “BadRagartz 2006”
(Artists: Shimmy Schadegg, Gockhausen, and her workshop team).