This book uses a set of icons to point out certain details in the text. While they are relatively self-explanatory, here is what each of these icons indicates:

The SolidWorks 2007 Bible is unique in its use of these two icons:

These icons point out and describe techniques and settings that are either recommended or not recommended for specific reasons. Best Practice is usually considered to be very conservative usage, where the stability of the parametrics and performance (a euphemism for rebuild speed) are the ultimate goals. These two aspects of SolidWorks models are usually weighed against modeling speed (how long it takes you to create the model).

Best Practice and Performance recommendations need to be taken seriously, but you should treat them as guidelines rather than as rules. When it comes right down to it, the only hard and fast rule about SolidWorks is that there are no hard and fast rules. In fact, I believe that the only reason to have rules in the first place is so that you know when you can break them. Parametric stability and modeling speed are not always the ultimate goals, and are often overridden when workaround techniques are used simply to accomplish a geometric goal.

Because not everyone models with the same goals in mind, a single set of rules can never apply for everyone. You must take the best practice suggestions and apply them to your situation using your own judgment.

My point of view while writing this book has been that of someone who is actually using the software, not of someone trying to sell ideas, nor of someone trying to make the software look good. I try to approach the software objectively as a tool, recognizing that complex tools are good at some things and not so good at others. Both kinds of information (good and not-so-good) are useful to the reader. Pointing out negatives in this context should not be construed as criticizing the SolidWorks software, but rather as preparing the reader for real-world use of the software. Any tool this complex is going to have imperfections. Hopefully some of my enthusiasm for the software also shows through and is to some extent contagious.

An important concept referred to frequently in SolidWorks is design intent. As a practical matter, I use the phrase design for change to further distinguish design intent from other design goals.

The reader needs to be familiar with some special terminology before continuing. In many cases, a SolidWorks vernacular or slang is used when the official terminology is either not descriptive enough or, as is sometimes the case, has multiple meanings. For example, the word shortcut has multiple meanings in the SolidWorks interface. It is used to describe right mouse button menus as well as hotkeys. As a result, I have chosen not to use the word shortcut and instead substitute the words RMB and hotkey.

I frequently use RMB to refer to Right Mouse Button menus, or other data that you access by clicking the right mouse button on an item. The word tree refers to the list of features in the FeatureManager. Also, command and option names are referred to using all initial capitals, even when SolidWorks does not use the same capitalization. For example, the setting Single Command Per Pick is listed in Tools

Differences are frequently found between the names of features on toolbars and the names in the menus or PropertyManager titles. In these cases, the differences are usually minor, and either name may be used.

Most functions in SolidWorks can work with either the object-action or the action-object scenarios. These are also called pre-select and select, respectively. For example, the Hole Wizard is one tool for which pre-selection is definitely recommended because a difference in functionality is seen between pre-selection and selection. The Fillet feature shows no difference between using pre-selection and selection. Most features allow pre-selection, and some functions, such as inserting a design table, require pre-selection. Although you cannot identify a single rule that covers all situations, most functions accept both.

Frequently in this book, I have suggested enhancement requests that the reader may want to make. This is because SolidWorks development is driven to a large extent by customer requests, and if a large number of users converge on a few issues, then those issues are more likely to be fixed or changed. Again, the enhancement request suggestions are not made to criticize the software, but to make it better. I hope that several of you will join me in submitting enhancement requests.

SolidWorks is an extremely powerful modeling tool, very likely with the best combination of power and accessibility on the MCAD market today. This book is meant to help you take advantage of its power in your work and even hobbyist applications. If I could impart only a single thought to all readers of this book, it would be that with a little curiosity and some imagination, you can begin to access the power of SolidWorks for geometry creation and virtual product prototyping. You should start with the assumption that there is a way to do what you are imagining, and that you should be open to using different techniques.

For AutoCAD users making the transition to SolidWorks, you should simply forget everything you know about AutoCAD, because most of it, except for the most general geometric concepts, will not apply to SolidWorks, and will often simply confuse you.

Whoever you are, I hope that you find insight deeper than simply "what does this button do?" in this book. I hope that you will find an intuition for thinking like the software. Jeff Ray of the SolidWorks Corporation has said that the goal is to make the software as "intuitive as a light switch." While most people will agree that they have some work left to achieve that particular goal, I believe that approaching the interface intuitively, rather than attempting to remember it all by rote, is the best method. Good luck to you all.