Having Wicket manage resources outside classpath
is it possible to have Wicket manage resources (.css and .js) outside of the classpath, so that we can leverage all the great dev/prod things that Wicket does with resources served from within the classpath? We typically put our resources at the root of the context: /assets/css /assets/js /assets/images /WEB-INF/ This way we can reference images from within our style sheets using 'background:url(../images/logo.png);' If Wicket were to serve these resources (I guess we would have to move the assets down a level so they were brought in to the accessible classpath of the Wicket app), can we manage such context sensitive references within CSS files that are being managed by Wicket? We're using 6.x N
Wicket WebRTC Integration
Hi everybody, I just implemented a component to provide a way to integrate a video conference to Wicket applications using WebRTC - I would be very pleased to receive feedback! An installation of NodeJS is required. https://github.com/klopfdreh/wicket-components-playground (Scroll to section Wicket WebRTC Integration) kind regards Tobias - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket WebRTC Integration
Hi, Excellent work, congrats! And I'm talking about all your wicket-components-playground project! I'll test your Wicket WebRTC Integration and tell you how it goes. In fact, I'm currently using a full JS WebRTC component ( https://code.google.com/p/webrtc4all/) but I'm not fully satisfied with it. Hopefully, yours will do it for me. Regards, Pierre On Fri, Jan 30, 2015 at 5:26 PM, Tobias Soloschenko tobiassolosche...@googlemail.com wrote: Hi everybody, I just implemented a component to provide a way to integrate a video conference to Wicket applications using WebRTC - I would be very pleased to receive feedback! An installation of NodeJS is required. https://github.com/klopfdreh/wicket-components-playground (Scroll to section Wicket WebRTC Integration) kind regards Tobias - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Si le sang ne coule pas assez chaud dans tes veines, je le répandrai sur le sable pour qu'il bouille au soleil.
Re: Having Wicket manage resources outside classpath
Hi, you can manage your resources like this. There are classes / methods to generate headers for CSS and JS based on a given URL: http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup/head/CssHeaderItem.html http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup/head/JavaScriptHeaderItem.html You can use the forUrl method of both classes. In addition you could also mount ResourceReferences to a specific path an write ../mypicture.jpg in your CSS / JS files. See the user guide for handling resources. kind regards Tobias Am 30.01.2015 um 14:21 schrieb Nick Pratt nbpr...@gmail.com: is it possible to have Wicket manage resources (.css and .js) outside of the classpath, so that we can leverage all the great dev/prod things that Wicket does with resources served from within the classpath? We typically put our resources at the root of the context: /assets/css /assets/js /assets/images /WEB-INF/ This way we can reference images from within our style sheets using 'background:url(../images/logo.png);' If Wicket were to serve these resources (I guess we would have to move the assets down a level so they were brought in to the accessible classpath of the Wicket app), can we manage such context sensitive references within CSS files that are being managed by Wicket? We're using 6.x N - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
