Re: render google analytics at end of head
Hm, interesting, on this page: http://www.google.com/support/analytics/bin/answer.py?hl=en_US&answer=174090&utm_id=ad they say: " Once you find the code snippet, copy and paste it into your web page, *just before the closing* tag " This is why I'm asking... If I just dump it in the head in my base page html, wicket still puts other script tags after it (default wicket js libraries for ajax calls). Wouter 2010/9/12 Martin Grigorov > What about using plain javascript to create the new
Re: render google analytics at end of head
This looks like hacking into the output string buffer? That seems a bit of a dirty hack to me, that would involve splitting up just before and appending code their. I hope there is a better way than this... Wouter 2010/9/12 Alexander Morozov > > Hi! > > Have you looked at IResponseFilter ? > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/render-google-analytics-at-end-of-head-tp2536175p2536213.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- check out https://www.memolio.com
render google analytics at end of head
Hi, For some time now, google has changed the way you can incorporate an analytics snippet. The former one was slow and synchronous, the current one is asynchronous, so I would like to use that one. However you have to place it just before . Placing it in our base page at the end of wicket:head doesn't work as wicket pushes it's own extra's for ajax related stuff. Is there a way to make sure the analytics snippet goes to the exact end of the head section? Thanks, Wouter
Re: Can I develop without recompiling/restarting after every change?
Did you use the DevLoader? If so, the eclipse classpath gets loaded directly into tomcat, making hotreplace and debugging possible. See http://www.eclipsetotale.com/tomcatPlugin/readmeDevLoader.html For heavy changes you might need restarts, but eclipse will prompt when necessary. When you use a tool like JRebel these restarts are let frequently needed. Wouter 2010/5/29 David Chang : > Wouter, thanks for your input! > > I got tomcatPlugiin installed as you sugggested and I can start it from > within eclipse to run a wicket app. But how can I do development without > recompiling or restarting after every change? > > The quickstart's Start.java in Jeremy's suggestion uses Jetty as web server. > How can I do a similar thing with Tomcat? Any pointers? I am using Tomcat 6.x. > > Best, > David > > --- On Sat, 5/29/10, Wouter de Vaal wrote: > >> From: Wouter de Vaal >> Subject: Re: Can I develop without recompiling/restarting after every change? >> To: users@wicket.apache.org >> Date: Saturday, May 29, 2010, 9:52 AM >> If you're using eclipse, use sysdeo: >> >> http://www.eclipsetotale.com/tomcatPlugin.html >> >> Wouter >> >> 2010/5/29 David Chang : >> > I am using Tomcat, any tips about how to develop out >> recompiling/restarting after every change? >> > >> > Best. >> > >> > --- On Fri, 5/21/10, Jeremy Thomerson >> wrote: >> > >> >> From: Jeremy Thomerson >> >> Subject: Re: Can I develop without >> recompiling/restarting after every change? >> >> To: users@wicket.apache.org >> >> Date: Friday, May 21, 2010, 12:17 PM >> >> the easiest way to do this is to use >> >> the Start class (Start.java) from the >> >> quickstart to run an embedded jetty instance in >> your >> >> IDE. then, if you run >> >> it in debug mode, it will hotswap any possible >> changes (and >> >> tell you if you >> >> must restart if it's an incompatible change) >> >> >> >> -- >> >> Jeremy Thomerson >> >> http://www.wickettraining.com >> >> >> >> >> >> >> >> On Fri, May 21, 2010 at 10:53 AM, ekallevig >> >> wrote: >> >> >> >> > >> >> > I'm a front-end developer trying to learn >> Java (total >> >> n00b) and working on >> >> > a >> >> > wicket application at work. The whole >> process >> >> feels very slow primarily >> >> > because I have to recompile and restart JBoss >> every >> >> time I make a change. >> >> > So I'm wondering what the best way is to >> avoid having >> >> to do this when >> >> > editing .java/.js/.css/.html files during >> development? >> >> I'd like to just >> >> > make >> >> > changes and then refresh the browser to test >> -- is >> >> this possible? >> >> > >> >> > I've seen in the FAQ that you can change the >> >> application settings to >> >> > auto-reload markup .html files -- where would >> I insert >> >> this setting >> >> > (remember I'm a total n00b). >> >> > >> >> > As to .css/.js/.java files -- do I need >> jRebel or >> >> something like that to >> >> > get >> >> > these files to reload automatically? >> >> > >> >> > Thanks for helping out a super-beginner :) >> >> > -- >> >> > View this message in context: >> >> > http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html >> >> > Sent from the Wicket - User mailing list >> archive at >> >> Nabble.com. >> >> > >> >> > >> >> >> - >> >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> >> > For additional commands, e-mail: users-h...@wicket.apache.org >> >> > >> >> > >> >> >> > >> > >> > >> > >> > >> - >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> > For additional commands, e-mail: users-h...@wicket.apache.org >> > >> > >> >> >> >> -- >> check out https://www.memolio.com >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- check out https://www.memolio.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
If you're using eclipse, use sysdeo: http://www.eclipsetotale.com/tomcatPlugin.html Wouter 2010/5/29 David Chang : > I am using Tomcat, any tips about how to develop out recompiling/restarting > after every change? > > Best. > > --- On Fri, 5/21/10, Jeremy Thomerson wrote: > >> From: Jeremy Thomerson >> Subject: Re: Can I develop without recompiling/restarting after every change? >> To: users@wicket.apache.org >> Date: Friday, May 21, 2010, 12:17 PM >> the easiest way to do this is to use >> the Start class (Start.java) from the >> quickstart to run an embedded jetty instance in your >> IDE. then, if you run >> it in debug mode, it will hotswap any possible changes (and >> tell you if you >> must restart if it's an incompatible change) >> >> -- >> Jeremy Thomerson >> http://www.wickettraining.com >> >> >> >> On Fri, May 21, 2010 at 10:53 AM, ekallevig >> wrote: >> >> > >> > I'm a front-end developer trying to learn Java (total >> n00b) and working on >> > a >> > wicket application at work. The whole process >> feels very slow primarily >> > because I have to recompile and restart JBoss every >> time I make a change. >> > So I'm wondering what the best way is to avoid having >> to do this when >> > editing .java/.js/.css/.html files during development? >> I'd like to just >> > make >> > changes and then refresh the browser to test -- is >> this possible? >> > >> > I've seen in the FAQ that you can change the >> application settings to >> > auto-reload markup .html files -- where would I insert >> this setting >> > (remember I'm a total n00b). >> > >> > As to .css/.js/.java files -- do I need jRebel or >> something like that to >> > get >> > these files to reload automatically? >> > >> > Thanks for helping out a super-beginner :) >> > -- >> > View this message in context: >> > http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html >> > Sent from the Wicket - User mailing list archive at >> Nabble.com. >> > >> > >> - >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> > For additional commands, e-mail: users-h...@wicket.apache.org >> > >> > >> > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- check out https://www.memolio.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
wicket:link images and variation problem
Hi, I'm trying to use variations with images that are automatically localized when they are within wicket:link. When I turned on debugging I could see that it tries to get the image for the current locale, or one without locale extension when it is not available (logo_nl.png versus logo.png). However when I change getVariation() on the page, nothing notable happened in the debug statements. So I started debugging and I found out that Component.getStyle is actually called, but will never give a result, as the parent is consulted to get the variation, however the automatically added components of type AutoLinkResolver$ResourceReferenceAutolink do not get a parent when they are created. Could this be a bug? I would expect the variation to be used when I autolink an image within a normal page. Thanks, Wouter - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: users, please give us your opinion: what is your take on generics with Wicket
> 1) Generifying* Wicket > [x] Can best be done like currently in the 1.4 branch, where models > and components are both generified. I care most about the improved > static type checking generified models and components give Wicket. I had a production quality project with the old 2.0 branch (downgraded it) and that worked just fine and very intuitive, I was very bummed at the time I had to add all these hideous type casts. I do not understand the fuss about generifying everything, I did not have ANY problems using the generics in my production project (which consists of about 30 wicket classes) and it was not a simple crud app, I did some funky wicket stuff with this project (loads of panels, fragment, own custom component, ajax) and it all just worked. > > 2) How strongly do you feel about your choice above? > [X] Whatever choice ultimately made, I'll happily convert/ start > using 1.4 and up. Wouter de Vaal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release 1.4 with only generics and stop support for 1.3
+1 Wouter On Mon, Mar 17, 2008 at 9:13 AM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > This thread is for voting only. Use the [discuss] thread for voicing > your opinion or asking questions. This makes counting the votes much > easier. > > The discussion on our development list makes it clear that a lot of > folks are anxious for generified models. Most users if not all wish us > to release a quick release which is 1.3 + generics. The consequence is > that the core team will stop to support 1.3, and that everybody that > wishes updates will have to migrate to 1.4, and upgrade to Java 5. > > Everybody is invited to vote! Please use > > [ ] +1, Wicket 1.4 is 1.3 + generics, drop support for 1.3 > [ ] -1, I need a supported version running on Java 1.4 > > Let your voices be heard! > > Martijn > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.2 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2 > > - > 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]
