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/03/27 00:02:27 UTC
[jira] Created: (WOOKIE-131) Skinnable widgets
Skinnable widgets
-----------------
Key: WOOKIE-131
URL: https://issues.apache.org/jira/browse/WOOKIE-131
Project: Wookie
Issue Type: Improvement
Reporter: Ross Gardler
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.
[jira] Updated: (WOOKIE-131) Skinnable widgets
Posted by "Bernhard Hoisl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernhard Hoisl updated WOOKIE-131:
----------------------------------
Attachment: footer.txt
When using the template for issue Wookie-133 I encountered that when inserting content as, for example
<h1>Header</h1>
in <div> 'wookie-content' the footer disappears. There seems to be incorrect behaviour when using 'min-height' attributes. It would be nice if the footer appears at the bottom of the widget, but I would rather have it at the end of the content of a widget if this means it will get displayed. That is why I just commented out the min-height CSS attribute.
Maybe this needs some more testing with other browsers/OS and a generic solution can be found.
I used Google Chrome 7.0.517.41 beta and Firefox 3.6.10 with 64-bit Ubuntu (Kernel 2.6.32-25-generic) and both browsers showed the same behaviour.
-Bernhard
> 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
>
> Attachments: footer.txt
>
>
> 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.
[jira] Commented: (WOOKIE-131) Skinnable widgets
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924096#action_12924096 ]
Ross Gardler commented on WOOKIE-131:
-------------------------------------
I'm not seeing this problem in Firefox, IE or Chrome.
I don't like the idea of a floating footer, and wouldn't it just float of the page if the texst was too long? Might well do so with the CSS i've put in there anyway.
I *really* fon't like the idea of doing layout in Javascript that is just wrong in my opinion. Way to hard to manage (change the height of the footer and you have to edit the javascript). Sure, we could calculate the height of the footer in the javascript routine, but that sounds like a hack. Plenty of sites do this without javascript so I don't see why we can't. All we need is someone with the time to explore it and do the CSS.
I'm leaving as is for now, but this issue remains open for many reasons, not jus the footer problem.
> 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
>
> Attachments: footer.txt
>
>
> 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.
[jira] Commented: (WOOKIE-131) Skinnable widgets
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922509#action_12922509 ]
Scott Wilson commented on WOOKIE-131:
-------------------------------------
Having a footer always appear at the bottom of the viewport is a problem that is very difficult to resolve in CSS alone - I've usually resorted to using JS to reset the position - see WOOKIE-153 for an example of this sort of layout.
> 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
>
> Attachments: footer.txt
>
>
> 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.
[jira] Commented: (WOOKIE-131) Skinnable widgets
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (WOOKIE-131) Skinnable widgets
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Wilson updated WOOKIE-131:
--------------------------------
Fix Version/s: 0.8.2
Definitely worth doing - I'm putting this against 0.8.2
> 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.8.2
>
>
> 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.
[jira] Issue Comment Edited: (WOOKIE-131) Skinnable widgets
Posted by "Bernhard Hoisl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922505#action_12922505 ]
Bernhard Hoisl edited comment on WOOKIE-131 at 10/19/10 6:21 AM:
-----------------------------------------------------------------
When using the template for issue Wookie-133 I encountered that when inserting content as, for example
<h1>Header</h1>
in <div> 'wookie-content' the footer disappears. There seems to be incorrect behaviour when using 'min-height' attributes. It would be nice if the footer appears at the bottom of the widget, but I would rather have it at the end of the content of a widget if this means it will certainly get displayed. That is why I just commented out the min-height CSS attribute.
Maybe this needs some more testing with other browsers/OS and a generic solution can be found.
I used Google Chrome 7.0.517.41 beta and Firefox 3.6.10 with 64-bit Ubuntu (Kernel 2.6.32-25-generic) and both browsers showed the same behaviour.
-Bernhard
was (Author: hoisl):
When using the template for issue Wookie-133 I encountered that when inserting content as, for example
<h1>Header</h1>
in <div> 'wookie-content' the footer disappears. There seems to be incorrect behaviour when using 'min-height' attributes. It would be nice if the footer appears at the bottom of the widget, but I would rather have it at the end of the content of a widget if this means it will get displayed. That is why I just commented out the min-height CSS attribute.
Maybe this needs some more testing with other browsers/OS and a generic solution can be found.
I used Google Chrome 7.0.517.41 beta and Firefox 3.6.10 with 64-bit Ubuntu (Kernel 2.6.32-25-generic) and both browsers showed the same behaviour.
-Bernhard
> 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
>
> Attachments: footer.txt
>
>
> 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.