Atomized Presentation Services:
Wednesday Jul 12, 2006
Yesterday I mentioned Portlets can be considered Atomized Presentation Services. I thought I could expand that definition a bit. Atomized means they are part of an overall presentation viewable by an individual user on one or more portal pages.
- [SnapFunction] - designed to provide a simple method to view or enter common or frequently accessed data into a larger application.
- Example: an enterprise has automated its business process for manufacturing widgets. This application is complete and is a full / independent web application (with its own URL). A portlet is developed which provides a manager a list of production lines which are running below peak production thresholds. The manager can click on the line items and is presented (in the same portlet) a detail on the line managers current recommendations and production line resolution status.
- Example: an manager is able to select from a set of available portlets to add to their page. Each portlet provides a graph which shows the near-real time status of a business process. The portlet provides no other drill down functionality.
- Example: A portlet allows an individual to track a list of blogs - blog updates are listed, clicks in portlet display blog in new window.
- Example: A portlet allows an individual to interface to a webservice.
- [BuildingBlock] - designed to work in conjunction with a set of Building Block portlets, allowing individual functions to be constructed seperately, and allowing other building blocks to be placed on the same portal page or additional functions to be added "as building blocks" to the page over time.
- Example: A portal page consists of two portlets. Portlet 1contains a search text field and a list of items that are the top of a categorical taxonomy. Portlet 2 contains initially a view of the "catalog items of the day". If user enters a search request into portlet 1, the results for the list are displayed into Portlet 2. If a list of items matches the result, portlet 2 shows the list and if one item is selected from the list, the results are displayed in Portlet 1. A user can click to add an item into a shopping basket in Portlet 1. If a user clicks on a link at the top of the page [e.g., "Show Shopping Basket"], the display is routed to a new portal page with a portlet that shows the list of items placed into the shopping basket. After time a new portlet, portlet 3 is added to the page which shows a list of recently viewed items.
- Example: A portal page consists of 4 portlets. Portlet 1 and Portlet 2 work in combination. Portlets 3 and 4 are individual functions. Portlet 1 contains a bar graph showing production levels each day for the last 7 days. Clicks on the bar graphs show detail information in Portlet 2. Default view for Portlet 2 is a summary of all production levels and issues over last 30 days. Portlet 3 provides a simple menu list, linking to other web applications that can be used in support of production control. portlet 4 contains a pick list (each list item corresponds to one day in the last 7 days) and a text field. The user can select a day in pick list and enter comments which are stored as a record for the specific day.
- [Singleton]- functions which are simple and completely self contained
- Example: A portlet contains data in a content management system. The portlet displays the latest published content.
- Example: A portlet contains a menu list.
- Example: A portlet allows an individual to calculate the mortgage payment given a balance, number of payments and the interest rate.
Why are these important? The answer is because opensource communities can build a great deal of these and make them available to any portal administrator. The more generic portlets available to the world community, the greater the functionality to the end user, the greater the value of the deployments.
-- Next we can discuss how this can be exponentially beneficial when discussing opensource, atomized services available to portal communities.
Like this post?
|
|
|
|
|
|
|
|
