Misc Thoughts

[petar]

Hi again,

now I am ready to thank you very much for WicketRAD! (I got it working ;-))

I have some questions/thoughts:
 * Couldn't you add a default behaviour for e.g. Strings <-> it should annotate the property with @TextField (for the editor) and @LabelProperty (for the table)
 * Shouldn't WiRAD add the yaml-file-approach of WicketWebBeans to configure beans?
 * And shouldn't WiRAd use one annotation @WRAD(editor="textfield", sortable="true", ..) instead of all the annotations?
 * [JPA] Is there a way to avoid extending from DataWebApplication (instead of WebApplication)?

Finally you should document that we can use @WysiwygEditor instead of @TextField. This is very very cool!
BTW: the user then needs to add
<dependency>
  <groupId>commons-collections</groupId>
  <artifactId>commons-collections</artifactId>
  <version>3.2.1</version>
</dependency>

Regards + and happy WiRADing,
Peter.

[wfaler]

Hi,
Thanks for the feedback!

It is entirely possible to implement custom behaviours and ways of configuring the forms by implementing the IFormMetadata interface, and it's dependent interfaces. You could effectively implement any behaviour, or any data source (not only beans, I have thought about db tables).
I think this is the answer for points 1 and 2.

At the moment I have not gotten around to implementing any other configuration options than annotations, and I think they work quite well as they are very explicit in what they do.
But if you want, I can gladly look at including other ways of configuring forms and behaviours if you have ideas that you want to use. I'm more than happy to look at contributions.

As for point 3, could you please elaborate a little? I don't quite understand what you mean. Although I'd be very happy to get rid of the @Order(1) way of ordering fields if I could think of a more elegant solution.

4 - There is no direct way of avoiding DataWebApplication, however if you want to extend something else, it should be simple to just look at the DataWebApplication implementation and put that into your WebApplication implementation.
All it really does is override the newRequestCycle() method and provide the DataRequestCycle for each RequestCycle instead of the default one.

petar wrote:

Hi again,

now I am ready to thank you very much for WicketRAD! (I got it working ;-))

I have some questions/thoughts:
 * Couldn't you add a default behaviour for e.g. Strings <-> it should annotate the property with @TextField (for the editor) and @LabelProperty (for the table)
 * Shouldn't WiRAD add the yaml-file-approach of WicketWebBeans to configure beans?
 * And shouldn't WiRAd use one annotation @WRAD(editor="textfield", sortable="true", ..) instead of all the annotations?
 * [JPA] Is there a way to avoid extending from DataWebApplication (instead of WebApplication)?

Finally you should document that we can use @WysiwygEditor instead of @TextField. This is very very cool!
BTW: the user then needs to add
<dependency>
  <groupId>commons-collections</groupId>
  <artifactId>commons-collections</artifactId>
  <version>3.2.1</version>
</dependency>

Regards + and happy WiRADing,
Peter.

[petar]

Hi,

> As for point 3, could you please elaborate a little?

Yes, it is just a cosmetic point. So, instead
@Sortable
@TextField
@Order(1)

it wouldn't blow up the code if you use a one-liner:
@WRAD(sortable="true", editor="textfield", order="1")

for the order problem you could add an annotation for the whole entity:
@WRAD(prop1, prop2, prop3)
but this is not refactoring-save

Another cool point would be the tab feature in WicketWebBeans: it sorts the properties of one bean
into several categories (tabs). E.g. a general property tab and a specific property tab. See here:
http://wicketwebbeans.sourceforge.net/wiki-html/Tabs.html

Regards,
Peter.