Simon - Thanks. I finally got it to work with your change. The last step is I had to start/stop the server - since I'm using 1.0.0 and the bug fix for hot-deploying a skin came in 1.0.1.

Thanks,
Chris....

Simon Lessard wrote:
Hello Chris,

You got a small error in your selector, the right one is

af|inputDate::launch-icon (note the double colons)

While at it, here's the rules for urls placed within skins.

All examples assume an application using /myApp context path and using the following directory structure:

    * /skins
          o /mySkin
                + /skinImages
    * /images

Rules:

    * If the url starts with "//", the url is considered server
      relative, i.e. it won't prefix it with the context path
          o url('//resourceApp/globalImages/logo.gif') -->
            /resourceApp/globalImages/logo.gif
    * If the url starts with "/", the url is considered application
      relative, i.e. the context path will prefix the generated url
          o url('/images/logo.gif') --> /myApp/images/logo.gif
    * Otherwise, it's considered relative to the skin's stylesheet
          o url('skinImages/logo.gif') --> Some url pointing to
/skins/mySkin/skinImages/logo.gif

Regards,

~ Simon


On 8/9/07, *Chris Hane* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    How can I skin the inputDate launch icon?

    I have tried variations of this:

    af|inputDate:launch-icon {
        content:url(../ires/chris/images/dfb.gif);
    }

    When I use firebug it shows the icon being generated from:

      adf/images/dfb.gif

    and not my icon defined in the skin file.


    Is there anything obviously wrong with what I'm doing?

    Thanks,
    Chris....


Reply via email to