I know that wicket offers 2 colors of modal dialog backgrounds, BLUE and GRAY.
Servoy is using BLUE by default, is there a way to change it to GRAY?
Better yet, is there a way to substitute servoy-webclient/resources/modalwindow/res/frame-blue-1-alpha.png or servoy-webclient/resources/modalwindow/res/frame-gray-1-alpha.png with graphics of our own? I can’t find it in the media library nor physically on disk.
ow yes!!
+1
see: application_server\lib\wicket-extentions.jar\org\apache\wicket\extensions\ajax\markup\html\modal\res\
Johan, so we need to manually change stuff inside that jar-file? what about Servoy updates? we have to do that again?
yes
that is the location of the files that the browser uses.
Hi Johan,
I tried to apply changes but I see no change in either IE or FF/Chrome. I made sure to clear my browser cache, still no change.
When I look at the HTML/CSS generated, it is still the same. Is this cached somewhere else?
are you testing in the developer?
Then that is not the jar that is used. The wicket jars are in the servoy shared plugin.
What i pointed out was purely the app server
Yes I was testing in developer.
I tried it from the server now. That gives an Internal error now. I cannot start the client app.
The only change I did was in the modal.css. I refer it to the -gray* png now instead of the -blue*.
Is there a specific way to edit the jar files? I just used WinRAR for that, maybe that’s the problem?
Giving us a property or code-setting, is’nt that much easier?
I don’t think that’s feasible considering the millions of thing you could change in this. But some documentation on the frameworks that Servoy is based on would be very helpfull.
After Johan’s initial mail I also found the wicket-calendar jar. Can’t wait to get my hands dirty on that one too. But first we need to know how to operate on these jars…
After restoring the backup of that particular jar file, everything is back to normal so me messing around with it with WinRaR was not appreciated. Howto…
These jars are signed. If you alter a file in a jar, the signing hash will be wrong so most probably Java will see the whole jar as corrupted…
If you do this (but I wouldn’t recommend it unless you alter the source distribution and recreate the jar from there - and when I mean the source distribution, I mean the Servoy one, not the Wicket one, since Servoy has patched Wicket for its own usage), you will need to re-sign the jar.
you should be able to just remove the signing.
Wicket jars dont really need to be signed, they are pure serverside.
Great, that solved it.
I justed removed the RSA en SF files from the META-INF folder and presto!.
Thanks Johan.
I think the cleverer way to go is inspect the HTML/CSS of a Web Client in the browser and find the CSS selectors used to decorate the dialog. Then take those selectors and add them to the default webclient template CSS that Servoy uses, with your own values for the CSS properties and to make those take priority over the CSS that is incorporated in the Wicket jars, you just put “!important” behind each CSS property value.
That way you do not have to hack the jars.
Paul