Book Image

RESS Essentials

Book Image

RESS Essentials

Overview of this book

RESS is a new methodology in the world of web design and development. It attempts to solve the problems that accompany the RWD (responsive web design) approach to web design. RESS is still in its infancy, but it is growing at an exponential rate. RESS Essentials shows you how to make server-side applications smarter and more aware of a visitor's environment limitations (device, screen size, and browser). This allows you to create faster and more reliable websites. Through this book, you will build a solid base of knowledge on RESS-related technologies, while the step-by-step tutorials will help you to create your own RESS system. This book is an introduction to RESS alchemy and gives you an incentive to build your own RESS lab. It will give you a broad overview of the multiple techniques used to code responsive websites in responsible ways. Beginning with an overview of RWD, you will learn the steps involved in setting up RWD for client-side development. You will then learn how to scale images using client- and server-side technology. By the end of this book, you will have learned about the implementation of RESS application patterns, browser feature detection, and various RESS architectures. RESS Essentials will also teach you how to use jQuery with some RWD design patterns and how to employ REST API for RWD pages.
Table of Contents (15 chapters)
RESS Essentials
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

What is it good for?


Some say that REST "will power the future of the Internet" (http://www.phparch.com/2012/02/what-will-power-the-future-of-the-internet-rest-or-soap/). For several years we have been able to see the constantly increasing significance of client-side programming and the evolution of APIs powering them. PHP programmers cannot ignore this trend as it already influences the leading PHP frameworks, such as Symphony. Let me quote Fabien Potencier (http://fabien.potencier.org/article/49/what-is-symfony2):

"I don't like MVC because the Web has evolved a lot in the recent years and some projects are much different than the projects we had some years ago. Sometimes, you just need a way to create a REST API. Sometimes, the logic is mostly in the browser and the server is just used to serve data (think backbone.js, for instance). And for these projects, you don't need an MVC framework."

So the simple answer could be that learning this pattern of building web applications is good to better...