Hi Ernesto,
Yes, thanks for your input, I guess the way to go is to wrap components into
combined Wicket Panels, and then use repeaters.
Thanks again!
reiern70 wrote:
>
> Hi,
>
>> Component: TextField
>> Required: True
>> Type: String
>> Length:30
>> Order: 2
Hi,
> Component: TextField
> Required: True
> Type: String
> Length:30
> Order: 2 (The order in which it needs to be displayed on the
> form)
> Defaul Value: "some value"
> and so on.
>
> An entry can also define a compound component (like a Wicket panel comp
Thanks for the answers guys, getting some ideas here that might be helpful.
In a way what our backend allows us to do is define a (specific) form and
store it in our database. So, when you call the backend service, it returns
and array declaring all the components that will make up the final form.
Hi,
I see no contradiction in having your UI (declaratively) defined by a
service and having panels (with associated HTML markup): that markup
could "match" what you wanted on your "definition". As you also suggest,
you could use repeaters to create META-components that read your
definition and p
Hi Mito
Behaviors can also add stuff (like encapsulating your tag in to new
tags) to the component,
Like I describe here:
http://ninomartinez.wordpress.com/2008/12/11/wicket-never-stops-to-impress-me/
mito wrote:
Hi,
I've been using Wicket at home for quite a while. The company I work for
Hi Mito,
Basically you are asking for Label. Label can generate anything you
want. Look at the source of Label for inspiration if you need more
customization.1
Also take a look at TextTemplate. There is also a FreeMarker version, I
think its in wicketq-extra.
Regards,
Erik.
mito wr
Hi,
I've been using Wicket at home for quite a while. The company I work for has
an old Swing application and we've been trying to figure out how to migrate
it and make it web based.
Even though I've been pitching in for Wicket since day one, the team lead
decided to go with "standard" stack
(j