Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
Image

Plone 3 Products Development Cookbook 52

Posted by samzenpus
from the read-all-about-it dept.
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:
  • Okay but... (Score:3, Informative)

    by Lunix Nutcase (1092239) on Wednesday June 30, 2010 @11:32AM (#32746426)

    Okay, but what the fuck is Plone?

  • Re:Okay but... (Score:5, Informative)

    by Lunix Nutcase (1092239) on Wednesday June 30, 2010 @11:39AM (#32746550)

    No, the point is that no where in the review does it even have one sentence telling anyone what Plone is.

  • Re:Okay but... (Score:5, Informative)

    by zr-rifle (677585) <zedr@zedDEBIANr.com minus distro> on Wednesday June 30, 2010 @11:44AM (#32746640) Homepage
    Thanks for asking nicely...

    Plone [plone.org] is a Content Management System (CMS) written in Python programming language for the Zope 2 Web Application server. Among the big names that have deployed Plone in the past are NASA, CIA, Akamai and Novell.

    Pros:
    • Mature
    • Flexible
    • Secure (with a proven track record)
    • Cross platform
    • Tons of third party extensions

    Cons:

    • Steep learning curve for developers and integrators
    • Python, not PHP (so uncommon hosting requirements)
    • Some say it's slow... (but have probably failed to correctly setup and optimize caching)
  • by kb1jcy (1598403) on Wednesday June 30, 2010 @11:49AM (#32746738)

    Wow, what a blast from the past! I got on the Plone train back in the 0.9.x version days and continued to build sites on it until 2006. It had it's peak between '04 - '06. I moved on to Rails and LAMP because clients wanted something that ran on a low-end shared hosting account or low-end Xen virtual machine. I'm surprised it's still around and at version 4. I still think it's better in some ways than Drupal but it's a pain in the ass to set up a proper hosting environment for it.

    So far as the name Plone, it was derived from the electronica band Plone as the developers were fans of the band.

  • Re:Okay but... (Score:4, Informative)

    by Kevin Stevens (227724) <.moc.liamg. .ta. .vetsvek.> on Wednesday June 30, 2010 @01:00PM (#32747894)

    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.

    I have been a professional software developer for 7 years now in a range of areas, whether it be web development of HR apps based around java to server side financial trading systems in C++, and I consider myself well versed in the universe of technology. So when I hear about something that I have never heard of before, I am surprised, and when I hear that this technology is big enough to have a book written about it, its kind of a jaw dropping moment.

    I guess what I am trying to get at is... I kind of wonder who is submitting these reviews- people who are generally interested in the book/subject and wanted to review it, or people who have a vested interest in promoting the book for their own ends. I think its perfectly ok to try to promote books, especially if you think they will be useful to others, but if you have a vested interest in the book, it should be made known. A search for the reviewer, RickJWagner shows only returns two items- both for books recently reviewed and written by a publisher I am not familiar with, Packt Publishing.

  • Re:Unread (Score:3, Informative)

    by Lunix Nutcase (1092239) on Wednesday June 30, 2010 @01:31PM (#32748344)

    Because Packt Publishing has some long and storied history on Slashdot?

Whom the gods would destroy, they first teach BASIC.

Working...