For straightforward on-page Date formatting, I suggest Databinder's
DateLabel component:
http://preview.tinyurl.com/3cveh5
But for site-wide format handling in 1.2.x, there's no magic bullet at
the moment. Roll on 1.3.0 :-)
Charlie.
On 6/15/07, Seldon, Richard [EMAIL PROTECTED] wrote:
As Alex says, wicket:child tags can't solve this because that's not
the way they're intended to be used.
There are various ways to solve the problem, though: you could place
the common content into a Panel, have a method on the base page return
this panel, and then include it as normal on your
Hi all,
Taken from the Best practice and use of detachable models thread:
On 2/22/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
no, not exactly. if you havent set a model on the component (or set it to
null) and call getmodel() wicket will search upwards for a model that
implements the
() {..} }
-igor
On 2/15/07, Charlie Dobbie [EMAIL PROTECTED] wrote:
Hi Igor,
The processing of the submitted data is handled in the same way, but
the following page navigation must be different. If in a standard
request, I'll need to setResponsePage() to the next page, but an AJAX
like
protected Component newSubmitButton(String id) {
[create with id and return]
}
that you call from the base constructor and override in the subclass.
Nathan
Charlie Dobbie wrote:
Is there a more suitable place to handle page navigation than the
Form's onSubmit/onError methods
is to leave form.submit() unused and put all the logic
into button.onsubmit()
what do you mean no onerror method? ajaxsubmitbutton should have one afaik.
-igor
On 2/20/07, Charlie Dobbie [EMAIL PROTECTED] wrote:
Hi Igor,
Thanks, that's very reassuring! I'm having a bit of fun
, or even an entirely better way of
doing things?
Cheers,
Charlie.
On 2/14/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
i thought you wanted to handle it the same way so why do you need to know if
the processing is ajax or regular request?
-igor
On 2/14/07, Charlie Dobbie [EMAIL PROTECTED] wrote
Hi all,
In my Databinder-using application I have the requirement to
create/edit entities both within a standard request cycle, and via
AJAX inside a Modal Window. In the interests of not duplicating code,
I would like to drive both these processes from the same Form object,
passing a boolean
Hi Jaime,
The Choose One selection only appears when nulls are not considered
valid but the selection is currently null. If you want a default
no-decision option, the cleanest solution is to set the DropDownChoice
to allow nulls, and set the formName.componentName.nullValid property
to the text
You don't say what HTML editor you're using.
If you're using the Amateras editor, you just need to disable validation:
- Right-click your project, select Properties
- Browse to the Amateras tab
- Uncheck XML Validation and Code Completion using DTD/XML schema
and HTML Validation
--Charlie
On
Hi all,
One problem I had today was rendering a Boolean property on a domain
object in a very specific way (Yes/No/Unspecified). After a few false
starts and a few ugly hacks, I came up with the MappedValueModel,
below.
I'm posting it here in case anyone else finds it useful. It's a
simple
11 matches
Mail list logo
