Follow along as we work together to build 10 different applications using Laravel 4. Since each chapter is devoted to the design of a different application, there is no need to read the book in any particular order. Instead, you can pick and choose the blueprints that are of most interest to you and dive right in.This book is for intermediate to advanced level PHP programmers who want to master Laravel. It's assumed that you will have some experience with PHP already. This book is also for those who are already using a different PHP framework and are looking for better solutions.
Time for another Laravel cookbook. I am writing one of these, so perhaps I’m over-sensitive to some of the faults because I’ve seen them in my own work.
This is another Laravel 4 cookbook, demonstrating how to build a number of projects. The chapters are significantly longer than the previous Packt Laravel cookbook I reviewed, more in line with my book. Consequently, you can linger in tasks and really get to grips with the teaching. It’s still reference, but it’s the kind of reference you will need access to if you forget minutia of what you learned by first going through it.
This book assumes more than it states. There are examples of Blade templates without the author ever having explained what Blade is. There are examples of JavaScript (and Ajax requests) without the author having ever explained what these two things are. The front-matter does set some requirements for reading, but they are about general PHP knowledge and “those who are already using a PHP framework”.
I too have been guilty of these things, but that’s where the technical reviewer needs to step in and point out unfair expectations.
There are many comments, within the code listings of this book. That would be hugely beneficial if not for the complete lack of syntax highlighting. What should help tends to fill the screen in confusing monochrome. While we’re on the subject, take a look at this example from the second chapter…
This illustrates the problem with omitting syntax highlighting. I know template code leans towards being a mess in a book, but the insane level of indentation and monochrome presentation are enough to make me want to skip code listings altogether.
There is a nice set of projects to build, from link shorteners to e-commerce websites. If you are already familiar with the basics of Laravel 4 (and JavaScript) then there’s a lot to learn from this book. If you’re a beginner, I suggest first reading Code Bright and a few JavaScript (particularly jQuery) tutorials.
This is the Laravel 4 book I recently had a chance to grab. If you’ve just read through Laravel 4 documents and want to play with it by making simple things up and running, you’ll get some useful ideas from the examples throughout this book. You can’t say that the way they implemented is ideal though.
I’ve found many typos and even inconsistent file names which lead me to think if the authors actually run the test with the codes. But, fortunately, nothing major. With all those explanations, it’s not hard to get the idea of what they’re trying to do. Besides, it’s always good to have a look at others’ implementations when you are new at it I guess.
It’s not exactly a type of book I want to keep for a reference. But, if you feel a bit overwhelmed even after reading through Laravel 4 documents and don’t know how to start putting things together. Their step-by-step instructions will help you get the hang of it. Recommended to beginner level Laravel 4 developers. As a side note, I found it super easy to copy-and-paste source codes from ebook format.
This book is characterized by its practical application on Laravel framework. It is useful for intermediate and advanced developers. However, beginners will find a difficulty in dealing with this book. In addition, this book provides applications that introduce the developer to different points of view and ideas of other developers. It is worth reading.
A lot of typos and gaps here. It's not something you could follow through step by step and end up with working code. The projects are decent, but this has obviously not been adequately proof-read. The explanations are a little disjointed too. Maybe a good read for an intermediate level user who already knew enough to spot the errors.