Re: documentation
Hi all, On Tue, 22 Jan 2013 18:25:41 +0100, Guillaume Smet wrote: > On Tue, Jan 22, 2013 at 5:53 PM, Philippe Demaison > wrote: > > Are you kidding ? > > First thing first, while everyone agrees that a good documentation is > a good thing, you should consider that you don't pay anyone to write > it. On Tue, 22 Jan 2013 19:08:35 +0100, Thies Edeling wrote: > Wicket is open source, if you feel that the documentation is lacking - feel > free to contribute. don't mean to offend anyone, but things like those are the least helpful kind of answers possible. We all know Wicket is open source, we all know what open source means, an we all know that we aren't paying anyone. It's just that if someone had the resources to pay anyone or significantly contribute to the documentation himself (*after* having learned everything he'd need, and after doing so *without* a complete reference), he'd probably not complain in the first place. More probable is that he's already got a job to do himself and is just looking for the best tool to do so. Of course, shouting abuse (not that I'd think anyone here did) at maybe even unsalaried developers who are doing what they can doesn't help, either. To add my experience to the subject, I bought the 'Wicket in Action' book some time ago, and for my first steps with Wicket 6 I tried to extract what I could from it and the Net. The problem is, just as Philippe said, much has changed between versions, and it's not only that things I find sometimes don't apply anymore, but, what's possibly worse, I can't even know whether code examples I find still work until I tried them myself, as the changes aren't really exhaustively documented and because, well, there is no such thing as a Wicket 6 reference. As far as I am concerned, I'll keep trying to get into Wicket 6, though - but that's something I'll be doing in my spare time, because I probably won't ever see Wicket used at my main job, and so I can take my time. Cheers, Robert - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: set favicon.ico dynamically in wicket 6
Hi Tim, I ran into the same question a couple of days ago, and in what maybe constitutes overkill for a simpler solution I didn't see, I looked at CssResourceReference and reused as much of the code as seemed to be necessary to make a FaviconResourceReference: https://docs.google.com/uc?export=download&id=0B3dKFXxMXAj1dWpCVUJqYzNJYUk With it, you can put your favicon.ico where you said you would, create a FaviconResourceReference feedReaderFavicon = new FaviconResourceReference (FeedReader.class, "resources/favicon.ico"); and add response.render(FaviconReferenceHeaderItem.forReference(feedReaderFavicon)); to your page's (overridden) renderHead method, just as you would with a page-specific CSS resource. Cheers, Robert On Sat, 24 Nov 2012 21:36:14 +0100, Tim Van Meerbeeck wrote: > Hi > > I got a question about wicket 6 and adding a favicon.ico: > > I am trying to use a StringHeaderItem but I want the favicon.ico to be in > the resources folder (normal page: > http://localhost/whatever/page?0standard wicket resource directory: > http://localhost/whatever/resources/*). I think I should use a > ContextRelativeResource to point to the favico but you can'( point that in > stringheaderitem. > > I am looking at the best way to do this in Wicket 6 and above. for earlier > versions of wicket I found some things on the net but version 6 changed > things around and I suppose this will be easy but I can't find it. > > Any help is appreciated > > Tim Van Meerbeeck > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Intro, Wicket 6, RuntimeException error page
Hi Jordi,
excellent, thanks!
It seems that the matter was discussed before, resulting in ticket
https://issues.apache.org/jira/browse/WICKET-2659 with a proposal for a
change to Wicket that would automatically pass an Exception to the page
specified by getApplicationSettings().setInternalErrorPage if the page's
class had a suitable constructor, but the proposal was voted down because
of the existence of your approach.
Cheers,
Robert
On Sat, 17 Nov 2012 15:30:33 +0100, Jordi Deu-Pons wrote:
> Hi Robert,
>
> I'm using a custom error page in Wicket 6 adding a
> RequestCycleListener at WebApplication init like this:
>
> /* In case of unhandled exception redirect it to a custom page */
> getRequestCycleListeners().add(new AbstractRequestCycleListener() {
> @Override
> public IRequestHandler onException(RequestCycle cycle,
> Exception e) {
> return new RenderPageRequestHandler(new
> PageProvider(new ExceptionErrorPage(e)));
> }
> });
>
> Here you can see that you get the exception on the constructor.
>
> I'm not sure if there is a better way to do this in Wicket 6.
>
> Best regards,
>
> Jordi.
>
> On Sat, Nov 17, 2012 at 2:18 PM, Rob Schroeder wrote:
> > Hello,
> >
> > I'm a new list member and I'll start with a quick introduction:
> >
> > After one or two earlier, but aborted attempts to try and get into Wicket,
> > I've
> > finally decided to take the plunge now, even if only for some pending
> > personal
> > projects and possible future side-jobs. On my primary job as a Java SE/EE
> > developer, JSF will most probably become the one-and-only web framework for
> > the
> > foreseeable future, which I don't like, but that's life.
> >
> > While the mentioned attempts were with Wicket 1.3 and 1.4, it probably would
> > seem stupid to start with anything but Wicket 6 now.
> >
> > It seems though that Wicket 6 introduced some major changes so that quite
> > some
> > of the docs, tips & tricks to be found on the web are no more applicable,
> > including parts of the official Wicket Wiki and not really covered by the
> > migration hints either; at least that's my impression after my initial
> > dabblings
> > in Wicket 6, which leads me to the first questions for which I found no
> > hints so
> > far:
> >
> > In Wicket 1.5, there is a way to define a custom error page for
> > RuntimeExceptions which knows about the causing exception, by extending
> > WebRequestCycle and overriding the WebApplication's newRequestCycle method.
> > In
> > Wicket 6, I can use getApplicationSettings().setInternalErrorPage and
> > getExceptionSettings().setUnexpectedExceptionDisplay, but within my error
> > page
> > class I don't see my Exception, then. Did I miss something?
> >
> > Cheers,
> > Robert
> >
> >
> >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
>
>
>
> --
> a10! i fins aviat.
> J:-Deu
>
> -
> 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
Intro, Wicket 6, RuntimeException error page
Hello, I'm a new list member and I'll start with a quick introduction: After one or two earlier, but aborted attempts to try and get into Wicket, I've finally decided to take the plunge now, even if only for some pending personal projects and possible future side-jobs. On my primary job as a Java SE/EE developer, JSF will most probably become the one-and-only web framework for the foreseeable future, which I don't like, but that's life. While the mentioned attempts were with Wicket 1.3 and 1.4, it probably would seem stupid to start with anything but Wicket 6 now. It seems though that Wicket 6 introduced some major changes so that quite some of the docs, tips & tricks to be found on the web are no more applicable, including parts of the official Wicket Wiki and not really covered by the migration hints either; at least that's my impression after my initial dabblings in Wicket 6, which leads me to the first questions for which I found no hints so far: In Wicket 1.5, there is a way to define a custom error page for RuntimeExceptions which knows about the causing exception, by extending WebRequestCycle and overriding the WebApplication's newRequestCycle method. In Wicket 6, I can use getApplicationSettings().setInternalErrorPage and getExceptionSettings().setUnexpectedExceptionDisplay, but within my error page class I don't see my Exception, then. Did I miss something? Cheers, Robert - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
