Hmm. Strange things I see with image paths in my borders with variants.
My page is mounted like:
mountBookmarkablePage("/getFrame", OrderPaymentPage.class);
So, when I reach my theme with:
.../getFrame?theme=white
- everything is alright.
But asking it with:
.../getFrame/theme/white
- and my border images are touching server with
".../getFrame/theme/images/bar/white/t.gif" address.
So, as there is no images there, 404 Not Found is returned for them.
They must be ".../images/bar/white/t.gif"
Quickstart?
On Thu, Feb 26, 2009 at 2:52 PM, Anton Veretennikov
<[email protected]> wrote:
> Igor, I did it already :)
> Jeremy suggests another approach - with no variations.
>
> On Thu, Feb 26, 2009 at 2:48 PM, Igor Vaynberg <[email protected]>
> wrote:
>> return new roundedcornerborder(...) { string getvariation() { return
>> "black"; }};
>>
>> -igor
>>
>> On Wed, Feb 25, 2009 at 11:45 PM, Jeremy Thomerson
>> <[email protected]> wrote:
>>> Bummer - knew it couldn't be as easy as it looked. :) I don't suppose it's
>>> something you could do like this, then?
>>>
>>> Border.html
>>> <td class="foo">
>>>
>>> main_white.css
>>> TD.foo { background-image: (/url/whiteimages/bar.jpg); }
>>>
>>> main_black.css
>>> TD.foo { background-image: (/url/blackimages/bar.jpg); }
>>>
>>> As to performance, not sure I understood the question, but selecting the
>>> "themed" borders rather than normal borders doesn't slow anything down. Is
>>> that what you meant?
>>>
>>>
>>> On Thu, Feb 26, 2009 at 1:15 AM, Anton Veretennikov <
>>> [email protected]> wrote:
>>>
>>>> It will be better of course, Jeremy.
>>>>
>>>> My borders have differences not only in css but in images in table
>>>> cells. Images are taken from other folders depending on theme name.
>>>> Yes, I know, rounded corners can be made with pure css. But my war
>>>> with browsers is endless.
>>>>
>>>> I thought about some variable that could be replaces with exact name
>>>> of theme in html part. But onComponentTagBody is final in Border
>>>> class. And I'm far from Wicket guru.
>>>>
>>>> Another question is performance. When borders are many on a page their
>>>> customazation is time consuming. Am I right?
>>>>
>>>>
>>>>
>>>> On Thu, Feb 26, 2009 at 1:54 PM, Jeremy Thomerson
>>>> <[email protected]> wrote:
>>>> > Obviously I have nothing other than the name of your file to base this
>>>> > thought on, but I'll throw it out there anyway....
>>>> >
>>>> > If the only difference between the two is color, just use localized /
>>>> themed
>>>> > css files and use a single HTML file. This will save you a ton of code
>>>> > duplication over having MyBorder_white, MyPanel_white, etc.
>>>> >
>>>> > Maybe you already are, but I couldn't bare to see what appears to be pain
>>>> > and suffering without at least trying to help. :)
>>>> >
>>>> > On Wed, Feb 25, 2009 at 10:13 AM, Anton Veretennikov <
>>>> > [email protected]> wrote:
>>>> >
>>>> >> Hi!
>>>> >>
>>>> >> I have a problem with theme support for borders.
>>>> >> I want to exchange real markup of border depending on theme name, for
>>>> >> example:
>>>> >>
>>>> >> RoundedCornerBorder_black.html
>>>> >> RoundedCornerBorder_white.html
>>>> >>
>>>> >> How to do this in Wicket?
>>>> >>
>>>> >> ---------------------------------------------------------------------
>>>> >> To unsubscribe, e-mail: [email protected]
>>>> >> For additional commands, e-mail: [email protected]
>>>> >>
>>>> >>
>>>> >
>>>> >
>>>> > --
>>>> > Jeremy Thomerson
>>>> > http://www.wickettraining.com
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>>
>>>
>>>
>>> --
>>> Jeremy Thomerson
>>> http://www.wickettraining.com
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
