Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Image

Plone 3 Products Development Cookbook 52

RickJWagner writes "This book takes an interesting path to teaching Plone 3 development. Unlike most software instructional books, it starts way back in the often-unread Preface by listing 10 requirements a mythical customer is asking the reader to implement in Plone 3. The requirements are realistic and I think would probably be quite a stretch for an inexperienced Plone developer. The rest of the book is dedicated to implementing those 10 features, and coaching the reader on Plone 3 development along the way." Read on for the rest of Rick's review.
Plone 3 Products Development Cookbook
author Juan Pablo Gimenez, Marcos F. Romero
pages 388
publisher Packt Publishing
rating 9/10
reviewer RickJWagner
ISBN 1847196721
summary If you want to develop feature-rich add-on products in Plone, this book is for you.
I wouldn't say this is a good book for a novice Plone user. There really isn't much introductory material, and there is little material to transition the reader from Plone installation to meaty development. A newbie could certainly use this book if it were augmented with additional material (say, the Internet and a fair amount of time allocate), but the reader had better be ready to self-educate on Plone/Zope/Python development if they are not already proficient in these areas. For developers who already know their way around Plone, however, this book is an excellent step-by-step guide to adding serious functionality to the platform.

The book follows a consistent theme throughout. The desired functionality is briefly (very briefly) described, then the reader is given the following sections: Getting Ready, How to Do It, How it Works, and (sometimes) There's More. Here's how these work:

Getting Ready — outlines installation prerequisites, the things you'll need to gather.
How to Do It — step by step instructions on how to implement your changes.
How It Works — after you've configured things in the previous step, this step explains why things work.
There's More — an optional section where further reading can be found, or maybe extras like test procedures.

The book includes more than just the 10 specified features from the Preface, though. The authors cover development best practices, documentation, a section on testing, and many other goodies that are not directly in the path of implementing those 10 requirements. I especially liked the parts about performance improvements, a consideration that's sometimes lacking in development books.

Many expert-level techniques are revealed to the reader, especially those concerning production of Products for Plone 3. The authors are obviously well versed in their domain and they freely share best practices the reader will be able to leverage. These tips deal with the whole development cycle, distributed in a sort of holistic manner, sprinkled into several chapters along with the primary material for that section. It's not a book on the development process, but if the reader is willing to listen as advice is given, they will become aware of many development best practices (automated testing, documentation, etc.) along the way.

Besides just the how-to aspect of Product development, the authors give the reader some insight into runtime aspects of a Plone site. The chapter covering cache configuration, for example, was lighter on Product development verbiage and much longer on advice that is bound to be helpful for a Plone site administrator rather than a Product developer. I imagine it's probably not uncommon for people to wear both these hats, so this is another useful characteristic. Developers and Administrators alike can profit from this kind of advice.

The book definitely reads differently than most tech instructional books-- it's more like an expert's working notes than it is a typical dev book. It took me a few chapters to catch on, but after I figured out how to best use this format I can see how this would be very useful for random-access reference work. You don't need to do everything in sequence, just skip right to where you need to go.

There's a lot of text provided, too. There are nearly 370 pages here, almost all of it good, meaty instructions provided in the soon-familiar instructional template the authors established early on. If you know exactly what you want to do, there is little room for ambiguous interpretation-- you're bound to get it right. Some might consider portions of the text verbose, but that can be a desirable trait in a book that's going to serve as both introductory survey and later valued reference.

If you're charged with doing Plone 3 development, I'd recommend this book. There's a lot of expert advice here, and it covers a wide range of development activities. I would imagine almost every developer will learn some things from this book, and many developers will learn a great deal. For producing Plone 3 products, it will provide a quick answer for many commonly encountered questions.

You can purchase Plone 3 Products Development Cookbook from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
This discussion has been archived. No new comments can be posted.

Plone 3 Products Development Cookbook

Comments Filter:
  • Re:Okay but... (Score:3, Insightful)

    by Monkeedude1212 ( 1560403 ) on Wednesday June 30, 2010 @03:57PM (#32749418) Journal

    Just in general, there seems to be a bunch of book reviews on Slashdot lately about really niche subjects with no explanations as to what they are.

    Well, thats because they are usually either the next gen (I want to say 4th level...?) languages or systems that haven't really caught on fully yet, and it sometimes takes a book to help push the product.

    For example, you may or may not be familiar with PHP. I think its safe to say you've at least heard of it, possibly even used it, if you are as well versed in the universe of tehnology as you think. Have you heard of Joomla? It may have crossed your ears a few times, but have you used it? It's another Open Source Content Management system, built on PHP. I haven't used it myself but I think I've seen a few book reviews on it here on slashdot. When I look into these kinds of things, its kind of like how Assembly is to C - You understand C a lot more when you know Assembly but its not necessary to write code. You don't need to know PHP to use Joomla, but you'll be a better developer for it.

    So, Plone is along those lines, the next step in development, except its in Python, not PHP.

  • Re:Okay but... (Score:3, Insightful)

    by siride ( 974284 ) on Wednesday June 30, 2010 @04:58PM (#32750094)
    Slashdot isn't chat. Slashdot is a techie news aggregator. Why it ought to behave by the same rules is beyond me. In any case, Slashdot frequently mentions technologies without defining them. Generally, they are well-known among the crowd here (e.g., Linux kernel, X11, iPhone, etc.), but I guess they misjudged things with this article.
  • Re:Okay but... (Score:3, Insightful)

    by Unoti ( 731964 ) on Wednesday June 30, 2010 @09:45PM (#32752376) Journal

    I consider myself well versed in the universe of technology

    There's the problem, right there. "Technology" in general is a terribly diverse subject, and getting more diverse with every passing moment, and at a faster rate with every passing moment. In the field of software technology, this is even more true than in most of the other sciences. If you'd been doing software development for more than 7 years you might be more sensitive to this issue. 20 or 30 years ago, there were people around that knew pretty much everything there was to know about digital computers. (This may not be true strictly speaking, but it's true enough for people like, say, Peter Norton.) Today, it's just not possible because the state of the art is progressing too quickly.

    I hear what you're saying regarding not giving even a 1 line intro. But if you weren't up on Plone before, that's not slashdot's fault, that's your fault. Plone and Zope have been discussed here at length many, many times over the last several years.

    I don't really want to come down on you too hard, but maybe you're not as much of a technology badass as you think.

1 + 1 = 3, for large values of 1.

Working...