Re: [wsrp-markup] [wsrp][markup] Customization screen consistency

Isn't enough just to specify the CSS style classes the buttons should 
have? This would achieve consistent look&feel if the developer follows 
the markup recommendations. And what the label displays is up to the 
portlet developer.

Windows or Swing do not define the 'Save' menu item, developers do and 
they always use 'Save', not 'Store' or 'Persist'.


Alejandro


Eric VanLydegraf wrote:
 > I would expect that part of the registerConsumer process
 > the consumer could be supplying the producer "consumer Image URLs" and
 > "button labels" for a standardized set of action buttons.
 > Should the consumer supply them a well behaved producer should use 
them, if
 > not the producer can resort to it's set
 > of default button images or just plain submit form buttons.
 >
 > I would consider this in the same vain as the standardized set of CSS 
style
 > classes in supporting Consumer "UI consistency"
 >
 >
 > -----Original Message-----
 > From: Michael Freedman [mailto:]
 > Sent: Wednesday, July 24, 2002 4:36 PM
 > To: WSRP-Markup
 > Subject: [wsrp-markup] [wsrp][markup] Customization screen consistency
 >
 >
 > Folks,
 >    How does a portal get UI consistency within portlet
 > customization screens?  Particularly the set of
 > buttons and the names used for "apply", "cancel",
 > "ok", "revert to defaults", etc.
 >     -Mike-
 >
 >
 > ----------------------------------------------------------------
 > To subscribe or unsubscribe from this elist use the subscription
 > manager: <http://lists.oasis-open.org/ob/adm.pl>
 >
 > ----------------------------------------------------------------
 > To subscribe or unsubscribe from this elist use the subscription
 > manager: <http://lists.oasis-open.org/ob/adm.pl>