View this message in context: Re: [Trinidad] Understanding Trinidad
Skinning?
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--Understanding-Trinidad-Skinning--tf4161417.html#a12686032
Sent from the MyFaces - Users mailing list archive at Nabble.com.
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,
Hello Andrew,
I am using also
debug-outputtrue/debug-output
in trinidad-config.xml
But I am not sure if this is responsible to decrypt css style names ...
Regards,
Peter
Simon Lessard wrote:
Hello Andrew,
Disabling compression does just that... .af_inputText_content is very
readable imho.
yes, I also have the debug-output set to true in my
trinidad-config.xml. But I am still getting the .x6v type of CSS
styles with org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION
set to true in the web.xml
FYI, this is version 1.0.2 that I am using
On 8/27/07, Petr Kotek [EMAIL
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
Hello Andrew,
It works perfectly fine for me ... What container are you using? Is it
possible that's a very strange container that isn't greedy at all about
trimming white space and that you configured your web.xml the following way?
context-param
param-name
Yes, I stepped through the code and saw that it checked the parameter
fine. The thing is that it is checked in SkinImpl.java but it doesn't
seem to have had any affect on
FileSystemStyleCache._getShortStyleClassMap which is what is creating
the .x* type of class names.
With that said, some class
Andrew,
Could it also be possible that your stylesheet is cached? Try clearing
you cache. This works for me as well.
Scott
Simon Lessard wrote:
Hello Andrew,
It works perfectly fine for me ... What container are you using? Is it
possible that's a very strange container that isn't greedy
Stopped tomcat (version 6 btw), cleaned out the work directory
completely and the temp directory, ran an mvn clean on my project
and re-deployment my application, and am still getting the shortened
class names. I checked /tmp also and didn't see any files there. Is
there anywhere else I should be
Your browser cache. I must say that I've been trying this on the
Trinidad 1.2 branch and I know it works there. I havn't used 1.1 in a
while so it's possible something might be broken..
Scott
Andrew Robinson wrote:
Stopped tomcat (version 6 btw), cleaned out the work directory
completely
Since I stepped through the code in the server, I can see that the
short names are in that map
(FileSystemStyleCache._getShortStyleClassMap). Besides, I can see all
my changes to the skin reflected in the CSS on the client, so I know
it is not a client side cache issue.
Here is the contents of
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
Chris,
On 7/28/07, Chris Hane [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
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
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
Hello Chris,
For your first question, it come from the simple skin. If you want to get
rid of the default value, try to add the following in the selector:
-tr-inhibit: all;
or
-tr-inhibit: css property to inhibit;
For your second question, yes source or skin-selectors.xml file which is
only
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
18 matches
Mail list logo
