Hey Juergen,
I totally agree with you that Wicket should 'force' you to write xhtml
compliant code. Maybe that will teach those lazy html-designers... ;)
Niels, in my opinion you you should maybe consider changing your code to
be xhtml compliant. Not only is it s much more readable, it is
Hi,
Erik, I agree with you: it seems like most BSCs (big slow companies)
don't care about that at all. Still I think - just like you - that they
are valid arguments and thus need to be mentioned.
Be the prophet! Make them care about it! :)
Additionally, presenting this stuff to a sales team
/06, Che Schneider [EMAIL PROTECTED] wrote:
Hi,
My vote goes to LGPL: not as restrictive as GPL but
preserves the gist
of it. :)
// Che
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Ted Roeloffzen
Sent: Tuesday
Hi Eelco,
I totally agree to you (*)-comment:
We are working on a project at the moment where almost exactly that is
happening. A collegue is creating all the markup while 'we Java
developers' (;) give it a life afterwards.
And yes, it works very smoothly and with success... :)
// Che
Hi,
My vote goes to LGPL: not as restrictive as GPL but preserves the gist
of it. :)
// Che
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Ted Roeloffzen
Sent: Tuesday, September 26, 2006 2:13 PM
To: wicket-user
Subject: [Wicket-user]
+1 because this actually _is_ a very important point.
// Che
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Ryan Sonnek
Sent: Tuesday, September 26, 2006 3:29 PM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Wicket
Hi Arseny,
One way is to markup your main template with wicket-tagged elements in
all the places where you can possibly have a control or frame. Then in
your business logic you replace that element either with nothing (an
empty component) or the panel you would like to have in the place.
guess the guys around here possibly know a
much better way...
// Che
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Che Schneider
Sent: Tuesday, September 19, 2006 3:11 PM
To: Ars; wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user
Hey Les,
For me code is like pictures, they speek for themselves.
Sorry, I probably was not clear enough about this: I totally agree with
that.
Actually, for me, looking at the code most of the time helps more than
any technichal explanation.
However, if I read a book on Wicket (or any other
Hey Igor,
Although I disagree about the 'real life' (that's what you have the
design for: to avoid the constant architecture change), you are right
that in a book it is a valid approach.
However, I very much dislike it unless you clearly state in the
beginning that you are gonna do it in a messy
. it mightve been better if karthik gave you a heads up
that there are better ways of doing this later on.
-Igor
On 9/15/06, Che Schneider [EMAIL PROTECTED] wrote:
Hey Igor,
Although I disagree about the 'real life' (that's what
you have the
design
except that i wouldnt consider a few printed pages of code a
complex example, but thats just me :)
Well, some of the examples are actually quite complex - if you are new
in Wicket. There are loads of IConverters and stuff that need to
register each other (chained) with the main application. It
the first HelloWorld class in the default package. It is
then much more evident to explain why one should not do this.
Pierre-Yves
Che Schneider a écrit :
Okay, understood. And you are right, there hopefullt (and luckily,
looking back at my code from former days :) always is a
progress
Hey,
I have to agree with Gavin: the book is indeed a bit rough.
For example, the auther takes loads of time to elaborate certain
'features' while others are being handled as if he expects the audience
to know what he is talking about.
The examples are imo completely useless in real life since
By the way:
There is a very nice introduction to Wicket 2.0 in the last chapters of
the book - I cannot wait to play around with that baby... :)
//Che
__
DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized
recipient only. If you are not the
in the beta
version I read. I guess that has changed or will change soon...
Yes, I have passed on the corrections to the publisher.
- Karthik
On 9/14/06, Che Schneider [EMAIL PROTECTED] wrote:
Hey,
I have to agree with Gavin: the book is indeed a bit rough.
For example, the auther
Hey,
At this stage of the project we are just researching which options
current popular CMS systems
I think you should first pick a target audience and then
model your CMS towards that group of users with their application.
Agree to disagree :)
The few stars in the flood of available CMS
); } }
or
add(new MyCustomPanel(panel) { void onclick() {
setResponsePage(new MyPage(some params)); } }
but to the panel its all the same.
-Igor
On 9/4/06, Che Schneider [EMAIL PROTECTED] wrote:
Hi all,
Is there a decent resource somewhere on how to do
things
Hi all,
Is there a decent resource somewhere on how to do things 'properly' (aka
nice and clean :) in wicket?
I can always think of quite a few ways to solve a problem but since I am
totally new to wicket I am not sure which way is the right one..
Example:
In a custom panel I want to create a
19 matches
Mail list logo
