jQuery with PHP
The second chapter is where you will see some demonstrations. It will give you a quick overview on the matter with jQuery-PHP-HTML integration, how the data is handled, how you can create inline edit buttons, dinamic select boxes, etc and will get you in to the action as fast as possible. However this is just a quick way to demonstrate you that you can do a lot of things with jQuery without even knowing anything and just copy-pasting would be enough. Later it code will be explained and you will get a detailed idea on how everything fits together. The later chapters will discuss more specific ways like file handling, data grids, etc thoroughly.
From chapter 3 to 9 there are detailed descriptions and how-to’s for things like tabbed pages, data grid views (data tables), drag-n-drop’s, image editing tools etc. These chapters are the heart of the book and they contain a lot of recipes. The best part of these chapters is that it does give you both the plugin and how to use it. So you know what to download and add it as library for the specific task you need to do and you also know how to use it.
He also mentioned “Caching jQuery Objects”, while his point is valid and something that a good developer must do, this is not called caching, it’s called “variable assignment”. Instead of calling one function 10 times you call it one time and you assign it to a variable and later use it, you cannot call it actual caching but “best practice”.
Finally as last thoughts, think this book as a book which you will keep in your library for a year or two. It does not contain anything which cannot be found on the internet however it saves you time from searching it and puts most of the things you will need when creating a “RIA” and also contains how-to’s. It’s not a book you should start reading from top to bottom like the previous books I reviewed (Magento and Zend Framework) because it does not contain a whole application, it only contains recipes and it’s a good cookbook while some of the code examples would have been better. Many of the examples are kept simple for the sake of simplicity and easy understanding as the primary audience is the back-end developers who only thinks to get it done on the front-end.