Hi Kamil,
Nice to see yet another person being very enthousiastic about Wicket. Can't hear enough of that :-)
See the notes below for my reply. Note that I don't have actual experience with the Spring framework itself. I merely see it as an IoC framework with lots of components and services which provides a viable alternative for J2EE application servers.
Kamil Rembalski wrote:
One of things that quite quickly came to my mind is the integration ofYou are not the first person to think about it. But focussing on Spring alone would be very limiting. Adding adapters to enable Spring-like (Pico container comes to mind) integration would be nicer. The question in my opinion remains what can be gained by supplying this kind of features. Considering the current state of development, I don't envision integration of such a framework (when it really adds value) in the big 1.0. Perhaps if it doesn't break too much it might make it into 1.1, but more realistic seems to be aiming at 2.0.
Wicket with Spring/ other IoC container.
I am aware that Wicket is not supposed to be XML-configurable. ButI don't think that this should be on our wishlist for the near future. Wicket being a presentation (only) framework doesn't lend itself tooo much for XML configuration. There actually isn't much to configure in the Wicket core as I see it. Your example of navigation is something which Wicket solves by inheritence and composition of components. If I really need an external configurable menu component, I can create a menu component that renders its HTML based on a XML configuration file read by the model. Nothing in Wicket prevents you from doing this. One might even use Spring to do this.
there are hordes of XML-config-adicts in the java world, who will not
use anything that is not xml-configurable. Optional use of Spring,
using method/constructor injection would give them such a possibility
and would not force other people to write config files.
Authentication configuration: would allow the user to configure for which pages does the authentication occur.This is again a model issue. Authentication has nothing to do with rendering the HTML, which is what Wicket does primarily. And again, the model doesn't constrain anybody to use whatever framework is available for authentication, persistence, etc.
I agree that this is something that needs some work on the Wicket part. Mainly the use and generation of stylesheets in components is something that could use some additional thinking. Most likely, the component that you downloaded should use a stylesheet for rendering itself. One could override the style of the component in the css of the containing page. This takes some effort on the part of the component builder but it is doable.Components are great. If you want to use a calendar, just download a jar and use the component. But what if the component's look does not fill your needs?
What if for example your client for some twistedIf the component builder uses the possibilities of CSS well, then almost anything is possible (see for some good examples: http://www.csszengarden.com). I haven't looked into the tree component yet, but I envision being able to replace the images with your own using CSS, or it should be part of the tree rendering (allowing special icons for nodes such as folders, pdf icons, etc).
reason wants password textbox to be above the login textbox in
SignInPanel? Does Wicket have a mechanism for overriding component's
html resources? Or for overriding the default images (like those in
the Tree component?) And is it possible to provide such a mechanism at
all?
Sorry to hear about the company situation, perhaps you could show in a small setting how easy and fast you can develop applications using wicket. That might trigger some response.BTW, don't you think that components that contain their own images, html, etc. are a little bit in the opposition to Wicket's html-centric nature? In other words, if a single [span componentName="compicatedComponent"] in the input markup spills out 2K of html code completely out of control of the WYSIWIG tool, can we talk about the maintainability of the templates using those tools?
The only disadvantage of wicket is that my company will probably never
use it (beurocracy). And maybe problems with marketing - tapestry was
out there for a few years and still not that many people have heard
about it...
The marketing campaign is something we haven't talked about on the list, but Eelco and I talk to eachother almost everyday and we are *very* aware of the marketing issue. We both think Wicket has the potential to outgrow Tapestry given some good components and very good documentation. We hope that Wicket can become the Hibernate of the presentation technologies. If you have some ideas on how to promote Wicket, that would be very appreciated!
Thank you for your interest in Wicket. I really appreciate your ideas on extending Wicket to enlarge our target audience.
Thanks!
Martijn Dashorst
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Wicket-develop mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
