If your building small to
medium size applications I could see grails or a CMS fitting your needs.
You didn't mention how much you have done with wicket, but I think it
takes a while (and a project or two) before you really realize the
beauty of its approach to building web applications. I
t; Are there any demo/reference websites that run Hippo CMS or Hippo Portal?
>
> Original-Nachricht
> > Datum: Fri, 16 Jan 2009 16:12:13 +0100
> > Von: "Frank van Lankvelt"
> > An: users@wicket.apache.org
> > Betreff: RE: Things I miss
amental
> changes in the core of some Java framework you do not wish to know in
> detail..
>
> So long...
>
> Toby
>
> Original-Nachricht
>> Datum: Thu, 15 Jan 2009 21:46:08 -0500
>> Von: Trevor Burnham
>> An: Tobias Marx
>>
Great!
Are there any demo/reference websites that run Hippo CMS or Hippo Portal?
Original-Nachricht
> Datum: Fri, 16 Jan 2009 16:12:13 +0100
> Von: "Frank van Lankvelt"
> An: users@wicket.apache.org
> Betreff: RE: Things I miss in Wicket
> Sure th
Frank
> -Original Message-
> From: Tobias Marx [mailto:superoverdr...@gmx.de]
> Sent: 16 January 2009 14:10
> To: users@wicket.apache.org
> Subject: Re: Things I miss in Wicket
>
> Brix only works the way it works because it does not need a
> database..with
... or conscious design debt... ;)
**
Martin
2009/1/16 Johan Compagner :
>> An ideal web-application is developed once and the Java code is never
>> touched again for 3-5 years until there are a lot of new features
>> necessary
>
>
> where do you live?
>
> thats not my experience. Yes after a
> An ideal web-application is developed once and the Java code is never
> touched again for 3-5 years until there are a lot of new features
> necessary
where do you live?
thats not my experience. Yes after a while the web app code is pretty done
but then it did already run for 1 or 2 years i
On Fri, Jan 16, 2009 at 7:47 AM, Tobias Marx wrote:
> What about merging Wicket and Tapestry? Similiar to Wicket with Tapestry
> templates?
>
I don't think this would work very well. The Tapestry team's
philosophy doesn't really work well with how the Wicket community
works.
--
ouch the Java code there is an
> error by design
>
>
> Original-Nachricht
>> Datum: Fri, 16 Jan 2009 14:53:05 +0200
>> Von: Martin Makundi
>> An: users@wicket.apache.org
>> Betreff: Re: Things I miss in Wicket
>
>> All you need i
rting from scratch is often the better option in
the long-term.
Original-Nachricht
> Datum: Fri, 16 Jan 2009 07:59:11 -0500
> Von: Richard Allen
> An: users@wicket.apache.org
> Betreff: Re: Things I miss in Wicket
> >
> >
> > What I don't like ab
Hi Tobias,
I don't agree on a couple of points you made on Wicket.
Wicket is providing the GUI and you have to make sure your gluing to the backend
is as transparent as it can be. So, if you have your interfaces untouched, you
wont need to touch the Java code again for your 3-5 years. Also, wick
ing spaghetti.
**
Martin
>
>
>
> Original-Nachricht
>> Datum: Fri, 16 Jan 2009 06:31:39 +0200
>> Von: Martin Makundi
>> An: users@wicket.apache.org
>> Betreff: Re: Things I miss in Wicket
>
>> > 3. Pick up components automatically without needing to add t
> Von: Martin Makundi
> An: users@wicket.apache.org
> Betreff: Re: Things I miss in Wicket
> All you need is a RAD IDE that co-operates well with the typesafe wicket.
>
> **
> Martin
>
> 2009/1/16 Tobias Marx :
> > I think there already a lot of projects out there
>
>
> What I don't like about Wicket is, that it is like writing normal Java
> applications - although rich clients applications are being replaced with
> web-based solutions and there is a fundamental difference between
> web-applications and normal java applications. If you have a java
> applicat
thout having
to define them in the code or some xml.
Original-Nachricht
> Datum: Fri, 16 Jan 2009 06:31:39 +0200
> Von: Martin Makundi
> An: users@wicket.apache.org
> Betreff: Re: Things I miss in Wicket
> > 3. Pick up components automatically without nee
l
> changes in the core of some Java framework you do not wish to know in
> detail..
>
> So long...
>
> Toby
>
> Original-Nachricht
>> Datum: Thu, 15 Jan 2009 21:46:08 -0500
>> Von: Trevor Burnham
>> An: Tobias Marx
>> Betreff:
sh to know in detail..
So long...
Toby
Original-Nachricht
> Datum: Thu, 15 Jan 2009 21:46:08 -0500
> Von: Trevor Burnham
> An: Tobias Marx
> Betreff: Re: Things I miss in Wicket
> Hi Toby,
>
> I've been considering creating a new project that woul
> Ouch, that is ugly. Now I understand why it is deprecated.
It for sure is nothing meant to be used on a day-to-day basis, right. But there
are use cases where you're happy it exists.
Best regards, --- Jan.
-
To unsubscribe,
Jan Kriesten wrote:
just replace 'type' with 'class' and you're there. Also, any other attribute you
put into the wicket:component tag is looked a setter on the class for, so you
can pass parameters in from you html code.
Best regards, --- Jan.
Ouch, that is ugly. Now I understand why it is
Hi Erik,
> Yep, I did see that. However, it does not describe the type attribute
> Pills described:
just replace 'type' with 'class' and you're there. Also, any other attribute you
put into the wicket:component tag is looked a setter on the class for, so you
can pass parameters in from you html
Yep, I did see that. However, it does not describe the type attribute
Pills described:
Pills wrote:
3) may be a good improvement, maybe with a new wicket tag
(). let's see what think
core developpers
Jan Kriesten wrote
Hi Erik,
Can you point to a place where this is documented? Its not
Hi Erik,
> Can you point to a place where this is documented? Its not on
> http://cwiki.apache.org/WICKET/wickets-xhtml-tags.html.
actually, it is there. :)
---8<---
Element wicket:component
- Creates a Wicket component on the fly. Needs a class
attribute. Though this has been in wicket for a
Hi Jan,
Can you point to a place where this is documented? Its not on
http://cwiki.apache.org/WICKET/wickets-xhtml-tags.html.
Regards,
Erik.
Jan Kriesten wrote:
3) may be a good improvement, maybe with a new wicket tag
(). let's see what think
core developpers
hehe - that one alread
Sure! sorry, missed that one... Well, all requirements were already
implemented :D
If I were naughty, I would write "rtfm" ;)
Jan Kriesten wrote:
Hi Sébastien,
1) and 2) are already implemented, or something very close exists. 3)
may be a good improvement, maybe with a new wicket tag
().
Hi Sébastien,
> 1) and 2) are already implemented, or something very close exists. 3)
> may be a good improvement, maybe with a new wicket tag
> (). let's see what think
> core developpers
hehe - that one already exists, too! :D
Best regards, --- Jan.
--
> How are you envisioning this working from within an IDE? This sounds like
> an interesting feature to add.
Context-sensitive auto-complete, quickfix, ..., there are a lot of
examples of suitable functionalities in Eclipse, for example. I have
never implemented those, however.
We could start ga
How are you envisioning this working from within an IDE? This sounds like
an interesting feature to add.
On Thu, Jan 15, 2009 at 8:31 PM, Martin Makundi <
martin.maku...@koodaripalvelut.com> wrote:
> > 3. Pick up components automatically without needing to add them in the
> Java code:
> >
> > ad
> 3. Pick up components automatically without needing to add them in the Java
> code:
>
> add(new LastPostsPanel("lastPostsPanel"));
> add(new NewsPanel("newsPanel"));
>
> This could be matched automatically
This should be accomplished using and IDE, not by default. I would not
mind an IDE that c
Hi,
1) and 2) are already implemented, or something very close exists. 3)
may be a good improvement, maybe with a new wicket tag
(). let's see what think
core developpers
1) you have various way of altering tags and attributes:
attributemodifiers, attributeappenders, overriding oncomponentt
On Thu, Jan 15, 2009 at 1:44 PM, Tobias Marx wrote:
> Hi there!
>
> There are some things in Wicket I am missing and I think they could improve
> the framework a lot.
>
> But just some small background first:
>
> In my opinion the most important things in a web application are:
>
> - as few l
30 matches
Mail list logo
