<< 1 >>
Rating: 
Summary: Caution: Not a beginner's guide to postscript!
Review: I consider myself a hardcore programmer, but I have not programmed with postscript before. When my job required postscript options added to the printer drivers, I started with this book. I now believe it would have been better to start with a beginner's guide and a reference manual on postscript. This book is great if you are already programming in postscript and want to better your skills with it
Rating:
Summary: I didn't really need to know THAT much about PostScript!
Review: This is a book intended for those who want to write drivers and stuff. I'm not that guy. I just want to know enough about how it works to respond to needs as they arise.You know? Just because I want a web server on my machine doesn't mean I want to write an HTTP stack from scratch. I'll probably just find what works and adapt it to my purposes. Here's a specific example relative to PostScript: I needed to create an application for someone who wanted a custom driver that would print different state-related labels on their printed images. Did I run off to the Program Design book to figure out how to write it from scratch? No way, man. My advanced status within the cigarette consumption community requires continued proficiency through hourly breaks, thus making this sort of focused activity quite impossible. Instead I looked in other drivers that had what I wanted, then printed to file, viewed source, and then pulled the code out as I felt appropriate. Quick, relatively easy, and demonstratively slothful. Get this book if you want to learn how to write drivers. Better, get this book and display it prominently so others think you know how to write PostScript drivers. Just get this book. Hell, its worth the money.
Rating:
Summary: I didn't really need to know THAT much about PostScript!
Review: This is a book intended for those who want to write drivers and stuff. I'm not that guy. I just want to know enough about how it works to respond to needs as they arise. You know? Just because I want a web server on my machine doesn't mean I want to write an HTTP stack from scratch. I'll probably just find what works and adapt it to my purposes. Here's a specific example relative to PostScript: I needed to create an application for someone who wanted a custom driver that would print different state-related labels on their printed images. Did I run off to the Program Design book to figure out how to write it from scratch? No way, man. My advanced status within the cigarette consumption community requires continued proficiency through hourly breaks, thus making this sort of focused activity quite impossible. Instead I looked in other drivers that had what I wanted, then printed to file, viewed source, and then pulled the code out as I felt appropriate. Quick, relatively easy, and demonstratively slothful. Get this book if you want to learn how to write drivers. Better, get this book and display it prominently so others think you know how to write PostScript drivers. Just get this book. Hell, its worth the money.
<< 1 >>
| 
