Just some things that need to be done for Jetspeed 1.1 and 1.0.1. I want 1.0.1 to be available within the next couple of weeks. This should just be a tweak of the platform. Also if anyone wants to help out please feel free to jump on any one of these issues. Remember this is a volunteer organization so having active contributors is very important to Apache's success. ----------------- Jetspeed 1.0 TODO Last Modified: $Date: 2000/03/23 03:45:31 $ Latest version at: http://www.working-dogs.com/jetspeed/cvsweb/index.cgi/jetspeed/docs/misc/ Author: [EMAIL PROTECTED] ********************************* 1.0.1***************************************** - Within overview.xml add items about Apache, Jakarta, Cocoon, ECS, etc. - Move CVS and mailing lists over to locus.apache.org. - DefaultPortletController needs to handle PortletExceptions better. Provide the user with a better dialog box ... ie this portlet couldn't render... - Rework JetspeedResources.properties - should become JetspeedResources.properties. - Make it more like TurbineResources.properties - Caching is currently broken in Jetspeed... all portlets are always added to the cache (only under Linux IBM JDK 1.1.8 is this reproducable) - Fix this so that JDK 1.1.8 doesn't GC the objects... look at the thread for this. - This turns out to be a problem with Turbine and maybe a Classloader it uses The PortletCache uses a static instance but for some reason the VM doesn't thinks that this isn't a static reference when it actually is. Therefore everytime it hits the portlet that uses the cache the PortletCache is re-instantiated - Fix up artwork (have a powered by Jetspeed logo) so that it appears on the home page. - Redo the cache infrastucture. - Place PortletControllers and PortletControls within the cache - Note: need a better way to get cache handles before their impls are instantiated. - Note: Portlets handles shouldnt be obtained by the AbstractPortlet - Ability to flush the cache without restarting Jetspeed or the servlet engine ********************************** 1.1 ***************************************** ** HIGH PRIORITY - Portlets should have the the ability to be added to a users profile so they when they logon they get their own profile and their own portlets. - Release and publisize my RSS 0.92 format.. see if anything else addresses this. - Include RSS support for having an <img> on all <item>'s (this isn't supported in the current RSS version). This should become RSS 0.92 - This version of RSS is actually very complex and should become something like Jetspeed Site Markup. We also need a GUI for adding records to the default site markup. Jetspeed should have multiple site markups but some get priority. - Ability to browse by topic. - integrate the Javacorporate Forum code. - Discussion portlet which obtains it's information based on another portlet. ** NORMAL PRIORITY - Finish scheduler support into Turbine/Jetspeed. Place PersistentDocumentDaemon and FeedDaemon in the Scheduler as tasks - Admin interface (add to turbine): - view cache hit ratio - purge cache - number of items in cache - XML sybscription architecture - Blend multiple OCS channels. This should currently work but test its impl: - Add all OCS channels from Internet Alchemy - http://theweb.startshere.net/channels.phtml?format=OCS - http://www.moreover.com - http://www.headlinewatch.com - these all need to be blended - Improve Portlet subcription. You should be able to pick from a couple of generic portlets. Then you should also be able to search from additional portlets using keywords (from OCS) or domain name. - Bring back the meta search engine portlet. The Javascript is currently broken here. - Feature to browse portlets by the URL's domain. - Support for better browsing of Portlets - should enable the user to select how many pages at a time to view and to have grouping of the Portlets - user should be able to skin their portlets via the PortletConrol and PortletController. - Improve RSS support. Only use 1 stylesheet this should be *very* smart and work across RSS 0.90, 0.91, and 0.92. - Support the ability for portlets to do their own posts. Each portlet needs to define it's own namespace. If they don't define their own namespace then two portlets might conflict and one might accidentally realize it was posted. also might want to thing about a service() method of a portlet. - require all portlets to use XHTML. Then we can process the <form> data and add namespaces within the Factory and pull them out when we call service() on a Portlet - PortletMarkup - ability to have colums that only have a certain number of portlets - Portlets provide layout hints which the Portlet controller is supposed to pay attention to. <portlets> <!-- Provide a remote url that has skin data. This would be the default but would be removed if the user has his own skin. --> <skin href=""/> <portlet> <metainfo> <!-- Only a suggestion to the PortletController --> <!-- Provide a suggestion that the PortletController should include a title --> <!-- "state" can be either "minimized" | "normal" | "maximized" --> <layout title="false" columnId="0" rowId="0" state="minimized"/> <!-- Provide a hint as to when this Portlet should get expired from the cache. Use the same interval spec as OCS --> <cache interval="hourly" value="2"/> </metainfo> <portlet/> </portlets> <skin> <!-- Define what columns to have and their widths. --> <column id="0" width="40"/> <column id="1" width="100%"/> <column id="2" width="40"/> <page-title-background></page-title-background> <page-title-foreground></page-title-foreground> <portlet-title-background></portlet-title-background> <portlet-title-foreground></portlet-title-foreground> <portlet-body-background></portlet-body-background> <portlet-body-foreground></portlet-body-foreground> </skin> - Add support for a Portlet "state" Include the state in the cache engine so that different cache states are correctly displayed. this.getPortletConfig().getState() - STATE_NORMAL - STATE_MINIMIZED - STATE_MAXIMIZED This is necessary so that portlets can determine how much information to display when the user changes their state. For example a maximized portlet might display extra graphics, etc. - Develop 3rd party authentication API for Portlets that need to authenticate with other non-Jetspeed systems. IE Mail, NNTP, SQL, etc - develop a secure password store that stores portlets and authentication mappings - This is necessary because the user might have multiple content sources that each have different usernames and passwords - think about having all portlets referenced via a GUID. This way you can reference all portlets (with complex parameters) without having a huge URL that contains all params. - Content/Portlets should be able to be refreshed and not just get stale in the cache forever. - ability to set the refresh rate within portlet markup - Make NNTP (any JavaMail provider) into a portlet - Mail-XSP and integrate it with my current messaging - iCalendar Support - Project Support - Move some of the screens to become properties so they can be easily created by the user: PortletViewerScreen, etc - Place a disk space cap on the PersistentDocument cache - Have a boolean property defined so that people can run Jetspeed but that it doesn't *require* user authentication. This would just run Jetspeed but never give you the option to logon. ********************************** BLUE SKY ************************************ - Messaging TODO: - Jetspeed support for placing the JavaMail transport and provider into debug... - Message "Forward" support - Support for deleting messages - JNDI/LDAP address book support - URL highlighting within message view - Reply to all - ability to search through all JavaMail messages - Messaging using cocoon and custom DTD - Four objects: - Transport - Store - Folder - Message which uses a URL/Session communications "protocol" and -- Kevin A Burton ([EMAIL PROTECTED]) http://relativity.yi.org Message to SUN: "Please Open Source Java!" "For evil to win is for good men to do nothing." -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
