As I mentioned, disabling the compression did not work. As you can see
from my post, I am getting CSS styles like .x6v.
On 8/27/07, Simon Lessard <[EMAIL PROTECTED]> wrote:
> Hello Andrew,
>
> Disabling compression does just that... .af_inputText_content is very
> readable imho. the underscore after af is always coming from | while all
> other underscores were translated from ::, also you can always remove the
> dot if the generated selector starts with .af_. So, .af_inputText_content
> comes from af|inputText::content.
>
>
> Regards,
>
> ~ Simon
>
>
> On 8/26/07, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> > Disabling the style compression only seems to help a little bit. The
> > FileSystemStyleCache._getShortStyleClassMap still returns
> unreadable
> > styles. For example, one of the selectors firebug showed was:
> >
> > .x6v, .portlet-section-selected, .xbv, .portlet-table-selected, .xc2 {
> >
> > the .x* styles are really near impossible to know where they came from.
> >
> > Is there an easy way to get all styles to stay in a readable state?
> >
> > Thanks,
> > Andrew
> >
> > On 7/30/07, Jeanne Waldman <[EMAIL PROTECTED]> wrote:
> > > Another tip:
> > >
> > > Use Firebug. It allows you to view the css that is rendered on a
> > > component by default and then you can inhibit anything you want in your
> > > skin using -tr-inhibit.
> > >
> > > Also, by default we compress the styleclass names to boost performance.
> > > While creating your skin, you can disable this compression so that you
> > > can see styleclass names that more closely resemble the css selectors.
> > >
> > > To do this, add to your web.xml file:
> > >
> > > <context-param>
> > >
> <param-name>org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION</param-name>
> > > <param-value>true</param-value>
> > > </context-param>
> > >
> > > And finally, looking at the xss files like Abhijit suggests will help
> you as well.
> > >
> > > - Jeanne
> > >
> > >
> > > Abhijit Ghosh wrote:
> > > > Chris,
> > > >
> > > > On 7/28/07, *Chris Hane* <[EMAIL PROTECTED]
> > > > <mailto:[EMAIL PROTECTED]>> wrote:
> > > >
> > > >
> > > > We are trying to create our own custom skin for Trinidad and I
> > > > have a basic
> > > > question:
> > > >
> > > > First, where do the defaults for a paticular element come from?
> For
> > > > example, we are trying to skin "af:column::header-text". When we
> > > > remove
> > > > the color element, a default of #669966 is put into the
> > > > transformed skin.
> > > >
> > > >
> > > > The defaults are defined in base-desktop.xss and
> > > > simple-desktop.xss.AFAIK your custom skin CSS is overlaid over the
> > > > styles defined in base-desktop.xss and simple-desktop.xss.If you
> > > > specify a style in your custom skin CSS it will override the default
> > > > styles.The XSS files are actually XML files so you can read them if
> > > > you want to find out the default values.
> > > >
> > > > Thanks,
> > > > Abhi
> > > >
> > > > I found the skin selector documentation, is the another doc
> > > > describing how
> > > > skins works and their default values? I have css people working
> on
> > > > defining the skin and they are having a slow time trying to figure
> > > > this out.
> > > >
> > > > Second, the skin selector documentation states that it is not
> > > > up-to-date.
> > > > Where can I find updated info - source code only?
> > > >
> > > > Thanks,
> > > > Chris....
> > > >
> > > >
> > >
> >
>
>
