[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsrp][wsia] Request for input, useful portlet properties
Thanks Thomas. I'd like to add the list of CSS classes as specified in WSUI as part of this discussion: http://www.wsui.org/doc/20010717/WD-wsui-20010717.html#Toc5-1-2 -----Original Message----- From: Thomas Schaeck [mailto:SCHAECK@de.ibm.com] Sent: Tuesday, March 26, 2002 7:59 PM To: Alan Kropp Cc: wsia@lists.oasis-open.org; 'wsrp@lists.oasis-open.org'; Alan Kropp; griddell@bowstreet.com; Srinivas.Vadhri@commerceone.com; Rich Thompson; carsten leue; Lothar Merk Subject: Re: [wsrp][wsia] Request for input, useful portlet properties Alan, this is definitively an important topic. We have touched this topic at the WSRP initial meeting and decided that a subgroup organized by Gino Filicetti will look into the details of what are valid markup fragments for different markup languages and what common CSS styles are required in particular for HTML fragments. The members are David Taieb, Khurram Mahmood, Susan Levine, and Michael Hillerman. At IBM we have a set of CSS styles for WebSphere Portal Server, these styles are used by the portlets provided by IBM, other portal vendors probably have similar CSS styles with different names... We are working on creating a list with the subset of styles that seem generally relevant. To really achieve true interoperability of both local portlets as well as WSRP/WSIA services with portals, the industry will need to agree on a generalized, common set of basic styles that portlet or WSRP/IA service providers can securely expect from all portals. Here are the styles used in WPS that might be interesting to consider for generalization: a, table, tr, td, select, input, form, li, p, textarea A A:visited A:hover UL .portletColorBack { background-color: #CCCCCC; } .portletTitle { background-color: #006699; color: white; font-weight: bold; font-family: sans-serif; font-size: x-small; } .portletTitleCust { color: white; font-weight: bold; font-family: sans-serif; font-size: x-small; } .portletHead { font-family: sans-serif; font-size: x-small; font-weight: bold; color: black; } .portletText { font-family: sans-serif; font-size: x-small; } .portletSmText { font-family: sans-serif; font-size: x-small; } .portletTinyText { font-family: sans-serif; font-size: x-small; } .portletBody { } .portletBack { background-color: #FFFFFF; } .buttonText { font-family: sans-serif; font-size: x-small; color: black;} .tableHead { background-color: #6699CC; font-family: sans-serif; font-size: x-small; font-weight: bold; color: #000000; } .tableText { font-family: sans-serif; font-size: x-small; align: center; } .tableShdRow { background-color: #CCCCCC; font-family: sans-serif; font-size: x-small; font-weight: normal; color: #000000; } .fieldErrorText { color: #FF0000; } Best regards, Thomas Thomas Schaeck Architect, WebSphere Portal Server IBM Pervasive Computing Division Phone: +49-(0)7031-16-3479 Mobile: +49-(0)171-6928407 e-mail: schaeck@de.ibm.com Fax: +49-(0)7031-16-4888 Address: IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen, Germany Alan Kropp <akropp@epicentric.com> on 03/27/2002 03:37:56 AM Please respond to Alan Kropp <akropp@epicentric.com> To: wsia@lists.oasis-open.org, "'wsrp@lists.oasis-open.org'" <wsrp@lists.oasis-open.org> cc: Alan Kropp <akropp@epicentric.com>, griddell@bowstreet.com, Srinivas.Vadhri@commerceone.com, Rich Thompson/Watson/IBM@IBMUS Subject: [wsrp][wsia] Request for input, useful portlet properties During our call this morning to talk about fleshing out the Embedded Use Case requirements, Rich Thompson and I thought it would be a useful exercise to build a comprehensive list of typical look and feel abstractions that a portlet could or should expose, in addition to the common properties we're considering (e.g., locale, supported content types, etc.) Plenty of people in both tc's have direct experience creating portal/portlet-related technology, so we figure that perhaps just passing along a list of the abstractions (CSS classes, etc.) that you're working with in your own products or environments would be a good start, and we can then work on normalizing it for inclusion in the requirements. Alan ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC