Sounds good, We just need to make sure of the following:1. the portlet participates in filtering in a meaningful way (db config, logging, etc) 2. If included on the default layout the demo'd functionality is interesting and more importantly doesn't introduce any external dependencies (like some imap server somewhere)
It doesn't sound like either of those would be a problem so I'm all for adding it to the default set of portlets.
-Eric On 10/12/2011 12:40 PM, Drew Wills wrote:
Hey folks,As I mentioned a few minutes ago in uportal-user & portlet-user, I'd like to bundle the Jasig Email Preview portlet with the uPortal platform...*****It's a really sharp portlet, and I hope it will help uPortal make a good impression with potential adopters by building on the notion that uPortal comes with many compelling portlets "out of the box."With this purpose in mind, a new Service (data source) implementation has been added to Email Preview: DemoAccountService. This service doesn't access emails over IMAP, POP, SOAP, or through any other customary means. It loads a collection of "demo" emails from a JSON file contained in the project itself. In this way, it can give example users -- like admin, student,and staff -- the experience of entering the portal and immediately seeing their "INBOX." No setup or configuration required. All the nice Email Preview features work with this service implementation: view message, mark seen/unseen, delete, etc. But the collection is a user-specific copy, so when the user logs in again (or another user logs in) the INBOX will be "reset" to the original contents.***** The new 1.1.0 release includes these features.I'd like to do an overlay, a demo portlet-definition, and put the portlet on the example layout(s).Any thoughts? drew
smime.p7s
Description: S/MIME Cryptographic Signature
