please share with us the detailed
how-to?
There's no particular secret, just call
this.getMarkupSettings().setStripXmlDeclarationFromOutput(true); in
your Application.init() method.
Regards.
--- On Sun, 10/4/09, Phil Housley undeconstruc...@gmail.com wrote:
From: Phil Housley undeconstruc
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Phil Housley
-
To unsubscribe, e-mail: users-unsubscr
final thing to note is that IE6 will screw up any page with an
?xml declaration. I prefer to include it in my source, and then have
Wicket strip it out at the last moment - at least when I'm forced to
be IE6 compatible.
--
Phil Housley
not
forcing the issue, so I'm currently thinking I will have to step up
the infrastructure to add things like error reporting. Fortunately I
can just delegate to Wicket pretty quickly, so shouldn't be too much
extra code.
Phil.
On Tue, Sep 29, 2009 at 2:11 PM, Phil Housley undeconstruc
.
Despite all that, I don't particularly want a hard dependency on
anything other than Wicket, so plain Java first, other things
hopefully on top.
Phil
On Tue, Sep 29, 2009 at 4:11 PM, Phil Housley
undeconstruc...@gmail.comwrote:
Hello list,
I'm currently working on some ideas for building
, and the
radio buttons are partially processed out of sequence to get the input
when its needed.
I don't know how safe this is, but it seems to work.
Thanks everyone.
On Tue, Sep 15, 2009 at 11:10 AM, Phil Housley
undeconstruc...@gmail.comwrote:
2009/9/15 Bas Gooren b...@iswd.nl:
The fact
to work around them, or does the whole thing sounds like so much
crack?
Thanks,
--
Phil Housley
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
to
refresh, but if you are being strict on that sort of thing, I guess
you will have a refresh button on the page when and only when it is
appropriate.
--
Phil Housley
-
To unsubscribe, e-mail: users-unsubscr
there
though, so I'm doing it off my own back at home.
Cheers,
Scott
On Tue, Sep 29, 2009 at 2:11 PM, Phil Housley undeconstruc...@gmail.com
wrote:
Hello list,
I'm currently working on some ideas for building apps with fairly
complex workflows. My aim is to find a nice pattern/framework
it
around as raw input, but I don't want to know if it is missing or
fails to convert/validate.
Thanks for any help.
--
Phil Housley
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail
in searching and various other places,
so it would be a lot of work to make them all respond to this
particular use. A way to just prevent the required check/validation
from the top would fit the bill better.
2009/9/15 Phil Housley undeconstruc...@gmail.com:
Hello,
I'm currently working on a search
required flags on fields
// ...
// Call regular validation
super.validate();
}
}
Regards,
Bas
- Original Message - From: Phil Housley
undeconstruc...@gmail.com
To: users@wicket.apache.org
Sent: Tuesday, September 15, 2009 2:30 PM
Subject: Re: Selectively
- From: Phil Housley
undeconstruc...@gmail.com
To: users@wicket.apache.org
Sent: Tuesday, September 15, 2009 3:37 PM
Subject: Re: Selectively ignoring required fields
Several interesting ideas, but they all seem to involve more invasive
changes than I really want to make - either
13 matches
Mail list logo
