>> If there's any framework that let's you develop mini-applications
>> seamlessly, it's Wicket.
>
> If one can easily build a group of components that will appear on different
> pages and work together collaboratively as a whole functional unit that's
> great.

You certainly can, it's all a matter of designing these components
well. Again, I don't know much about Django, so I can't really
compare.

>> The availability of such components is
>> another matter.
>
> Yes, I (honestly) wonder though why more higher-level components are not
> available? You suggest it is not technical.

I think - certainly speaking from my situation - that it is easier and
quicker with Wicket to develop components exactly for your needs
instead of depending on more generic ones. Especially domain specific
components can be hard to develop in such a way that they are helpful
for a great number of cases (great enough to justify the extra effort
of developing such components generically), and their API might get so
complex that it is hardly worth the effort. That's what I think at
least.

But in the end, it's just a matter of someone picking up the task to
develop things like survey components etc.

>>> Also, I can't see a high-level automatic and customisable admin/CRUD
>>> interface for Wicket like there is for Django.
>>
>> Not sure what you're looking for, but something like
>> http://wicketwebbeans.sourceforge.net/ or
>> http://sourceforge.net/projects/wicket-rad?
>
> I've read a bit about them and will check them out further.  I don't believe
> they handle relationships (to-one and to-many) between entities though?

No idea.

> Yes, I understand and agree.  However, the project I am doing now is
> relatively small and simple and not "Enterprise class" hence I am looking
> for an easy and RAD solution.

You might be better off using a framework that focussed on that. There
nothing wrong with using different frameworks for different purposes
if you ask me :-)


> Unfortunately, although there has been some discussion of serialising
> closures on the Groovy mailing lists but I don't believe anything has been
> done about it.

Too bad. Well, a single person can make all the difference in the world :-)

> I think I will just stick with plain Java Wicket or Django for the time
> being.

Sounds good. Good luck with your project.

Eelco

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to