This post originated from an RSS feed registered with Python Buzz by Carlos de la Guardia. Original Post: In support of Plone 3 portlets Feed Title: I blog therefore I am Feed URL: http://blog.delaguardia.com.mx/feed.atom Feed Description: A space to put my thoughts into writing. Latest Python Buzz Posts Latest Python Buzz Posts by Carlos de la Guardia Latest Posts From I blog therefore I am

Even though I have spoken in favor of not forgetting the through the web use case for Plone, I have to say that I fully support what Martin Aspeli has to say about Plone 3 Portlets. They are truly a step in the right direction.

Like he says, more portlets are needed for common tasks and documentation is not abundant, but it is now easier for developers to create better portlet solutions for their customers.

In my experience, customers want portlets to do a lot of things, and having a solid foundation for their development and use seems good to me. Many customers like to meddle with page templates, but a portlet usually has a lot of logic behind and they are not likely to do a lot with them outside of the ZPT. As Martin says, with the TAL portelt in Plone 3 you still have this option.

As a developer, I totally hate Plone 2.x portlet handling, starting with the unfamous right_slots and left_slots properties. The old system is really not user friendly for either the developer or the TTW crowd.

I really appreciate Martin's work, and I wanted to say that I like Plone 3 portlets a lot. I like them even though they render almost useless one of my own products, which I wrote precisely to improve portlet management and development in Plone 2.5 (by the way, for those not yet doing the jump to Plone 3, I would love it if you take a look. It's called portletmania and you can find it in the collective).