You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Ross Gardler (JIRA)" <ji...@apache.org> on 2010/10/19 00:17:27 UTC

[jira] Commented: (WOOKIE-131) Skinnable widgets

    [ https://issues.apache.org/jira/browse/WOOKIE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922322#action_12922322 ] 

Ross Gardler commented on WOOKIE-131:
-------------------------------------

A plan for implementation (comments welcome)

<div id="wookie-widget">
  <div id="wookie-toolbar">This is where the toobar will be</div>
  <div id="wookie-content">This is where the content will be</div>
  <div id="wookie-footer">This is where the footer will be</div>
</div>

We also need to provide a default CSS for rendering this as, for example:

+-----------------------+
|TOOLBAR                |
+-----------------------+
|                       |
|CONTENT                |
|                       |
+-----------------------+
|FOOTER                 |
+-----------------------+

This will need to be documented and all widgets should be changed to conform to 
this format.

We would need to document this on the Wookie website and also document how to 
extend this.

Once all this is in place I would like to start extending it to provide docuemnted 
CSS identifiers to be used in common cases, for example, we may want to define 
"wookie-navigation" as being used for a common navigation menu. We can then provide 
various CSS alternatives for rending this as a vertical navigation menu or drop down 
menu, or whatever.


> Skinnable widgets
> -----------------
>
>                 Key: WOOKIE-131
>                 URL: https://issues.apache.org/jira/browse/WOOKIE-131
>             Project: Wookie
>          Issue Type: Improvement
>            Reporter: Ross Gardler
>             Fix For: 0.9.1
>
>
> One of the common problems with sites that consist of multiple widgets is that they just luck messy. Each widget designer will create their own look and feel and chaos ensues.
> Wookie should provide a facility to skin widgets in order to keep them consistent on a single site. This requires:
> - design guidelines
> - common CSS
> - CSS override ability
> The design guidelines defines the recommended approach for designing a widget. It will provide a template for common widget layouts and CSS identifiers for common elements.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.