Bug 793717 (JBEPP-792) - Add a sample skin for Site Publisher
Summary: Add a sample skin for Site Publisher
Keywords:
Status: CLOSED DUPLICATE of bug 793718
Alias: JBEPP-792
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: unspecified
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 6.0.x
Assignee: mark yarborough
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard: EPP_6_0_0_Candidate
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-08 03:42 UTC by Toshiya Kobayashi
Modified: 2013-02-14 12:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 793718 (view as bug list)
Environment:
Last Closed: 2012-09-03 11:29:02 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-792 0 Major Closed Add a sample skin for Site Publisher 2013-02-14 12:10:47 UTC

Description Toshiya Kobayashi 2011-02-08 03:42:36 UTC
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000006GibcIAC&sfdc.override=1
project_key: JBEPP

Users who applied gatein-sample-skin.war to Site Publisher will find Content Explorer distorted. It is reasonable because gatein-sample-skin.war doesn't include any skin resources for SP portlets.
But it is not a good start point for users to develop their own skin. It would be nice to have a sample skin which includes resources for SP portlets and some documentations so that users can customize it.

Comment 1 Toshiya Kobayashi 2011-02-08 03:48:10 UTC
It may be okay if the sample skin includes DefaultSkin resources. But MacSkin/VistaSkin seem to be available :)

Comment 2 Scott Mumford 2011-08-05 05:00:06 UTC
Release Notes Docs Status: Added: Not Yet Documented


Comment 6 Thomas Heute 2011-12-15 11:02:22 UTC
Labels: Added: EPP_6_0_0_Candidate


Comment 7 Thomas Heute 2012-09-03 11:29:02 UTC

*** This bug has been marked as a duplicate of bug 793718 ***


Note You need to log in before you can comment on or make changes to this bug.