Matt, Thanks for the pointer, but to be honest all this skinning stuff sends me into a dizzy state of confusion. I looked at the FAQ which has one occurrance of "-tr-inhibit" - this directed me to the purpleSkin in the demo. From there I can see a usage of "-tr-inhibit" but I don't really understand how I'd apply this in my case.
Cheers, C. On 13/02/07, Matt Cooper <[EMAIL PROTECTED]> wrote:
You also can create a custom skin that inhibits styles from the style definitions using "-tr-inhibit". More details can be found at: http://wiki.apache.org/myfaces/Trinidad_Skinning_FAQ Regards, Matt On 2/13/07, Chris Lowe <[EMAIL PROTECTED]> wrote: > > Hi Adam, > > Thanks for the info on the minimal skin, I'll switch to that in the > meantime. An even more minimal skin would be great though - anything to > save bandwidth, server hits and browser parsing of CSS/JS will be greatly > appreciated. > > My main reasons for not using a skin are cited in my original post. I'm > using making minimal use of the Trinidad component set (using <10 > components) and having the CSS download seems excessive, plus learning > about > the skinning for my needs was overkill. So for my current project, regular > CSS suited my needs for positioning and setting simple attributes like > width. > > I completely get the point of skinning and it looks really useful, it's > just > not necessary at the minute. > > I will be using a compression filter for resources like CSS, I've always > found that the following filter does everything I need: > > http://sourceforge.net/projects/pjl-comp-filter/ > > Are there any better ones out there? > > Are the Trinidad generated CSS/JS files constant between pages? If so, do > you see any problem with setting the HTTP cache headers: "Expires" and > "Cache-Control" to prevent the browser from requesting these resources on > each page request? > > Cheers, > > Chris. > > > > On 13/02/07, Adam Winer <[EMAIL PROTECTED]> wrote: > > > > Skinning is an integral feature, so there's no turning it > > off. You could switch to a simpler l+f - minimal, for instance, > > clocks in at <30K. We could provide an even more minimal l+f, > > perhaps. But, I wonder, why are you looking to completely disable > > skinning? > > > > If it's an issue of download size, you might consider getting > > a .gzip filter involved, which will majorly decrease the size > > of the .css file (~80% smaller). The minimal l+f .css comes > > in at about 5K once gzip'd. > > > > -- Adam > > > > > > > > On 2/13/07, Chris Lowe <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > Is it possible to switch off skinning altogether? If so, will turning > > off > > > the skinning prevent the wrapping of various components in SPANs and > the > > > download of a ~140k CSS file? > > > > > > Cheers, > > > > > > Chris. > > > > > >
