About? Print? Config? All great ideas for custom portlet modes.
The point is, a custom mode is only possible if the vendor supports it. For example, IBM provides a config mode, and their portal supports it. So, I can create a portlet that uses a config mode, and deploy it to WebSphere Portal, and life is grand. But, if I deploy it to Pluto, well, it simply won't work as designed.
I put together a tutorial on creating custom portlet modes. It deploys a custom portlet to WebSphere Portal Server 5.1. Enjoy:
How to Use Custom Portlet Modes with WebSphere and Rational Application Developer (IRAD) It's a good idea. It allows vendor flexibility and competition, but also maintains compatability across portals. Custom mode or not, all portlets must have a view mode.