You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Philippe Demaison <ph...@gmail.com> on 2013/01/22 11:24:29 UTC
documentation
Hi All,
As Gabor Friedrich from the FAO, we are in my company, L'Oreal, comparing
different web frameworks.
Apache Wicket may be the best framework, may be usefull for my company, I
don't know.
I don't know because there is no clear documentation for a good evaluation.
In fact the documentation is not good.
The documentation is not up to date, not to say obsolete, not well
organized and definitely not sexy.
Sorry to being rude, I know this is difficult to do, but this is a major
drawback when company and people evaluate Wicket.
Some articles are for 1.4 or 1.5, not many for 6
Some articles are redundant.
I am sure the folowing structure could be improved :
https://cwiki.apache.org/WICKET/framework-documentation.html is
https://cwiki.apache.org/WICKET/index.html
https://cwiki.apache.org/WICKET/documentation-index.html
The http://wicket.apache.org/ layout is good.
Why not reorganize the documentation with this layout ?
Managers want to see benefits, developpers want to learn fast(and have fun).
I tested the mentionned blogs on http://wicket.apache.org/meet/blogs.html
Here is what I found :
Chillenious! - Eelco Hillenius - http://chillenious.wordpress.com/
last update : 2008
Here be beasties - Al Maw - http://herebebeasties.com/
last update : 2009
Codierspiel - Nathan Hamblen (runs on Wicket) - http://code.technically.us/
no a single wicket post
Antwerkz - Justin Lee - http://antwerkz.com/wp/
empty
Geertjan - Geertjan Wielenga - http://blogs.sun.com/geertjan
http 404 !
Mystic Coders - Andrew Lombardi and
Wicket by Example - Community driven are pointing to the same address :
http://www.mysticcoders.com/blog/
For a wider adoption of Wicket,
Best regards to all of you
Philippe Demaison
Re: documentation
Posted by Kees van Dieren <in...@squins.com>.
Sorry for that, some good articles that might help you :
http://www.devproof.org/why_choose_apache_wicket
http://www.devproof.org/wicket_best_practice
2013/1/22 Philippe Demaison <ph...@gmail.com>
> Hi All,
>
> As Gabor Friedrich from the FAO, we are in my company, L'Oreal, comparing
> different web frameworks.
> Apache Wicket may be the best framework, may be usefull for my company, I
> don't know.
> I don't know because there is no clear documentation for a good evaluation.
>
> In fact the documentation is not good.
>
> The documentation is not up to date, not to say obsolete, not well
> organized and definitely not sexy.
> Sorry to being rude, I know this is difficult to do, but this is a major
> drawback when company and people evaluate Wicket.
>
> Some articles are for 1.4 or 1.5, not many for 6
> Some articles are redundant.
>
> I am sure the folowing structure could be improved :
> https://cwiki.apache.org/WICKET/framework-documentation.html is
> https://cwiki.apache.org/WICKET/index.html
> https://cwiki.apache.org/WICKET/documentation-index.html
>
> The http://wicket.apache.org/ layout is good.
> Why not reorganize the documentation with this layout ?
>
> Managers want to see benefits, developpers want to learn fast(and have
> fun).
>
>
> I tested the mentionned blogs on http://wicket.apache.org/meet/blogs.html
>
> Here is what I found :
>
> Chillenious! - Eelco Hillenius - http://chillenious.wordpress.com/
> last update : 2008
>
> Here be beasties - Al Maw - http://herebebeasties.com/
> last update : 2009
>
> Codierspiel - Nathan Hamblen (runs on Wicket) -
> http://code.technically.us/
> no a single wicket post
>
> Antwerkz - Justin Lee - http://antwerkz.com/wp/
> empty
>
> Geertjan - Geertjan Wielenga - http://blogs.sun.com/geertjan
> http 404 !
>
> Mystic Coders - Andrew Lombardi and
> Wicket by Example - Community driven are pointing to the same address :
> http://www.mysticcoders.com/blog/
>
>
> For a wider adoption of Wicket,
> Best regards to all of you
>
> Philippe Demaison
>
--
Best regards / Met vriendelijke groet,
Kees van Dieren
Squins IT Solutions BV
Oranjestraat 30
2983 HS Ridderkerk
The Netherlands
Mobile: +31 (0)6 30413841
www.squins.com
Chamber of commerce Rotterdam: 24435103
Re: documentation
Posted by Philippe Demaison <ph...@gmail.com>.
The community is very responsive.
Thanks you very much, the documentation will help us.
Philippe Demaison
2013/1/25 Martin Grigorov <mg...@apache.org>
> Hi,
>
> I just pushed a new branch named 'reference-guide' to our Git repo.
> It contains the setup to write documentation and include code samples from
> wicket-examples project.
> This is just the first step. It will receive more updates.
>
> You can see how it looks at:
> http://martin-g.github.com/wicket-reference-guide/index.html
>
> If you feel that you know some area of Wicket better please be welcome to
> contribute!
>
> For now I'm going to move some documentation from
> http://wicket.apache.org/learn and the Wiki to this reference guide.
>
> On Thu, Jan 24, 2013 at 3:08 PM, Andrea Del Bene <an.delbene@gmail.com
> >wrote:
>
> > For what it's worth :) I'm about to finish a free reference document for
> > Wicket 6. I've started to write it almost one and a half years ago and it
> > should be ready by the end of February.
> > The example code used in the document are hosted here
> > https://github.com/bitstorm/**Wicket-tutorial-examples<
> https://github.com/bitstorm/Wicket-tutorial-examples>
> >
> > This is great !
> >> I am looking forward to reading the new documentation.
> >>
> >> Best regards
> >> Phlippe
> >>
> >>
> >> 2013/1/23 Rob Schroeder <sc...@gmail.com>
> >>
> >> Hi all,
> >>>
> >>> On Tue, 22 Jan 2013 18:25:41 +0100, Guillaume Smet wrote:
> >>>
> >>> On Tue, Jan 22, 2013 at 5:53 PM, Philippe Demaison
> >>>> <ph...@gmail.com> wrote:
> >>>>
> >>>>> Are you kidding ?
> >>>>>
> >>>> First thing first, while everyone agrees that a good documentation is
> >>>> a good thing, you should consider that you don't pay anyone to write
> >>>> it.
> >>>>
> >>> On Tue, 22 Jan 2013 19:08:35 +0100, Thies Edeling wrote:
> >>>
> >>> Wicket is open source, if you feel that the documentation is lacking -
> >>>>
> >>> feel
> >>>
> >>>> free to contribute.
> >>>>
> >>> don't mean to offend anyone, but things like those are the least
> helpful
> >>> kind of answers possible. We all know Wicket is open source, we all
> know
> >>> what open source means, an we all know that we aren't paying anyone.
> >>> It's just that if someone had the resources to pay anyone or
> >>> significantly contribute to the documentation himself (*after* having
> >>> learned everything he'd need, and after doing so *without* a complete
> >>> reference), he'd probably not complain in the first place. More
> probable
> >>> is that he's already got a job to do himself and is just looking for
> the
> >>> best tool to do so.
> >>>
> >>> Of course, shouting abuse (not that I'd think anyone here did) at maybe
> >>> even unsalaried developers who are doing what they can doesn't help,
> >>> either.
> >>>
> >>> To add my experience to the subject, I bought the 'Wicket in Action'
> >>> book some time ago, and for my first steps with Wicket 6 I tried to
> >>> extract what I could from it and the Net.
> >>>
> >>> The problem is, just as Philippe said, much has changed between
> >>> versions, and it's not only that things I find sometimes don't apply
> >>> anymore, but, what's possibly worse, I can't even know whether code
> >>> examples I find still work until I tried them myself, as the changes
> >>> aren't really exhaustively documented and because, well, there is no
> >>> such thing as a Wicket 6 reference.
> >>>
> >>> As far as I am concerned, I'll keep trying to get into Wicket 6, though
> >>> - but that's something I'll be doing in my spare time, because I
> >>> probably won't ever see Wicket used at my main job, and so I can take
> my
> >>> time.
> >>>
> >>> Cheers,
> >>> Robert
> >>>
> >>>
> >>>
> >>>
> >>> ------------------------------**------------------------------**
> >>> ---------
> >>> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> users-unsubscribe@wicket.apache.org>
> >>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>
> >>>
> >>>
> >
> > ------------------------------**------------------------------**---------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> users-unsubscribe@wicket.apache.org>
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com <http://jweekend.com/>
>
Re: documentation
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
I just pushed a new branch named 'reference-guide' to our Git repo.
It contains the setup to write documentation and include code samples from
wicket-examples project.
This is just the first step. It will receive more updates.
You can see how it looks at:
http://martin-g.github.com/wicket-reference-guide/index.html
If you feel that you know some area of Wicket better please be welcome to
contribute!
For now I'm going to move some documentation from
http://wicket.apache.org/learn and the Wiki to this reference guide.
On Thu, Jan 24, 2013 at 3:08 PM, Andrea Del Bene <an...@gmail.com>wrote:
> For what it's worth :) I'm about to finish a free reference document for
> Wicket 6. I've started to write it almost one and a half years ago and it
> should be ready by the end of February.
> The example code used in the document are hosted here
> https://github.com/bitstorm/**Wicket-tutorial-examples<https://github.com/bitstorm/Wicket-tutorial-examples>
>
> This is great !
>> I am looking forward to reading the new documentation.
>>
>> Best regards
>> Phlippe
>>
>>
>> 2013/1/23 Rob Schroeder <sc...@gmail.com>
>>
>> Hi all,
>>>
>>> On Tue, 22 Jan 2013 18:25:41 +0100, Guillaume Smet wrote:
>>>
>>> On Tue, Jan 22, 2013 at 5:53 PM, Philippe Demaison
>>>> <ph...@gmail.com> wrote:
>>>>
>>>>> Are you kidding ?
>>>>>
>>>> First thing first, while everyone agrees that a good documentation is
>>>> a good thing, you should consider that you don't pay anyone to write
>>>> it.
>>>>
>>> On Tue, 22 Jan 2013 19:08:35 +0100, Thies Edeling wrote:
>>>
>>> Wicket is open source, if you feel that the documentation is lacking -
>>>>
>>> feel
>>>
>>>> free to contribute.
>>>>
>>> don't mean to offend anyone, but things like those are the least helpful
>>> kind of answers possible. We all know Wicket is open source, we all know
>>> what open source means, an we all know that we aren't paying anyone.
>>> It's just that if someone had the resources to pay anyone or
>>> significantly contribute to the documentation himself (*after* having
>>> learned everything he'd need, and after doing so *without* a complete
>>> reference), he'd probably not complain in the first place. More probable
>>> is that he's already got a job to do himself and is just looking for the
>>> best tool to do so.
>>>
>>> Of course, shouting abuse (not that I'd think anyone here did) at maybe
>>> even unsalaried developers who are doing what they can doesn't help,
>>> either.
>>>
>>> To add my experience to the subject, I bought the 'Wicket in Action'
>>> book some time ago, and for my first steps with Wicket 6 I tried to
>>> extract what I could from it and the Net.
>>>
>>> The problem is, just as Philippe said, much has changed between
>>> versions, and it's not only that things I find sometimes don't apply
>>> anymore, but, what's possibly worse, I can't even know whether code
>>> examples I find still work until I tried them myself, as the changes
>>> aren't really exhaustively documented and because, well, there is no
>>> such thing as a Wicket 6 reference.
>>>
>>> As far as I am concerned, I'll keep trying to get into Wicket 6, though
>>> - but that's something I'll be doing in my spare time, because I
>>> probably won't ever see Wicket used at my main job, and so I can take my
>>> time.
>>>
>>> Cheers,
>>> Robert
>>>
>>>
>>>
>>>
>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<us...@wicket.apache.org>
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<us...@wicket.apache.org>
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>
Re: documentation
Posted by Andrea Del Bene <an...@gmail.com>.
For what it's worth :) I'm about to finish a free reference document for
Wicket 6. I've started to write it almost one and a half years ago and
it should be ready by the end of February.
The example code used in the document are hosted here
https://github.com/bitstorm/Wicket-tutorial-examples
> This is great !
> I am looking forward to reading the new documentation.
>
> Best regards
> Phlippe
>
>
> 2013/1/23 Rob Schroeder <sc...@gmail.com>
>
>> Hi all,
>>
>> On Tue, 22 Jan 2013 18:25:41 +0100, Guillaume Smet wrote:
>>
>>> On Tue, Jan 22, 2013 at 5:53 PM, Philippe Demaison
>>> <ph...@gmail.com> wrote:
>>>> Are you kidding ?
>>> First thing first, while everyone agrees that a good documentation is
>>> a good thing, you should consider that you don't pay anyone to write
>>> it.
>> On Tue, 22 Jan 2013 19:08:35 +0100, Thies Edeling wrote:
>>
>>> Wicket is open source, if you feel that the documentation is lacking -
>> feel
>>> free to contribute.
>> don't mean to offend anyone, but things like those are the least helpful
>> kind of answers possible. We all know Wicket is open source, we all know
>> what open source means, an we all know that we aren't paying anyone.
>> It's just that if someone had the resources to pay anyone or
>> significantly contribute to the documentation himself (*after* having
>> learned everything he'd need, and after doing so *without* a complete
>> reference), he'd probably not complain in the first place. More probable
>> is that he's already got a job to do himself and is just looking for the
>> best tool to do so.
>>
>> Of course, shouting abuse (not that I'd think anyone here did) at maybe
>> even unsalaried developers who are doing what they can doesn't help,
>> either.
>>
>> To add my experience to the subject, I bought the 'Wicket in Action'
>> book some time ago, and for my first steps with Wicket 6 I tried to
>> extract what I could from it and the Net.
>>
>> The problem is, just as Philippe said, much has changed between
>> versions, and it's not only that things I find sometimes don't apply
>> anymore, but, what's possibly worse, I can't even know whether code
>> examples I find still work until I tried them myself, as the changes
>> aren't really exhaustively documented and because, well, there is no
>> such thing as a Wicket 6 reference.
>>
>> As far as I am concerned, I'll keep trying to get into Wicket 6, though
>> - but that's something I'll be doing in my spare time, because I
>> probably won't ever see Wicket used at my main job, and so I can take my
>> time.
>>
>> Cheers,
>> Robert
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: documentation
Posted by Philippe Demaison <ph...@gmail.com>.
This is great !
I am looking forward to reading the new documentation.
Best regards
Phlippe
2013/1/23 Rob Schroeder <sc...@gmail.com>
> Hi all,
>
> On Tue, 22 Jan 2013 18:25:41 +0100, Guillaume Smet wrote:
>
> > On Tue, Jan 22, 2013 at 5:53 PM, Philippe Demaison
> > <ph...@gmail.com> wrote:
> > > Are you kidding ?
> >
> > First thing first, while everyone agrees that a good documentation is
> > a good thing, you should consider that you don't pay anyone to write
> > it.
>
> On Tue, 22 Jan 2013 19:08:35 +0100, Thies Edeling wrote:
>
> > Wicket is open source, if you feel that the documentation is lacking -
> feel
> > free to contribute.
>
> don't mean to offend anyone, but things like those are the least helpful
> kind of answers possible. We all know Wicket is open source, we all know
> what open source means, an we all know that we aren't paying anyone.
> It's just that if someone had the resources to pay anyone or
> significantly contribute to the documentation himself (*after* having
> learned everything he'd need, and after doing so *without* a complete
> reference), he'd probably not complain in the first place. More probable
> is that he's already got a job to do himself and is just looking for the
> best tool to do so.
>
> Of course, shouting abuse (not that I'd think anyone here did) at maybe
> even unsalaried developers who are doing what they can doesn't help,
> either.
>
> To add my experience to the subject, I bought the 'Wicket in Action'
> book some time ago, and for my first steps with Wicket 6 I tried to
> extract what I could from it and the Net.
>
> The problem is, just as Philippe said, much has changed between
> versions, and it's not only that things I find sometimes don't apply
> anymore, but, what's possibly worse, I can't even know whether code
> examples I find still work until I tried them myself, as the changes
> aren't really exhaustively documented and because, well, there is no
> such thing as a Wicket 6 reference.
>
> As far as I am concerned, I'll keep trying to get into Wicket 6, though
> - but that's something I'll be doing in my spare time, because I
> probably won't ever see Wicket used at my main job, and so I can take my
> time.
>
> Cheers,
> Robert
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
RE: documentation
Posted by Paul Bors <pa...@bors.ws>.
If you're trying to compare Java webapp frameworks, take your pick:
http://wicket.apache.org/meet/introduction.html
Also see:
http://en.wikipedia.org/wiki/Comparison_of_web_application_frameworks
~ Thank you,
Paul Bors
-----Original Message-----
From: Guillaume Smet [mailto:guillaume.smet@gmail.com]
Sent: Tuesday, January 22, 2013 12:26 PM
To: users@wicket.apache.org
Subject: Re: documentation
Hi Philippe,
On Tue, Jan 22, 2013 at 5:53 PM, Philippe Demaison <ph...@gmail.com>
wrote:
> Are you kidding ?
First thing first, while everyone agrees that a good documentation is a good
thing, you should consider that you don't pay anyone to write it.
There are a couple of very good books about Wicket you can purchase at
Amazon.
And the Wicket examples library is really nice to understand how Wicket
works and understand the best practices and how you should build your
application.
It took me a couple of hours to start developing my first components with
Wicket, mainly by reading the examples. Probably less than the time you
spent writing your emails.
> http://www.playframework.org/documentation/2.0.4/Home
> http://tapestry.apache.org/documentation.html
I don't know these 2 frameworks and they might (or might not) have a better
documentation than Wicket. The quality of a documentation isn't measured by
the number of pages. You measure it by the time you spend learning the
framework and how useful it is.
> https://developers.google.com/web-toolkit/doc/latest/DevGuide
Well, while you might think at first glance GWT documentation is better,
you're definitely wrong. And, considering the number of misarchitectured GWT
applications I studied (and helped getting them
fixed) for our customers, I'm pretty sure it's not that easy to get it right
from the documentation.
> http://www.springsource.org/spring-framework#documentation
Spring is a framework. Compare with the Spring MVC documentation if you want
to compare Wicket's documentation with something. That said, I agree that
Spring MVC documentation is really good but what really helps to understand
the best practices is the sample applications developed by SpringSource.
Really try to start learning Wicket by using the available documentation and
especially http://www.wicket-library.com/wicket-examples/index.html and
you'll see that it's efficient and a good starting point to learn the
framework.
If you don't want to give it a try and see by yourself, well, it's your
choice.
But before complaining about the quality of the documentation available,
please consider reading it.
--
Guillaume
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: documentation
Posted by Rob Schroeder <sc...@gmail.com>.
Hi all,
On Tue, 22 Jan 2013 18:25:41 +0100, Guillaume Smet wrote:
> On Tue, Jan 22, 2013 at 5:53 PM, Philippe Demaison
> <ph...@gmail.com> wrote:
> > Are you kidding ?
>
> First thing first, while everyone agrees that a good documentation is
> a good thing, you should consider that you don't pay anyone to write
> it.
On Tue, 22 Jan 2013 19:08:35 +0100, Thies Edeling wrote:
> Wicket is open source, if you feel that the documentation is lacking - feel
> free to contribute.
don't mean to offend anyone, but things like those are the least helpful
kind of answers possible. We all know Wicket is open source, we all know
what open source means, an we all know that we aren't paying anyone.
It's just that if someone had the resources to pay anyone or
significantly contribute to the documentation himself (*after* having
learned everything he'd need, and after doing so *without* a complete
reference), he'd probably not complain in the first place. More probable
is that he's already got a job to do himself and is just looking for the
best tool to do so.
Of course, shouting abuse (not that I'd think anyone here did) at maybe
even unsalaried developers who are doing what they can doesn't help,
either.
To add my experience to the subject, I bought the 'Wicket in Action'
book some time ago, and for my first steps with Wicket 6 I tried to
extract what I could from it and the Net.
The problem is, just as Philippe said, much has changed between
versions, and it's not only that things I find sometimes don't apply
anymore, but, what's possibly worse, I can't even know whether code
examples I find still work until I tried them myself, as the changes
aren't really exhaustively documented and because, well, there is no
such thing as a Wicket 6 reference.
As far as I am concerned, I'll keep trying to get into Wicket 6, though
- but that's something I'll be doing in my spare time, because I
probably won't ever see Wicket used at my main job, and so I can take my
time.
Cheers,
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: documentation
Posted by Guillaume Smet <gu...@gmail.com>.
Hi Philippe,
On Tue, Jan 22, 2013 at 5:53 PM, Philippe Demaison
<ph...@gmail.com> wrote:
> Are you kidding ?
First thing first, while everyone agrees that a good documentation is
a good thing, you should consider that you don't pay anyone to write
it.
There are a couple of very good books about Wicket you can purchase at Amazon.
And the Wicket examples library is really nice to understand how
Wicket works and understand the best practices and how you should
build your application.
It took me a couple of hours to start developing my first components
with Wicket, mainly by reading the examples. Probably less than the
time you spent writing your emails.
> http://www.playframework.org/documentation/2.0.4/Home
> http://tapestry.apache.org/documentation.html
I don't know these 2 frameworks and they might (or might not) have a
better documentation than Wicket. The quality of a documentation isn't
measured by the number of pages. You measure it by the time you spend
learning the framework and how useful it is.
> https://developers.google.com/web-toolkit/doc/latest/DevGuide
Well, while you might think at first glance GWT documentation is
better, you're definitely wrong. And, considering the number of
misarchitectured GWT applications I studied (and helped getting them
fixed) for our customers, I'm pretty sure it's not that easy to get it
right from the documentation.
> http://www.springsource.org/spring-framework#documentation
Spring is a framework. Compare with the Spring MVC documentation if
you want to compare Wicket's documentation with something. That said,
I agree that Spring MVC documentation is really good but what really
helps to understand the best practices is the sample applications
developed by SpringSource.
Really try to start learning Wicket by using the available
documentation and especially
http://www.wicket-library.com/wicket-examples/index.html and you'll
see that it's efficient and a good starting point to learn the
framework.
If you don't want to give it a try and see by yourself, well, it's your choice.
But before complaining about the quality of the documentation
available, please consider reading it.
--
Guillaume
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: documentation
Posted by Paul Bors <pa...@bors.ws>.
If you're interested in learning Wicket, see the Learn section on the
project's home page at:
http://wicket.apache.org/
It has its own Books link:
http://wicket.apache.org/learn/books/
~ Thank you,
Paul Bors
On Tue, Jan 22, 2013 at 12:06 PM, Ondrej Zizka <oz...@redhat.com> wrote:
> Hi Philippe,
>
> no, my suggestions were rather for learning wicket.
>
> However it's not quite easy to "evaluate" something you don't have
> knowledge of.
> At first glance, Wicket may seem quite verbose on Java side.
> I personally didn't like it for the first time. But once I understood the
> basic concepts, it started to make sense and I decided to make it my #1
> framework.
>
> The book from 2009 is really quick to read, and will introduce the basic
> concepts which did not change much since 2009.
> I think it's enough for evaluation.
> BTW, see JSF - spec didn't change since 2009. See Spring - books from
> 2007 still apply. Etc.
>
>
> Ondra
>
>
>
>
> On 01/22/2013 05:53 PM, Philippe Demaison wrote:
>
>> Hi Ondra and Kees,
>>
>> Are you kidding ?
>>
>> Are you saying that I need to
>>
>> - read a book released in 2009 covering wicket 1.3 ?
>> - read http://www.wicket-library.com/**wicket-examples/index.html<http://www.wicket-library.com/wicket-examples/index.html>(for which wicket version ? )
>> - read the Wicket Cookbook
>> - read the migration from 1.x to 1.5 https://cwiki.apache.org/**
>> WICKET/migration-to-wicket-15.**html<https://cwiki.apache.org/WICKET/migration-to-wicket-15.html>
>> - read the migration from 1.5 to 1.6 https://cwiki.apache.org/**
>> WICKET/migration-to-wicket-60.**html<https://cwiki.apache.org/WICKET/migration-to-wicket-60.html>
>>
>> to understand what are the Wicket's benefits and write a POC ?
>>
>>
>> Are you saying that I need to google to read the best practices ?
>>
>> You know that framework adoption is linked to good documentation.
>> Not only of course (quality are community are equally important) but
>> documentation is essential.
>>
>> For example, I find these documentations much more appealing
>>
>> http://www.playframework.org/**documentation/2.0.4/Home<http://www.playframework.org/documentation/2.0.4/Home>
>> http://tapestry.apache.org/**documentation.html<http://tapestry.apache.org/documentation.html>
>> https://developers.google.com/**web-toolkit/doc/latest/**DevGuide<https://developers.google.com/web-toolkit/doc/latest/DevGuide>
>> http://www.springsource.org/**spring-framework#documentation<http://www.springsource.org/spring-framework#documentation>
>>
>> Don't you ?
>>
>> Philippe
>>
>> 2013/1/22 Ondrej Zizka <ozizka@redhat.com <ma...@redhat.com>>
>>
>>
>> Hi Phillipe,
>>
>> you're right, the documentation deserves improvements.
>>
>> I would recommend you to start with the Wicket in Action book.
>> That will give you the basic concepts of Wicket.
>> Then continue with the examples from
>> http://www.wicket-library.com/**wicket-examples/index.html<http://www.wicket-library.com/wicket-examples/index.html>. That
>> will enforce what you learned in the book, and show more tricks.
>> Then go through the Wicket Cookbook. That is a collection of
>> solutions and best practices for common tasks.
>> Then skim through
>> https://cwiki.apache.org/**WICKET/migration-to-wicket-15.**html<https://cwiki.apache.org/WICKET/migration-to-wicket-15.html>
>> and https://cwiki.apache.org/**WICKET/migration-to-wicket-60.**html<https://cwiki.apache.org/WICKET/migration-to-wicket-60.html>.
>>
>>
>> It is quite easy to create non-ajax websites. I only have
>> dificulties once it gets to Ajax.
>> In such cases, this mailing list is very useful, and also
>> stackoverflow and the multitude of blogs.
>>
>> Not sure what are your other options, but e.g. I prefer Wicket
>> over JSF.
>> Even big JSF fans claim that "JSF is marginally better".
>>
>> And last thing, I would recommend to try Wicket in combination
>> with JBoss AS 7, which made my development quick and easy -
>> redeployment in 3 seconds, restart in 5 seconds, CDI, JPA and JAAS
>> at hand, the Infinispan cache, easy management, ...
>>
>> my2c,
>> Ondra
>>
>>
>>
>>
>> On 01/22/2013 11:24 AM, Philippe Demaison wrote:
>>
>> Hi All,
>>
>> As Gabor Friedrich from the FAO, we are in my company,
>> L'Oreal, comparing
>> different web frameworks.
>> Apache Wicket may be the best framework, may be usefull for my
>> company, I
>> don't know.
>> I don't know because there is no clear documentation for a
>> good evaluation.
>>
>> In fact the documentation is not good.
>>
>> The documentation is not up to date, not to say obsolete, not well
>> organized and definitely not sexy.
>> Sorry to being rude, I know this is difficult to do, but this
>> is a major
>> drawback when company and people evaluate Wicket.
>>
>> Some articles are for 1.4 or 1.5, not many for 6
>> Some articles are redundant.
>>
>> I am sure the folowing structure could be improved :
>> https://cwiki.apache.org/**WICKET/framework-**documentation.html<https://cwiki.apache.org/WICKET/framework-documentation.html>is
>> https://cwiki.apache.org/**WICKET/index.html<https://cwiki.apache.org/WICKET/index.html>
>>
>> https://cwiki.apache.org/**WICKET/documentation-index.**html<https://cwiki.apache.org/WICKET/documentation-index.html>
>>
>> The http://wicket.apache.org/ layout is good.
>> Why not reorganize the documentation with this layout ?
>>
>> Managers want to see benefits, developpers want to learn
>> fast(and have fun).
>>
>>
>> I tested the mentionned blogs on
>> http://wicket.apache.org/meet/**blogs.html<http://wicket.apache.org/meet/blogs.html>
>>
>> Here is what I found :
>>
>> Chillenious! - Eelco Hillenius - http://chillenious.wordpress.**
>> com/ <http://chillenious.wordpress.com/>
>>
>> last update : 2008
>>
>> Here be beasties - Al Maw - http://herebebeasties.com/
>> last update : 2009
>>
>> Codierspiel - Nathan Hamblen (runs on Wicket) -
>> http://code.technically.us/
>> no a single wicket post
>>
>> Antwerkz - Justin Lee - http://antwerkz.com/wp/
>> empty
>>
>> Geertjan - Geertjan Wielenga - http://blogs.sun.com/geertjan
>> http 404 !
>>
>> Mystic Coders - Andrew Lombardi and
>> Wicket by Example - Community driven are pointing to the same
>> address :
>> http://www.mysticcoders.com/**blog/<http://www.mysticcoders.com/blog/>
>>
>>
>> For a wider adoption of Wicket,
>> Best regards to all of you
>>
>> Philippe Demaison
>>
>>
>>
>>
>
Re: documentation
Posted by Ondrej Zizka <oz...@redhat.com>.
Hi Philippe,
no, my suggestions were rather for learning wicket.
However it's not quite easy to "evaluate" something you don't have
knowledge of.
At first glance, Wicket may seem quite verbose on Java side.
I personally didn't like it for the first time. But once I understood
the basic concepts, it started to make sense and I decided to make it my
#1 framework.
The book from 2009 is really quick to read, and will introduce the basic
concepts which did not change much since 2009.
I think it's enough for evaluation.
BTW, see JSF - spec didn't change since 2009. See Spring - books from
2007 still apply. Etc.
Ondra
On 01/22/2013 05:53 PM, Philippe Demaison wrote:
> Hi Ondra and Kees,
>
> Are you kidding ?
>
> Are you saying that I need to
>
> - read a book released in 2009 covering wicket 1.3 ?
> - read http://www.wicket-library.com/wicket-examples/index.html (for
> which wicket version ? )
> - read the Wicket Cookbook
> - read the migration from 1.x to 1.5
> https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
> - read the migration from 1.5 to 1.6
> https://cwiki.apache.org/WICKET/migration-to-wicket-60.html
>
> to understand what are the Wicket's benefits and write a POC ?
>
>
> Are you saying that I need to google to read the best practices ?
>
> You know that framework adoption is linked to good documentation.
> Not only of course (quality are community are equally important) but
> documentation is essential.
>
> For example, I find these documentations much more appealing
>
> http://www.playframework.org/documentation/2.0.4/Home
> http://tapestry.apache.org/documentation.html
> https://developers.google.com/web-toolkit/doc/latest/DevGuide
> http://www.springsource.org/spring-framework#documentation
>
> Don't you ?
>
> Philippe
>
> 2013/1/22 Ondrej Zizka <ozizka@redhat.com <ma...@redhat.com>>
>
> Hi Phillipe,
>
> you're right, the documentation deserves improvements.
>
> I would recommend you to start with the Wicket in Action book.
> That will give you the basic concepts of Wicket.
> Then continue with the examples from
> http://www.wicket-library.com/wicket-examples/index.html . That
> will enforce what you learned in the book, and show more tricks.
> Then go through the Wicket Cookbook. That is a collection of
> solutions and best practices for common tasks.
> Then skim through
> https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
> and https://cwiki.apache.org/WICKET/migration-to-wicket-60.html .
>
> It is quite easy to create non-ajax websites. I only have
> dificulties once it gets to Ajax.
> In such cases, this mailing list is very useful, and also
> stackoverflow and the multitude of blogs.
>
> Not sure what are your other options, but e.g. I prefer Wicket
> over JSF.
> Even big JSF fans claim that "JSF is marginally better".
>
> And last thing, I would recommend to try Wicket in combination
> with JBoss AS 7, which made my development quick and easy -
> redeployment in 3 seconds, restart in 5 seconds, CDI, JPA and JAAS
> at hand, the Infinispan cache, easy management, ...
>
> my2c,
> Ondra
>
>
>
>
> On 01/22/2013 11:24 AM, Philippe Demaison wrote:
>
> Hi All,
>
> As Gabor Friedrich from the FAO, we are in my company,
> L'Oreal, comparing
> different web frameworks.
> Apache Wicket may be the best framework, may be usefull for my
> company, I
> don't know.
> I don't know because there is no clear documentation for a
> good evaluation.
>
> In fact the documentation is not good.
>
> The documentation is not up to date, not to say obsolete, not well
> organized and definitely not sexy.
> Sorry to being rude, I know this is difficult to do, but this
> is a major
> drawback when company and people evaluate Wicket.
>
> Some articles are for 1.4 or 1.5, not many for 6
> Some articles are redundant.
>
> I am sure the folowing structure could be improved :
> https://cwiki.apache.org/WICKET/framework-documentation.html is
> https://cwiki.apache.org/WICKET/index.html
> https://cwiki.apache.org/WICKET/documentation-index.html
>
> The http://wicket.apache.org/ layout is good.
> Why not reorganize the documentation with this layout ?
>
> Managers want to see benefits, developpers want to learn
> fast(and have fun).
>
>
> I tested the mentionned blogs on
> http://wicket.apache.org/meet/blogs.html
>
> Here is what I found :
>
> Chillenious! - Eelco Hillenius - http://chillenious.wordpress.com/
> last update : 2008
>
> Here be beasties - Al Maw - http://herebebeasties.com/
> last update : 2009
>
> Codierspiel - Nathan Hamblen (runs on Wicket) -
> http://code.technically.us/
> no a single wicket post
>
> Antwerkz - Justin Lee - http://antwerkz.com/wp/
> empty
>
> Geertjan - Geertjan Wielenga - http://blogs.sun.com/geertjan
> http 404 !
>
> Mystic Coders - Andrew Lombardi and
> Wicket by Example - Community driven are pointing to the same
> address :
> http://www.mysticcoders.com/blog/
>
>
> For a wider adoption of Wicket,
> Best regards to all of you
>
> Philippe Demaison
>
>
>
Re: documentation
Posted by Andy Van Den Heuvel <an...@gmail.com>.
Projects like Springframework use docbook. It's really nice,
You put all documentation in xml files which are in the scm and when you
release it, you have documentation per release.
On Wed, Jan 23, 2013 at 12:26 PM, Martin Grigorov <mg...@apache.org>wrote:
> Hi,
>
>
> On Wed, Jan 23, 2013 at 12:36 PM, Philippe Demaison
> <ph...@gmail.com>wrote:
>
> > If I had your knowledge and more time (project manager), I wish I could
> > help.
> >
>
> Many people have said this...
>
> But I know exactly what you mean about the missing reference.
> I have an idea to start writing a reference guide that will explain the
> topics I'm most acquaint with.
> I'll use http://sphinx-doc.org/ because it supports an easy way to embed
> code snippets from other Maven modules - wicket-examples. So the code
> examples will evolve with the framework.
> Stay tuned!
>
>
> >
> > Best regards
> > Philippe
> >
> >
> > 2013/1/22 Thies Edeling <th...@rrm.net>
> >
> > > Wicket is open source, if you feel that the documentation is lacking -
> > feel
> > > free to contribute.
> > > On Jan 22, 2013 5:54 PM, "Philippe Demaison" <ph...@gmail.com>
> > > wrote:
> > >
> > > > Hi Ondra and Kees,
> > > >
> > > > Are you kidding ?
> > > >
> > > > Are you saying that I need to
> > > >
> > > > - read a book released in 2009 covering wicket 1.3 ?
> > > > - read http://www.wicket-library.com/wicket-examples/index.html (for
> > > which
> > > > wicket version ? )
> > > > - read the Wicket Cookbook
> > > > - read the migration from 1.x to 1.5
> > > > https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
> > > > - read the migration from 1.5 to 1.6
> > > > https://cwiki.apache.org/WICKET/migration-to-wicket-60.html
> > > >
> > > > to understand what are the Wicket's benefits and write a POC ?
> > > >
> > > >
> > > > Are you saying that I need to google to read the best practices ?
> > > >
> > > > You know that framework adoption is linked to good documentation.
> > > > Not only of course (quality are community are equally important) but
> > > > documentation is essential.
> > > >
> > > > For example, I find these documentations much more appealing
> > > >
> > > > http://www.playframework.org/documentation/2.0.4/Home
> > > > http://tapestry.apache.org/documentation.html
> > > > https://developers.google.com/web-toolkit/doc/latest/DevGuide
> > > > http://www.springsource.org/spring-framework#documentation
> > > >
> > > > Don't you ?
> > > >
> > > > Philippe
> > > >
> > > > 2013/1/22 Ondrej Zizka <oz...@redhat.com>
> > > >
> > > > > Hi Phillipe,
> > > > >
> > > > > you're right, the documentation deserves improvements.
> > > > >
> > > > > I would recommend you to start with the Wicket in Action book. That
> > > will
> > > > > give you the basic concepts of Wicket.
> > > > > Then continue with the examples from
> > http://www.wicket-library.com/**
> > > > > wicket-examples/index.html<
> > > > http://www.wicket-library.com/wicket-examples/index.html>. That will
> > > > enforce what you learned in the book, and show more tricks.
> > > > > Then go through the Wicket Cookbook. That is a collection of
> > solutions
> > > > and
> > > > > best practices for common tasks.
> > > > > Then skim through https://cwiki.apache.org/**
> > > > > WICKET/migration-to-wicket-15.**html<
> > > > https://cwiki.apache.org/WICKET/migration-to-wicket-15.html>
> > > > > and
> https://cwiki.apache.org/**WICKET/migration-to-wicket-60.**html<
> > > > https://cwiki.apache.org/WICKET/migration-to-wicket-60.html>.
> > > > >
> > > > > It is quite easy to create non-ajax websites. I only have
> dificulties
> > > > once
> > > > > it gets to Ajax.
> > > > > In such cases, this mailing list is very useful, and also
> > stackoverflow
> > > > > and the multitude of blogs.
> > > > >
> > > > > Not sure what are your other options, but e.g. I prefer Wicket over
> > > JSF.
> > > > > Even big JSF fans claim that "JSF is marginally better".
> > > > >
> > > > > And last thing, I would recommend to try Wicket in combination with
> > > JBoss
> > > > > AS 7, which made my development quick and easy - redeployment in 3
> > > > seconds,
> > > > > restart in 5 seconds, CDI, JPA and JAAS at hand, the Infinispan
> > cache,
> > > > easy
> > > > > management, ...
> > > > >
> > > > > my2c,
> > > > > Ondra
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 01/22/2013 11:24 AM, Philippe Demaison wrote:
> > > > >
> > > > >> Hi All,
> > > > >>
> > > > >> As Gabor Friedrich from the FAO, we are in my company, L'Oreal,
> > > > comparing
> > > > >> different web frameworks.
> > > > >> Apache Wicket may be the best framework, may be usefull for my
> > > company,
> > > > I
> > > > >> don't know.
> > > > >> I don't know because there is no clear documentation for a good
> > > > >> evaluation.
> > > > >>
> > > > >> In fact the documentation is not good.
> > > > >>
> > > > >> The documentation is not up to date, not to say obsolete, not well
> > > > >> organized and definitely not sexy.
> > > > >> Sorry to being rude, I know this is difficult to do, but this is a
> > > major
> > > > >> drawback when company and people evaluate Wicket.
> > > > >>
> > > > >> Some articles are for 1.4 or 1.5, not many for 6
> > > > >> Some articles are redundant.
> > > > >>
> > > > >> I am sure the folowing structure could be improved :
> > > > >> https://cwiki.apache.org/**WICKET/framework-**documentation.html<
> > > > https://cwiki.apache.org/WICKET/framework-documentation.html>is
> > > > >> https://cwiki.apache.org/**WICKET/index.html<
> > > > https://cwiki.apache.org/WICKET/index.html>
> > > > >> https://cwiki.apache.org/**WICKET/documentation-index.**html<
> > > > https://cwiki.apache.org/WICKET/documentation-index.html>
> > > > >>
> > > > >> The http://wicket.apache.org/ layout is good.
> > > > >> Why not reorganize the documentation with this layout ?
> > > > >>
> > > > >> Managers want to see benefits, developpers want to learn fast(and
> > have
> > > > >> fun).
> > > > >>
> > > > >>
> > > > >> I tested the mentionned blogs on http://wicket.apache.org/meet/**
> > > > >> blogs.html <http://wicket.apache.org/meet/blogs.html>
> > > > >>
> > > > >> Here is what I found :
> > > > >>
> > > > >> Chillenious! - Eelco Hillenius - http://chillenious.wordpress.
> > **com/<
> > > > http://chillenious.wordpress.com/>
> > > > >> last update : 2008
> > > > >>
> > > > >> Here be beasties - Al Maw - http://herebebeasties.com/
> > > > >> last update : 2009
> > > > >>
> > > > >> Codierspiel - Nathan Hamblen (runs on Wicket) -
> > > > >> http://code.technically.us/
> > > > >> no a single wicket post
> > > > >>
> > > > >> Antwerkz - Justin Lee - http://antwerkz.com/wp/
> > > > >> empty
> > > > >>
> > > > >> Geertjan - Geertjan Wielenga - http://blogs.sun.com/geertjan
> > > > >> http 404 !
> > > > >>
> > > > >> Mystic Coders - Andrew Lombardi and
> > > > >> Wicket by Example - Community driven are pointing to the same
> > address
> > > :
> > > > >> http://www.mysticcoders.com/**blog/ <
> > > http://www.mysticcoders.com/blog/>
> > > > >>
> > > > >>
> > > > >> For a wider adoption of Wicket,
> > > > >> Best regards to all of you
> > > > >>
> > > > >> Philippe Demaison
> > > > >>
> > > > >>
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com <http://jweekend.com/>
>
Re: documentation
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
On Wed, Jan 23, 2013 at 12:36 PM, Philippe Demaison
<ph...@gmail.com>wrote:
> If I had your knowledge and more time (project manager), I wish I could
> help.
>
Many people have said this...
But I know exactly what you mean about the missing reference.
I have an idea to start writing a reference guide that will explain the
topics I'm most acquaint with.
I'll use http://sphinx-doc.org/ because it supports an easy way to embed
code snippets from other Maven modules - wicket-examples. So the code
examples will evolve with the framework.
Stay tuned!
>
> Best regards
> Philippe
>
>
> 2013/1/22 Thies Edeling <th...@rrm.net>
>
> > Wicket is open source, if you feel that the documentation is lacking -
> feel
> > free to contribute.
> > On Jan 22, 2013 5:54 PM, "Philippe Demaison" <ph...@gmail.com>
> > wrote:
> >
> > > Hi Ondra and Kees,
> > >
> > > Are you kidding ?
> > >
> > > Are you saying that I need to
> > >
> > > - read a book released in 2009 covering wicket 1.3 ?
> > > - read http://www.wicket-library.com/wicket-examples/index.html (for
> > which
> > > wicket version ? )
> > > - read the Wicket Cookbook
> > > - read the migration from 1.x to 1.5
> > > https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
> > > - read the migration from 1.5 to 1.6
> > > https://cwiki.apache.org/WICKET/migration-to-wicket-60.html
> > >
> > > to understand what are the Wicket's benefits and write a POC ?
> > >
> > >
> > > Are you saying that I need to google to read the best practices ?
> > >
> > > You know that framework adoption is linked to good documentation.
> > > Not only of course (quality are community are equally important) but
> > > documentation is essential.
> > >
> > > For example, I find these documentations much more appealing
> > >
> > > http://www.playframework.org/documentation/2.0.4/Home
> > > http://tapestry.apache.org/documentation.html
> > > https://developers.google.com/web-toolkit/doc/latest/DevGuide
> > > http://www.springsource.org/spring-framework#documentation
> > >
> > > Don't you ?
> > >
> > > Philippe
> > >
> > > 2013/1/22 Ondrej Zizka <oz...@redhat.com>
> > >
> > > > Hi Phillipe,
> > > >
> > > > you're right, the documentation deserves improvements.
> > > >
> > > > I would recommend you to start with the Wicket in Action book. That
> > will
> > > > give you the basic concepts of Wicket.
> > > > Then continue with the examples from
> http://www.wicket-library.com/**
> > > > wicket-examples/index.html<
> > > http://www.wicket-library.com/wicket-examples/index.html>. That will
> > > enforce what you learned in the book, and show more tricks.
> > > > Then go through the Wicket Cookbook. That is a collection of
> solutions
> > > and
> > > > best practices for common tasks.
> > > > Then skim through https://cwiki.apache.org/**
> > > > WICKET/migration-to-wicket-15.**html<
> > > https://cwiki.apache.org/WICKET/migration-to-wicket-15.html>
> > > > and https://cwiki.apache.org/**WICKET/migration-to-wicket-60.**html<
> > > https://cwiki.apache.org/WICKET/migration-to-wicket-60.html>.
> > > >
> > > > It is quite easy to create non-ajax websites. I only have dificulties
> > > once
> > > > it gets to Ajax.
> > > > In such cases, this mailing list is very useful, and also
> stackoverflow
> > > > and the multitude of blogs.
> > > >
> > > > Not sure what are your other options, but e.g. I prefer Wicket over
> > JSF.
> > > > Even big JSF fans claim that "JSF is marginally better".
> > > >
> > > > And last thing, I would recommend to try Wicket in combination with
> > JBoss
> > > > AS 7, which made my development quick and easy - redeployment in 3
> > > seconds,
> > > > restart in 5 seconds, CDI, JPA and JAAS at hand, the Infinispan
> cache,
> > > easy
> > > > management, ...
> > > >
> > > > my2c,
> > > > Ondra
> > > >
> > > >
> > > >
> > > >
> > > > On 01/22/2013 11:24 AM, Philippe Demaison wrote:
> > > >
> > > >> Hi All,
> > > >>
> > > >> As Gabor Friedrich from the FAO, we are in my company, L'Oreal,
> > > comparing
> > > >> different web frameworks.
> > > >> Apache Wicket may be the best framework, may be usefull for my
> > company,
> > > I
> > > >> don't know.
> > > >> I don't know because there is no clear documentation for a good
> > > >> evaluation.
> > > >>
> > > >> In fact the documentation is not good.
> > > >>
> > > >> The documentation is not up to date, not to say obsolete, not well
> > > >> organized and definitely not sexy.
> > > >> Sorry to being rude, I know this is difficult to do, but this is a
> > major
> > > >> drawback when company and people evaluate Wicket.
> > > >>
> > > >> Some articles are for 1.4 or 1.5, not many for 6
> > > >> Some articles are redundant.
> > > >>
> > > >> I am sure the folowing structure could be improved :
> > > >> https://cwiki.apache.org/**WICKET/framework-**documentation.html<
> > > https://cwiki.apache.org/WICKET/framework-documentation.html>is
> > > >> https://cwiki.apache.org/**WICKET/index.html<
> > > https://cwiki.apache.org/WICKET/index.html>
> > > >> https://cwiki.apache.org/**WICKET/documentation-index.**html<
> > > https://cwiki.apache.org/WICKET/documentation-index.html>
> > > >>
> > > >> The http://wicket.apache.org/ layout is good.
> > > >> Why not reorganize the documentation with this layout ?
> > > >>
> > > >> Managers want to see benefits, developpers want to learn fast(and
> have
> > > >> fun).
> > > >>
> > > >>
> > > >> I tested the mentionned blogs on http://wicket.apache.org/meet/**
> > > >> blogs.html <http://wicket.apache.org/meet/blogs.html>
> > > >>
> > > >> Here is what I found :
> > > >>
> > > >> Chillenious! - Eelco Hillenius - http://chillenious.wordpress.
> **com/<
> > > http://chillenious.wordpress.com/>
> > > >> last update : 2008
> > > >>
> > > >> Here be beasties - Al Maw - http://herebebeasties.com/
> > > >> last update : 2009
> > > >>
> > > >> Codierspiel - Nathan Hamblen (runs on Wicket) -
> > > >> http://code.technically.us/
> > > >> no a single wicket post
> > > >>
> > > >> Antwerkz - Justin Lee - http://antwerkz.com/wp/
> > > >> empty
> > > >>
> > > >> Geertjan - Geertjan Wielenga - http://blogs.sun.com/geertjan
> > > >> http 404 !
> > > >>
> > > >> Mystic Coders - Andrew Lombardi and
> > > >> Wicket by Example - Community driven are pointing to the same
> address
> > :
> > > >> http://www.mysticcoders.com/**blog/ <
> > http://www.mysticcoders.com/blog/>
> > > >>
> > > >>
> > > >> For a wider adoption of Wicket,
> > > >> Best regards to all of you
> > > >>
> > > >> Philippe Demaison
> > > >>
> > > >>
> > > >
> > >
> >
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>
Re: documentation
Posted by Philippe Demaison <ph...@gmail.com>.
If I had your knowledge and more time (project manager), I wish I could
help.
Best regards
Philippe
2013/1/22 Thies Edeling <th...@rrm.net>
> Wicket is open source, if you feel that the documentation is lacking - feel
> free to contribute.
> On Jan 22, 2013 5:54 PM, "Philippe Demaison" <ph...@gmail.com>
> wrote:
>
> > Hi Ondra and Kees,
> >
> > Are you kidding ?
> >
> > Are you saying that I need to
> >
> > - read a book released in 2009 covering wicket 1.3 ?
> > - read http://www.wicket-library.com/wicket-examples/index.html (for
> which
> > wicket version ? )
> > - read the Wicket Cookbook
> > - read the migration from 1.x to 1.5
> > https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
> > - read the migration from 1.5 to 1.6
> > https://cwiki.apache.org/WICKET/migration-to-wicket-60.html
> >
> > to understand what are the Wicket's benefits and write a POC ?
> >
> >
> > Are you saying that I need to google to read the best practices ?
> >
> > You know that framework adoption is linked to good documentation.
> > Not only of course (quality are community are equally important) but
> > documentation is essential.
> >
> > For example, I find these documentations much more appealing
> >
> > http://www.playframework.org/documentation/2.0.4/Home
> > http://tapestry.apache.org/documentation.html
> > https://developers.google.com/web-toolkit/doc/latest/DevGuide
> > http://www.springsource.org/spring-framework#documentation
> >
> > Don't you ?
> >
> > Philippe
> >
> > 2013/1/22 Ondrej Zizka <oz...@redhat.com>
> >
> > > Hi Phillipe,
> > >
> > > you're right, the documentation deserves improvements.
> > >
> > > I would recommend you to start with the Wicket in Action book. That
> will
> > > give you the basic concepts of Wicket.
> > > Then continue with the examples from http://www.wicket-library.com/**
> > > wicket-examples/index.html<
> > http://www.wicket-library.com/wicket-examples/index.html>. That will
> > enforce what you learned in the book, and show more tricks.
> > > Then go through the Wicket Cookbook. That is a collection of solutions
> > and
> > > best practices for common tasks.
> > > Then skim through https://cwiki.apache.org/**
> > > WICKET/migration-to-wicket-15.**html<
> > https://cwiki.apache.org/WICKET/migration-to-wicket-15.html>
> > > and https://cwiki.apache.org/**WICKET/migration-to-wicket-60.**html<
> > https://cwiki.apache.org/WICKET/migration-to-wicket-60.html>.
> > >
> > > It is quite easy to create non-ajax websites. I only have dificulties
> > once
> > > it gets to Ajax.
> > > In such cases, this mailing list is very useful, and also stackoverflow
> > > and the multitude of blogs.
> > >
> > > Not sure what are your other options, but e.g. I prefer Wicket over
> JSF.
> > > Even big JSF fans claim that "JSF is marginally better".
> > >
> > > And last thing, I would recommend to try Wicket in combination with
> JBoss
> > > AS 7, which made my development quick and easy - redeployment in 3
> > seconds,
> > > restart in 5 seconds, CDI, JPA and JAAS at hand, the Infinispan cache,
> > easy
> > > management, ...
> > >
> > > my2c,
> > > Ondra
> > >
> > >
> > >
> > >
> > > On 01/22/2013 11:24 AM, Philippe Demaison wrote:
> > >
> > >> Hi All,
> > >>
> > >> As Gabor Friedrich from the FAO, we are in my company, L'Oreal,
> > comparing
> > >> different web frameworks.
> > >> Apache Wicket may be the best framework, may be usefull for my
> company,
> > I
> > >> don't know.
> > >> I don't know because there is no clear documentation for a good
> > >> evaluation.
> > >>
> > >> In fact the documentation is not good.
> > >>
> > >> The documentation is not up to date, not to say obsolete, not well
> > >> organized and definitely not sexy.
> > >> Sorry to being rude, I know this is difficult to do, but this is a
> major
> > >> drawback when company and people evaluate Wicket.
> > >>
> > >> Some articles are for 1.4 or 1.5, not many for 6
> > >> Some articles are redundant.
> > >>
> > >> I am sure the folowing structure could be improved :
> > >> https://cwiki.apache.org/**WICKET/framework-**documentation.html<
> > https://cwiki.apache.org/WICKET/framework-documentation.html>is
> > >> https://cwiki.apache.org/**WICKET/index.html<
> > https://cwiki.apache.org/WICKET/index.html>
> > >> https://cwiki.apache.org/**WICKET/documentation-index.**html<
> > https://cwiki.apache.org/WICKET/documentation-index.html>
> > >>
> > >> The http://wicket.apache.org/ layout is good.
> > >> Why not reorganize the documentation with this layout ?
> > >>
> > >> Managers want to see benefits, developpers want to learn fast(and have
> > >> fun).
> > >>
> > >>
> > >> I tested the mentionned blogs on http://wicket.apache.org/meet/**
> > >> blogs.html <http://wicket.apache.org/meet/blogs.html>
> > >>
> > >> Here is what I found :
> > >>
> > >> Chillenious! - Eelco Hillenius - http://chillenious.wordpress.**com/<
> > http://chillenious.wordpress.com/>
> > >> last update : 2008
> > >>
> > >> Here be beasties - Al Maw - http://herebebeasties.com/
> > >> last update : 2009
> > >>
> > >> Codierspiel - Nathan Hamblen (runs on Wicket) -
> > >> http://code.technically.us/
> > >> no a single wicket post
> > >>
> > >> Antwerkz - Justin Lee - http://antwerkz.com/wp/
> > >> empty
> > >>
> > >> Geertjan - Geertjan Wielenga - http://blogs.sun.com/geertjan
> > >> http 404 !
> > >>
> > >> Mystic Coders - Andrew Lombardi and
> > >> Wicket by Example - Community driven are pointing to the same address
> :
> > >> http://www.mysticcoders.com/**blog/ <
> http://www.mysticcoders.com/blog/>
> > >>
> > >>
> > >> For a wider adoption of Wicket,
> > >> Best regards to all of you
> > >>
> > >> Philippe Demaison
> > >>
> > >>
> > >
> >
>
Re: documentation
Posted by Thies Edeling <th...@rrm.net>.
Wicket is open source, if you feel that the documentation is lacking - feel
free to contribute.
On Jan 22, 2013 5:54 PM, "Philippe Demaison" <ph...@gmail.com> wrote:
> Hi Ondra and Kees,
>
> Are you kidding ?
>
> Are you saying that I need to
>
> - read a book released in 2009 covering wicket 1.3 ?
> - read http://www.wicket-library.com/wicket-examples/index.html (for which
> wicket version ? )
> - read the Wicket Cookbook
> - read the migration from 1.x to 1.5
> https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
> - read the migration from 1.5 to 1.6
> https://cwiki.apache.org/WICKET/migration-to-wicket-60.html
>
> to understand what are the Wicket's benefits and write a POC ?
>
>
> Are you saying that I need to google to read the best practices ?
>
> You know that framework adoption is linked to good documentation.
> Not only of course (quality are community are equally important) but
> documentation is essential.
>
> For example, I find these documentations much more appealing
>
> http://www.playframework.org/documentation/2.0.4/Home
> http://tapestry.apache.org/documentation.html
> https://developers.google.com/web-toolkit/doc/latest/DevGuide
> http://www.springsource.org/spring-framework#documentation
>
> Don't you ?
>
> Philippe
>
> 2013/1/22 Ondrej Zizka <oz...@redhat.com>
>
> > Hi Phillipe,
> >
> > you're right, the documentation deserves improvements.
> >
> > I would recommend you to start with the Wicket in Action book. That will
> > give you the basic concepts of Wicket.
> > Then continue with the examples from http://www.wicket-library.com/**
> > wicket-examples/index.html<
> http://www.wicket-library.com/wicket-examples/index.html>. That will
> enforce what you learned in the book, and show more tricks.
> > Then go through the Wicket Cookbook. That is a collection of solutions
> and
> > best practices for common tasks.
> > Then skim through https://cwiki.apache.org/**
> > WICKET/migration-to-wicket-15.**html<
> https://cwiki.apache.org/WICKET/migration-to-wicket-15.html>
> > and https://cwiki.apache.org/**WICKET/migration-to-wicket-60.**html<
> https://cwiki.apache.org/WICKET/migration-to-wicket-60.html>.
> >
> > It is quite easy to create non-ajax websites. I only have dificulties
> once
> > it gets to Ajax.
> > In such cases, this mailing list is very useful, and also stackoverflow
> > and the multitude of blogs.
> >
> > Not sure what are your other options, but e.g. I prefer Wicket over JSF.
> > Even big JSF fans claim that "JSF is marginally better".
> >
> > And last thing, I would recommend to try Wicket in combination with JBoss
> > AS 7, which made my development quick and easy - redeployment in 3
> seconds,
> > restart in 5 seconds, CDI, JPA and JAAS at hand, the Infinispan cache,
> easy
> > management, ...
> >
> > my2c,
> > Ondra
> >
> >
> >
> >
> > On 01/22/2013 11:24 AM, Philippe Demaison wrote:
> >
> >> Hi All,
> >>
> >> As Gabor Friedrich from the FAO, we are in my company, L'Oreal,
> comparing
> >> different web frameworks.
> >> Apache Wicket may be the best framework, may be usefull for my company,
> I
> >> don't know.
> >> I don't know because there is no clear documentation for a good
> >> evaluation.
> >>
> >> In fact the documentation is not good.
> >>
> >> The documentation is not up to date, not to say obsolete, not well
> >> organized and definitely not sexy.
> >> Sorry to being rude, I know this is difficult to do, but this is a major
> >> drawback when company and people evaluate Wicket.
> >>
> >> Some articles are for 1.4 or 1.5, not many for 6
> >> Some articles are redundant.
> >>
> >> I am sure the folowing structure could be improved :
> >> https://cwiki.apache.org/**WICKET/framework-**documentation.html<
> https://cwiki.apache.org/WICKET/framework-documentation.html>is
> >> https://cwiki.apache.org/**WICKET/index.html<
> https://cwiki.apache.org/WICKET/index.html>
> >> https://cwiki.apache.org/**WICKET/documentation-index.**html<
> https://cwiki.apache.org/WICKET/documentation-index.html>
> >>
> >> The http://wicket.apache.org/ layout is good.
> >> Why not reorganize the documentation with this layout ?
> >>
> >> Managers want to see benefits, developpers want to learn fast(and have
> >> fun).
> >>
> >>
> >> I tested the mentionned blogs on http://wicket.apache.org/meet/**
> >> blogs.html <http://wicket.apache.org/meet/blogs.html>
> >>
> >> Here is what I found :
> >>
> >> Chillenious! - Eelco Hillenius - http://chillenious.wordpress.**com/<
> http://chillenious.wordpress.com/>
> >> last update : 2008
> >>
> >> Here be beasties - Al Maw - http://herebebeasties.com/
> >> last update : 2009
> >>
> >> Codierspiel - Nathan Hamblen (runs on Wicket) -
> >> http://code.technically.us/
> >> no a single wicket post
> >>
> >> Antwerkz - Justin Lee - http://antwerkz.com/wp/
> >> empty
> >>
> >> Geertjan - Geertjan Wielenga - http://blogs.sun.com/geertjan
> >> http 404 !
> >>
> >> Mystic Coders - Andrew Lombardi and
> >> Wicket by Example - Community driven are pointing to the same address :
> >> http://www.mysticcoders.com/**blog/ <http://www.mysticcoders.com/blog/>
> >>
> >>
> >> For a wider adoption of Wicket,
> >> Best regards to all of you
> >>
> >> Philippe Demaison
> >>
> >>
> >
>
Re: documentation
Posted by Philippe Demaison <ph...@gmail.com>.
Hi Ondra and Kees,
Are you kidding ?
Are you saying that I need to
- read a book released in 2009 covering wicket 1.3 ?
- read http://www.wicket-library.com/wicket-examples/index.html (for which
wicket version ? )
- read the Wicket Cookbook
- read the migration from 1.x to 1.5
https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
- read the migration from 1.5 to 1.6
https://cwiki.apache.org/WICKET/migration-to-wicket-60.html
to understand what are the Wicket's benefits and write a POC ?
Are you saying that I need to google to read the best practices ?
You know that framework adoption is linked to good documentation.
Not only of course (quality are community are equally important) but
documentation is essential.
For example, I find these documentations much more appealing
http://www.playframework.org/documentation/2.0.4/Home
http://tapestry.apache.org/documentation.html
https://developers.google.com/web-toolkit/doc/latest/DevGuide
http://www.springsource.org/spring-framework#documentation
Don't you ?
Philippe
2013/1/22 Ondrej Zizka <oz...@redhat.com>
> Hi Phillipe,
>
> you're right, the documentation deserves improvements.
>
> I would recommend you to start with the Wicket in Action book. That will
> give you the basic concepts of Wicket.
> Then continue with the examples from http://www.wicket-library.com/**
> wicket-examples/index.html<http://www.wicket-library.com/wicket-examples/index.html>. That will enforce what you learned in the book, and show more tricks.
> Then go through the Wicket Cookbook. That is a collection of solutions and
> best practices for common tasks.
> Then skim through https://cwiki.apache.org/**
> WICKET/migration-to-wicket-15.**html<https://cwiki.apache.org/WICKET/migration-to-wicket-15.html>
> and https://cwiki.apache.org/**WICKET/migration-to-wicket-60.**html<https://cwiki.apache.org/WICKET/migration-to-wicket-60.html>.
>
> It is quite easy to create non-ajax websites. I only have dificulties once
> it gets to Ajax.
> In such cases, this mailing list is very useful, and also stackoverflow
> and the multitude of blogs.
>
> Not sure what are your other options, but e.g. I prefer Wicket over JSF.
> Even big JSF fans claim that "JSF is marginally better".
>
> And last thing, I would recommend to try Wicket in combination with JBoss
> AS 7, which made my development quick and easy - redeployment in 3 seconds,
> restart in 5 seconds, CDI, JPA and JAAS at hand, the Infinispan cache, easy
> management, ...
>
> my2c,
> Ondra
>
>
>
>
> On 01/22/2013 11:24 AM, Philippe Demaison wrote:
>
>> Hi All,
>>
>> As Gabor Friedrich from the FAO, we are in my company, L'Oreal, comparing
>> different web frameworks.
>> Apache Wicket may be the best framework, may be usefull for my company, I
>> don't know.
>> I don't know because there is no clear documentation for a good
>> evaluation.
>>
>> In fact the documentation is not good.
>>
>> The documentation is not up to date, not to say obsolete, not well
>> organized and definitely not sexy.
>> Sorry to being rude, I know this is difficult to do, but this is a major
>> drawback when company and people evaluate Wicket.
>>
>> Some articles are for 1.4 or 1.5, not many for 6
>> Some articles are redundant.
>>
>> I am sure the folowing structure could be improved :
>> https://cwiki.apache.org/**WICKET/framework-**documentation.html<https://cwiki.apache.org/WICKET/framework-documentation.html>is
>> https://cwiki.apache.org/**WICKET/index.html<https://cwiki.apache.org/WICKET/index.html>
>> https://cwiki.apache.org/**WICKET/documentation-index.**html<https://cwiki.apache.org/WICKET/documentation-index.html>
>>
>> The http://wicket.apache.org/ layout is good.
>> Why not reorganize the documentation with this layout ?
>>
>> Managers want to see benefits, developpers want to learn fast(and have
>> fun).
>>
>>
>> I tested the mentionned blogs on http://wicket.apache.org/meet/**
>> blogs.html <http://wicket.apache.org/meet/blogs.html>
>>
>> Here is what I found :
>>
>> Chillenious! - Eelco Hillenius - http://chillenious.wordpress.**com/<http://chillenious.wordpress.com/>
>> last update : 2008
>>
>> Here be beasties - Al Maw - http://herebebeasties.com/
>> last update : 2009
>>
>> Codierspiel - Nathan Hamblen (runs on Wicket) -
>> http://code.technically.us/
>> no a single wicket post
>>
>> Antwerkz - Justin Lee - http://antwerkz.com/wp/
>> empty
>>
>> Geertjan - Geertjan Wielenga - http://blogs.sun.com/geertjan
>> http 404 !
>>
>> Mystic Coders - Andrew Lombardi and
>> Wicket by Example - Community driven are pointing to the same address :
>> http://www.mysticcoders.com/**blog/ <http://www.mysticcoders.com/blog/>
>>
>>
>> For a wider adoption of Wicket,
>> Best regards to all of you
>>
>> Philippe Demaison
>>
>>
>
Re: documentation
Posted by Ondrej Zizka <oz...@redhat.com>.
Hi Phillipe,
you're right, the documentation deserves improvements.
I would recommend you to start with the Wicket in Action book. That will
give you the basic concepts of Wicket.
Then continue with the examples from
http://www.wicket-library.com/wicket-examples/index.html . That will
enforce what you learned in the book, and show more tricks.
Then go through the Wicket Cookbook. That is a collection of solutions
and best practices for common tasks.
Then skim through
https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
and https://cwiki.apache.org/WICKET/migration-to-wicket-60.html .
It is quite easy to create non-ajax websites. I only have dificulties
once it gets to Ajax.
In such cases, this mailing list is very useful, and also stackoverflow
and the multitude of blogs.
Not sure what are your other options, but e.g. I prefer Wicket over JSF.
Even big JSF fans claim that "JSF is marginally better".
And last thing, I would recommend to try Wicket in combination with
JBoss AS 7, which made my development quick and easy - redeployment in 3
seconds, restart in 5 seconds, CDI, JPA and JAAS at hand, the Infinispan
cache, easy management, ...
my2c,
Ondra
On 01/22/2013 11:24 AM, Philippe Demaison wrote:
> Hi All,
>
> As Gabor Friedrich from the FAO, we are in my company, L'Oreal, comparing
> different web frameworks.
> Apache Wicket may be the best framework, may be usefull for my company, I
> don't know.
> I don't know because there is no clear documentation for a good evaluation.
>
> In fact the documentation is not good.
>
> The documentation is not up to date, not to say obsolete, not well
> organized and definitely not sexy.
> Sorry to being rude, I know this is difficult to do, but this is a major
> drawback when company and people evaluate Wicket.
>
> Some articles are for 1.4 or 1.5, not many for 6
> Some articles are redundant.
>
> I am sure the folowing structure could be improved :
> https://cwiki.apache.org/WICKET/framework-documentation.html is
> https://cwiki.apache.org/WICKET/index.html
> https://cwiki.apache.org/WICKET/documentation-index.html
>
> The http://wicket.apache.org/ layout is good.
> Why not reorganize the documentation with this layout ?
>
> Managers want to see benefits, developpers want to learn fast(and have fun).
>
>
> I tested the mentionned blogs on http://wicket.apache.org/meet/blogs.html
>
> Here is what I found :
>
> Chillenious! - Eelco Hillenius - http://chillenious.wordpress.com/
> last update : 2008
>
> Here be beasties - Al Maw - http://herebebeasties.com/
> last update : 2009
>
> Codierspiel - Nathan Hamblen (runs on Wicket) - http://code.technically.us/
> no a single wicket post
>
> Antwerkz - Justin Lee - http://antwerkz.com/wp/
> empty
>
> Geertjan - Geertjan Wielenga - http://blogs.sun.com/geertjan
> http 404 !
>
> Mystic Coders - Andrew Lombardi and
> Wicket by Example - Community driven are pointing to the same address :
> http://www.mysticcoders.com/blog/
>
>
> For a wider adoption of Wicket,
> Best regards to all of you
>
> Philippe Demaison
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org