Re: New documentation on Wicket internals

2016-03-27 Thread Andrea Del Bene

Thanks also to Martin who double-checked my docs!
Andrea.

Great Andrea!

Thanks a lot!

kind regards

Tobias


Am 25.03.2016 um 16:34 schrieb andrea del bene :

Hi,

I've added a couple of notes to the userguide about markup parsing and 
autocomponents:

https://ci.apache.org/projects/wicket/guide/7.x/guide/single.html#autocomponents

Have fun!

Andrea.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: New documentation on Wicket internals

2016-03-25 Thread Tobias Soloschenko
Great Andrea!

Thanks a lot!

kind regards

Tobias

> Am 25.03.2016 um 16:34 schrieb andrea del bene :
> 
> Hi,
> 
> I've added a couple of notes to the userguide about markup parsing and 
> autocomponents:
> 
> https://ci.apache.org/projects/wicket/guide/7.x/guide/single.html#autocomponents
> 
> Have fun!
> 
> Andrea.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: New documentation on Wicket internals

2016-03-25 Thread Štefan Šimík
Thankx, very useful,
I like these clear explanations about wicket internals. It is not always
easy to understand them from code.

On Fri, Mar 25, 2016 at 6:05 PM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:

> Thanks!
>
> On Fri, Mar 25, 2016 at 4:34 PM, andrea del bene 
> wrote:
>
> > Hi,
> >
> > I've added a couple of notes to the userguide about markup parsing and
> > autocomponents:
> >
> >
> >
> https://ci.apache.org/projects/wicket/guide/7.x/guide/single.html#autocomponents
> >
> > Have fun!
> >
> > Andrea.
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>


Re: New documentation on Wicket internals

2016-03-25 Thread Ernesto Reinaldo Barreiro
Thanks!

On Fri, Mar 25, 2016 at 4:34 PM, andrea del bene 
wrote:

> Hi,
>
> I've added a couple of notes to the userguide about markup parsing and
> autocomponents:
>
>
> https://ci.apache.org/projects/wicket/guide/7.x/guide/single.html#autocomponents
>
> Have fun!
>
> Andrea.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Regards - Ernesto Reinaldo Barreiro


New documentation on Wicket internals

2016-03-25 Thread andrea del bene

Hi,

I've added a couple of notes to the userguide about markup parsing and 
autocomponents:


https://ci.apache.org/projects/wicket/guide/7.x/guide/single.html#autocomponents

Have fun!

Andrea.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: How get wiki Framework Documentation for offline reading

2014-02-12 Thread Duke
Hi, Martin. Hi everyone!
What about a offline wicket api  documentation
http://ci.apache.org/projects/wicket/apidocs/6.x/  ? Sometime it's usefull
to get it without any internet connection.  Can we download it anyware?
Best regards,
Andrey

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/How-get-wiki-Framework-Documentation-for-offline-reading-tp4664374p4664411.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: How get wiki Framework Documentation for offline reading

2014-02-12 Thread Martin Grigorov
http://central.maven.org/maven2/org/apache/wicket/wicket-core/6.13.0/wicket-core-6.13.0-javadoc.jar

Martin Grigorov
Wicket Training and Consulting


On Wed, Feb 12, 2014 at 4:57 PM, Duke warlock9...@gmail.com wrote:

 Hi, Martin. Hi everyone!
 What about a offline wicket api  documentation
 http://ci.apache.org/projects/wicket/apidocs/6.x/  ? Sometime it's
 usefull
 to get it without any internet connection.  Can we download it anyware?
 Best regards,
 Andrey

 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/How-get-wiki-Framework-Documentation-for-offline-reading-tp4664374p4664411.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




How get wiki Framework Documentation for offline reading

2014-02-11 Thread Farrukh SATTOROV
Hi everyone!, Can i download wicket wiki framework documentation for
offline reading. Thanks.
https://cwiki.apache.org/confluence/display/WICKET/Index


Re: How get wiki Framework Documentation for offline reading

2014-02-11 Thread Martin Grigorov
http://wicket.apache.org/guide/guide/single.pdf

Martin Grigorov
Wicket Training and Consulting


On Tue, Feb 11, 2014 at 6:06 PM, Farrukh SATTOROV fireda...@gmail.comwrote:

 Hi everyone!, Can i download wicket wiki framework documentation for
 offline reading. Thanks.
 https://cwiki.apache.org/confluence/display/WICKET/Index



Re: How get wiki Framework Documentation for offline reading

2014-02-11 Thread Farrukh SATTOROV
I have printed this guide as brochure and reading now, but i mean about
wiki doc. Thanks anyway


On Tue, Feb 11, 2014 at 10:52 PM, Martin Grigorov mgrigo...@apache.orgwrote:

 http://wicket.apache.org/guide/guide/single.pdf

 Martin Grigorov
 Wicket Training and Consulting


 On Tue, Feb 11, 2014 at 6:06 PM, Farrukh SATTOROV fireda...@gmail.com
 wrote:

  Hi everyone!, Can i download wicket wiki framework documentation for
  offline reading. Thanks.
  https://cwiki.apache.org/confluence/display/WICKET/Index
 




-- 
С уважением и наилучшими пожеланиями
*Фаррух*


Re: How get wiki Framework Documentation for offline reading

2014-02-11 Thread Martin Grigorov
The Wiki is not very up-to-date...

Martin Grigorov
Wicket Training and Consulting


On Tue, Feb 11, 2014 at 8:48 PM, Farrukh SATTOROV fireda...@gmail.comwrote:

 I have printed this guide as brochure and reading now, but i mean about
 wiki doc. Thanks anyway


 On Tue, Feb 11, 2014 at 10:52 PM, Martin Grigorov mgrigo...@apache.org
 wrote:

  http://wicket.apache.org/guide/guide/single.pdf
 
  Martin Grigorov
  Wicket Training and Consulting
 
 
  On Tue, Feb 11, 2014 at 6:06 PM, Farrukh SATTOROV fireda...@gmail.com
  wrote:
 
   Hi everyone!, Can i download wicket wiki framework documentation for
   offline reading. Thanks.
   https://cwiki.apache.org/confluence/display/WICKET/Index
  
 



 --
 С уважением и наилучшими пожеланиями
 *Фаррух*



Re: Documentation for RequestLogger

2013-08-07 Thread Jens Jahnke
Hi,

On Tue, 6 Aug 2013 15:11:34 -0400
Paul Bors p...@bors.ws wrote:

PB Isn't Log4J shipped with the quick-start?
PB 
PB Create yourself a quick-start and analyze it:
PB http://wicket.apache.org/start/quickstart.html
PB 
PB PS: You can also check the initialization related topics as well as
PB your first stop for Wicket's doc via the Wicket Free Guide at:
PB http://wicket.apache.org/learn/books/freeguide.html

thanks for the information, the freeguide rocks.

But actually I found the solution in wicket in action. :)

Nonetheless it only logs to stdout but I guess thats a log4j question.

Regards,

Jens

-- 
07. Ernting 2013, 10:04
Homepage : http://www.jan0sch.de

In order to live free and happily, you must sacrifice boredom.
It is not always an easy sacrifice.


pgp9Up9H3UBot.pgp
Description: PGP signature


Re: Documentation for RequestLogger

2013-08-07 Thread Martin Grigorov
On Wed, Aug 7, 2013 at 10:07 AM, Jens Jahnke jan0...@gmx.net wrote:

 Hi,

 On Tue, 6 Aug 2013 15:11:34 -0400
 Paul Bors p...@bors.ws wrote:

 PB Isn't Log4J shipped with the quick-start?
 PB
 PB Create yourself a quick-start and analyze it:
 PB http://wicket.apache.org/start/quickstart.html
 PB
 PB PS: You can also check the initialization related topics as well as
 PB your first stop for Wicket's doc via the Wicket Free Guide at:
 PB http://wicket.apache.org/learn/books/freeguide.html

 thanks for the information, the freeguide rocks.

 But actually I found the solution in wicket in action. :)

 Nonetheless it only logs to stdout but I guess thats a log4j question.


What do you mean that it logs to stdout ?
There is no usage of System.out/err in Wicket. The RequestLogger uses SLF4J.
Your question is really a log4j question (if you use slf4j-log4j as
backend).



 Regards,

 Jens

 --
 07. Ernting 2013, 10:04
 Homepage : http://www.jan0sch.de

 In order to live free and happily, you must sacrifice boredom.
 It is not always an easy sacrifice.



Re: Documentation for RequestLogger

2013-08-07 Thread Cedric Gatay
I guess he's talking of its current log4j setup which logs to stdout

__
Cedric Gatay (@Cedric_Gatay http://twitter.com/Cedric_Gatay)
http://code-troopers.com | http://www.bloggure.info | http://cedric.gatay.fr


On Wed, Aug 7, 2013 at 10:11 AM, Martin Grigorov mgrigo...@apache.orgwrote:

 On Wed, Aug 7, 2013 at 10:07 AM, Jens Jahnke jan0...@gmx.net wrote:

  Hi,
 
  On Tue, 6 Aug 2013 15:11:34 -0400
  Paul Bors p...@bors.ws wrote:
 
  PB Isn't Log4J shipped with the quick-start?
  PB
  PB Create yourself a quick-start and analyze it:
  PB http://wicket.apache.org/start/quickstart.html
  PB
  PB PS: You can also check the initialization related topics as well as
  PB your first stop for Wicket's doc via the Wicket Free Guide at:
  PB http://wicket.apache.org/learn/books/freeguide.html
 
  thanks for the information, the freeguide rocks.
 
  But actually I found the solution in wicket in action. :)
 
  Nonetheless it only logs to stdout but I guess thats a log4j question.
 

 What do you mean that it logs to stdout ?
 There is no usage of System.out/err in Wicket. The RequestLogger uses
 SLF4J.
 Your question is really a log4j question (if you use slf4j-log4j as
 backend).


 
  Regards,
 
  Jens
 
  --
  07. Ernting 2013, 10:04
  Homepage : http://www.jan0sch.de
 
  In order to live free and happily, you must sacrifice boredom.
  It is not always an easy sacrifice.
 



Re: Documentation for RequestLogger

2013-08-07 Thread Jens Jahnke
Hi,

On Wed, 7 Aug 2013 10:11:30 +0200
Martin Grigorov mgrigo...@apache.org wrote:

MG On Wed, Aug 7, 2013 at 10:07 AM, Jens Jahnke jan0...@gmx.net
MG wrote:
MG 
MG  Hi,
MG 
MG  On Tue, 6 Aug 2013 15:11:34 -0400
MG  Paul Bors p...@bors.ws wrote:
MG 
MG  PB Isn't Log4J shipped with the quick-start?
MG  PB
MG  PB Create yourself a quick-start and analyze it:
MG  PB http://wicket.apache.org/start/quickstart.html
MG  PB
MG  PB PS: You can also check the initialization related topics as
MG  PB well as your first stop for Wicket's doc via the Wicket Free
MG  PB Guide at: http://wicket.apache.org/learn/books/freeguide.html
MG 
MG  thanks for the information, the freeguide rocks.
MG 
MG  But actually I found the solution in wicket in action. :)
MG 
MG  Nonetheless it only logs to stdout but I guess thats a log4j
MG  question.
MG 
MG 
MG What do you mean that it logs to stdout ?
MG There is no usage of System.out/err in Wicket. The RequestLogger
MG uses SLF4J. Your question is really a log4j question (if you use
MG slf4j-log4j as backend).

sorry, I didn't express myself correctly. It logged to catalina.out
(tomcat).

I was able to solve the issue. Somehow I had slf4j-simple in my pom.xml
file. After changing that to slf4j-log4j12 everything works as expected.

Regards,

Jens

-- 
07. Ernting 2013, 11:14
Homepage : http://www.jan0sch.de

Never tell people how to do things.  Tell them WHAT to
do and they will surprise you with their ingenuity.
-- Gen. George S. Patton, Jr.


pgpy0pBGhE_TM.pgp
Description: PGP signature


Documentation for RequestLogger

2013-08-06 Thread Jens Jahnke
Hi,

I'd like to know if there is an official documentation for RequestLogger
anywhere?

I found several small bits on the net, but nothing that gives me a clue
how to actually do some logging.

I know that I have to initialise it somehow like this:

IRequestLoggerSettings requestLogger = 
Application.get().getRequestLoggerSettings();
requestLogger.setRequestLoggerEnabled(true);

But where do I have to put this initialisation? I've put it into my apps init() 
but it does nothing except creating an empty log file.

My log4j.properties:

log4j.category.org.apache.wicket.protocol.http.RequestLogger=INFO,RequestLogger
log4j.additivity.org.apache.wicket.protocol.http.RequestLogger=false
log4j.appender.RequestLogger=org.apache.log4j.RollingFileAppender
log4j.appender.RequestLogger.File=${catalina.home}/logs/wicket-requests.log
log4j.appender.RequestLogger.MaxFileSize=10MB
log4j.appender.RequestLogger.MaxBackupIndex=10
log4j.appender.RequestLogger.layout=org.apache.log4j.PatternLayout
log4j.appender.RequestLogger.layout.ConversionPattern=%d{ISO8601} %-5p- 
%-26.26c{1} - %m\n


Regards,

Jens

-- 
06. Ernting 2013, 10:38
Homepage : http://www.jan0sch.de

Kirk to Enterprise...


pgpm33oCFzdz6.pgp
Description: PGP signature


RE: Documentation for RequestLogger

2013-08-06 Thread Paul Bors
Isn't Log4J shipped with the quick-start?

Create yourself a quick-start and analyze it:
http://wicket.apache.org/start/quickstart.html

PS: You can also check the initialization related topics as well as your
first stop for Wicket's doc via the Wicket Free Guide at:
http://wicket.apache.org/learn/books/freeguide.html

~ Thank you,
  Paul Bors


-Original Message-
From: Jens Jahnke [mailto:jan0...@gmx.net] 
Sent: Tuesday, August 06, 2013 4:44 AM
To: users@wicket.apache.org
Subject: Documentation for RequestLogger

Hi,

I'd like to know if there is an official documentation for RequestLogger
anywhere?

I found several small bits on the net, but nothing that gives me a clue how
to actually do some logging.

I know that I have to initialise it somehow like this:

IRequestLoggerSettings requestLogger =
Application.get().getRequestLoggerSettings();
requestLogger.setRequestLoggerEnabled(true);

But where do I have to put this initialisation? I've put it into my apps
init() but it does nothing except creating an empty log file.

My log4j.properties:

log4j.category.org.apache.wicket.protocol.http.RequestLogger=INFO,RequestLog
ger
log4j.additivity.org.apache.wicket.protocol.http.RequestLogger=false
log4j.appender.RequestLogger=org.apache.log4j.RollingFileAppender
log4j.appender.RequestLogger.File=${catalina.home}/logs/wicket-requests.log
log4j.appender.RequestLogger.MaxFileSize=10MB
log4j.appender.RequestLogger.MaxBackupIndex=10
log4j.appender.RequestLogger.layout=org.apache.log4j.PatternLayout
log4j.appender.RequestLogger.layout.ConversionPattern=%d{ISO8601} %-5p-
%-26.26c{1} - %m\n


Regards,

Jens

--
06. Ernting 2013, 10:38
Homepage : http://www.jan0sch.de

Kirk to Enterprise...



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wasp-Swarm documentation

2013-05-03 Thread saty
Anyone?

Thanks



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wasp-Swarm-documentation-tp4658494p4658522.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wasp-Swarm documentation

2013-05-03 Thread Martijn Dashorst
I've some documentation on my disk. Takes some time to upload somewhere.

Martijn

On Fri, May 3, 2013 at 3:40 PM, saty satya...@gmail.com wrote:

 Anyone?

 Thanks



 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Wasp-Swarm-documentation-tp4658494p4658522.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com


Re: Wasp-Swarm documentation

2013-05-03 Thread Martijn Dashorst
https://github.com/wicketstuff/core/wiki/Wicket-Security---1.-Overview
https://github.com/wicketstuff/core/wiki/Wicket-Security---2.-Introduction
https://github.com/wicketstuff/core/wiki/Wicket-Security---3.-Getting-started
https://github.com/wicketstuff/core/wiki/Wicket-Security---4.-Spring-security

On Fri, May 3, 2013 at 3:49 PM, Martijn Dashorst martijn.dasho...@gmail.com
 wrote:

 I've some documentation on my disk. Takes some time to upload somewhere.

 Martijn


 On Fri, May 3, 2013 at 3:40 PM, saty satya...@gmail.com wrote:

 Anyone?

 Thanks



 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Wasp-Swarm-documentation-tp4658494p4658522.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 --
 Become a Wicket expert, learn from the best: http://wicketinaction.com




-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com


Re: Wasp-Swarm documentation

2013-05-03 Thread saty
Thanks, if you could upload that would be great.

a link here would help greatly too.

https://cwiki.apache.org/WICKET/wasp-swarm-security.html





--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wasp-Swarm-documentation-tp4658494p4658527.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wasp-Swarm documentation

2013-05-03 Thread saty
Thanks again, much appreciated.



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wasp-Swarm-documentation-tp4658494p4658531.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Wasp-Swarm documentation

2013-05-02 Thread saty
Can not find any documentation around this, can someone please point to some
useful link.

I need to disable few links, buttons, radio buttons based on user roles,
have not found any suitable material that can help. The goal is to create a
read only access to application.

The code we have works file at panel lavel hive configuration using
{ComponentPermission} render or 'render enable', i dont have any idea how to
configure these for individual controls at a given panel.

Any help would be appreciated.

Thanks



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wasp-Swarm-documentation-tp4658494.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: documentation

2013-01-28 Thread Philippe Demaison
The community is very responsive.
Thanks you very much, the documentation will help us.

Philippe Demaison


2013/1/25 Martin Grigorov mgrigo...@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.delb...@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 schrdrr...@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.demai...@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-unsubscr...@wicket.apache.org
  For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 
 
  --**--**-
  To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org
 users-unsubscr...@wicket.apache.org
  For additional commands, e-mail: users-h...@wicket.apache.org
 
 


 --
 Martin Grigorov
 jWeekend
 Training, Consulting, Development
 http://jWeekend.com http://jweekend.com/



Re: documentation

2013-01-25 Thread Martin Grigorov
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.delb...@gmail.comwrote:

 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-exampleshttps://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 schrdrr...@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.demai...@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.orgusers-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 --**--**-
 To unsubscribe, e-mail: 
 users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com http://jweekend.com/


Re: documentation

2013-01-24 Thread Philippe Demaison
This is great !
I am looking forward to reading the new documentation.

Best regards
Phlippe


2013/1/23 Rob Schroeder schrdrr...@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.demai...@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-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




Re: documentation

2013-01-24 Thread Andrea Del Bene
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 schrdrr...@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.demai...@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-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: documentation

2013-01-23 Thread Philippe Demaison
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.demai...@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 ozi...@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.htmlis
   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

Re: documentation

2013-01-23 Thread Martin Grigorov
Hi,


On Wed, Jan 23, 2013 at 12:36 PM, Philippe Demaison
ph.demai...@gmail.comwrote:

 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.demai...@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 ozi...@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.htmlis
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

Re: documentation

2013-01-23 Thread Andy Van Den Heuvel
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 mgrigo...@apache.orgwrote:

 Hi,


 On Wed, Jan 23, 2013 at 12:36 PM, Philippe Demaison
 ph.demai...@gmail.comwrote:

  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.demai...@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 ozi...@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.htmlis
 https://cwiki.apache.org/**WICKET/index.html
https://cwiki.apache.org/WICKET/index.html
 https://cwiki.apache.org

Re: documentation

2013-01-23 Thread Rob Schroeder
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.demai...@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-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



documentation

2013-01-22 Thread Philippe Demaison
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

2013-01-22 Thread Kees van Dieren
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.demai...@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

2013-01-22 Thread Ondrej Zizka

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-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: documentation

2013-01-22 Thread Philippe Demaison
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 ozi...@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.htmlhttp://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.**htmlhttps://cwiki.apache.org/WICKET/migration-to-wicket-15.html
 and 
 https://cwiki.apache.org/**WICKET/migration-to-wicket-60.**htmlhttps://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.htmlhttps://cwiki.apache.org/WICKET/framework-documentation.htmlis
 https://cwiki.apache.org/**WICKET/index.htmlhttps://cwiki.apache.org/WICKET/index.html
 https://cwiki.apache.org/**WICKET/documentation-index.**htmlhttps://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

2013-01-22 Thread Ondrej Zizka

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 ozi...@redhat.com mailto:ozi...@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

Re: documentation

2013-01-22 Thread Paul Bors
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 ozi...@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.htmlhttp://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.**htmlhttps://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.**htmlhttps://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/Homehttp://www.playframework.org/documentation/2.0.4/Home
 http://tapestry.apache.org/**documentation.htmlhttp://tapestry.apache.org/documentation.html
 https://developers.google.com/**web-toolkit/doc/latest/**DevGuidehttps://developers.google.com/web-toolkit/doc/latest/DevGuide
 http://www.springsource.org/**spring-framework#documentationhttp://www.springsource.org/spring-framework#documentation

 Don't you ?

 Philippe

 2013/1/22 Ondrej Zizka ozi...@redhat.com mailto:ozi...@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.htmlhttp://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.**htmlhttps://cwiki.apache.org/WICKET/migration-to-wicket-15.html
 and 
 https://cwiki.apache.org/**WICKET/migration-to-wicket-60.**htmlhttps://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.htmlhttps

Re: documentation

2013-01-22 Thread Guillaume Smet
Hi Philippe,

On Tue, Jan 22, 2013 at 5:53 PM, Philippe Demaison
ph.demai...@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-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



RE: documentation

2013-01-22 Thread Paul Bors
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.s...@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.demai...@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-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: documentation

2013-01-22 Thread Thies Edeling
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.demai...@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 ozi...@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.htmlis
  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
 
 
 



Wicket documentation suggestion

2011-07-22 Thread Niranjan Rao
Not sure if this is the right forum to post, but I presume many decision
makers are lurking here.

When googling for class documentation, google typically shows multiple
results. I have caught myself looking at wrong version of docs many
times. This is especially useful if there methods that are deprecated or
we have new way of doing things in better way.

From this perspective, I like what Microsoft does. They tell you that
you are looking at documentation of version X and have a link to jump to
other versions if required. Example at
http://msdn.microsoft.com/en-us/library/system.data.dataset.aspx


I know for API docs, we can see 1.4 or other versions in url bar, but I
think this might be really useful to have a link to jump to other
versions.

Any Thoughts?

Niranjan



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicketstuff-push Documentation?

2011-07-05 Thread jbrookover

Sebastian-61 wrote:
 
 there is currently not any more documentation.
 
 When you use push as decribed in the WIKI (EventHandler+PushNode) then 
 you will need an additional message dispatching service (which often is 
 the case in enterprise environments). If you want to communicate within 
 a wicket application only, e.g. between pages or users, than you can use 
 the channel feature provided by push: you create a named messaging 
 channel using IPushService.createChannel(Name), connect the node you 
 installed into a component to that channel using 
 IPushService.connectToChannel(Node,Channel) and send events to a 
 channel using IPushService.publish(Channel, Event).
 

Thanks for the feedback.  We do intend to scale to multiple server nodes
but, thankfully, I have a year to figure out the messaging system.  For some
reason, your quick paragraph makes more sense than anything else I've read -
so, thanks!  As I explore, I'll see about adding some JavaDoc for the newbs.

Jake

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-Documentation-tp3644319p3645846.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



wicketstuff-push Documentation?

2011-07-04 Thread jbrookover
Hey all,

Just explored the wicketstuff-push examples.  Everything works great. 

The only problem is that I'm overwhelmed with the code.  I'm new to
pushing; I had no idea what Comet was before yesterday.  I understand the
fundamentals of AjaxTimerBehavior polling, but push-timer and push-core go
way beyond that: channels, listeners, etc.

Question: Is there documentation beyond the GitHub Wiki and the
push-examples module?  

If not, I'll just dive in the old fashioned way, but I was hoping to get a
better understanding before doing so.  In return, I'll try to put some
JavaDoc in the source as I start playing around.

Thanks!

Jake

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-Documentation-tp3644319p3644319.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicketstuff-push Documentation?

2011-07-04 Thread Martin Grigorov
https://github.com/wicketstuff/core/wiki/Push


On Mon, Jul 4, 2011 at 8:48 PM, jbrookover jbrooko...@cast.org wrote:
 Hey all,

 Just explored the wicketstuff-push examples.  Everything works great.

 The only problem is that I'm overwhelmed with the code.  I'm new to
 pushing; I had no idea what Comet was before yesterday.  I understand the
 fundamentals of AjaxTimerBehavior polling, but push-timer and push-core go
 way beyond that: channels, listeners, etc.

 Question: Is there documentation beyond the GitHub Wiki and the
 push-examples module?

 If not, I'll just dive in the old fashioned way, but I was hoping to get a
 better understanding before doing so.  In return, I'll try to put some
 JavaDoc in the source as I start playing around.

 Thanks!

 Jake

 --
 View this message in context: 
 http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-Documentation-tp3644319p3644319.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org





-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicketstuff-push Documentation?

2011-07-04 Thread Sebastian

Hi Jake,

there is currently not any more documentation.

When you use push as decribed in the WIKI (EventHandler+PushNode) then 
you will need an additional message dispatching service (which often is 
the case in enterprise environments). If you want to communicate within 
a wicket application only, e.g. between pages or users, than you can use 
the channel feature provided by push: you create a named messaging 
channel using IPushService.createChannel(Name), connect the node you 
installed into a component to that channel using 
IPushService.connectToChannel(Node,Channel) and send events to a 
channel using IPushService.publish(Channel, Event).


Regards,

Seb

On 04.07.2011 20:48, jbrookover wrote:

Hey all,

Just explored the wicketstuff-push examples.  Everything works great.

The only problem is that I'm overwhelmed with the code.  I'm new to
pushing; I had no idea what Comet was before yesterday.  I understand the
fundamentals of AjaxTimerBehavior polling, but push-timer and push-core go
way beyond that: channels, listeners, etc.

Question: Is there documentation beyond the GitHub Wiki and the
push-examples module?

If not, I'll just dive in the old fashioned way, but I was hoping to get a
better understanding before doing so.  In return, I'll try to put some
JavaDoc in the source as I start playing around.

Thanks!

Jake

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/wicketstuff-push-Documentation-tp3644319p3644319.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: AjaxButton documentation error?

2010-10-22 Thread Jeremy Thomerson
It will lie no more.  I just fixed it in 1.4.x and trunk.  Thanks Chris and
Craig!

On Mon, Jul 12, 2010 at 7:03 AM, Craig McIlwee 
craig.mcil...@openroadsconsulting.com wrote:

 Yeah, that's been wrong for a really long time, maybe always.  Whenever I
 point coworkers to that class I tell them to ignore that comment.  Just
 checked the code for AjaxButton, and there is no form.add(this) call
 anywhere.

 Craig

 - Original Message -
 From: Chris Colman
 [mailto:chr...@stepaheadsoftware.com]
 To: users@wicket.apache.org
 Sent: Thu,
 08 Jul 2010 21:48:20 -0400
 Subject: AjaxButton documentation error?


  The JavaDoc for AjaxButton (and AjaxSubmitButton) says:
 
  A button that submits the form via ajax. Since this button takes the
  form as a constructor argument it does not need to be added to it unlike
  the Button component.
 
  Well I've just spent a good amount of time putting that theory to the
  test. I use the constructor that takes the form as its second parameter.
  Basically the form fails with an error saying wicket can't find the
  button component unless I explicitly add the AjaxButton object to the
  form object, seemingly contradicting the above doco quote. The Wicket
  example explicitly adds the button to the form too - which also seems to
  go against the above doco declaration.
 
  Maybe it's a rare case where reading the documentation is not a good
  idea =}
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
  For additional commands, e-mail: users-h...@wicket.apache.org
 
 

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket?  Use Brix! http://brixcms.org*


Re: AjaxButton documentation error?

2010-07-12 Thread Craig McIlwee
Yeah, that's been wrong for a really long time, maybe always.  Whenever I point 
coworkers to that class I tell them to ignore that comment.  Just checked the 
code for AjaxButton, and there is no form.add(this) call anywhere.

Craig

- Original Message -
From: Chris Colman
[mailto:chr...@stepaheadsoftware.com]
To: users@wicket.apache.org
Sent: Thu,
08 Jul 2010 21:48:20 -0400
Subject: AjaxButton documentation error?


 The JavaDoc for AjaxButton (and AjaxSubmitButton) says:
 
 A button that submits the form via ajax. Since this button takes the
 form as a constructor argument it does not need to be added to it unlike
 the Button component.
 
 Well I've just spent a good amount of time putting that theory to the
 test. I use the constructor that takes the form as its second parameter.
 Basically the form fails with an error saying wicket can't find the
 button component unless I explicitly add the AjaxButton object to the
 form object, seemingly contradicting the above doco quote. The Wicket
 example explicitly adds the button to the form too - which also seems to
 go against the above doco declaration.
 
 Maybe it's a rare case where reading the documentation is not a good
 idea =}
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: AjaxButton documentation error?

2010-07-09 Thread Igor Vaynberg
sounds like a bug, file a jira.

-igor

On Thu, Jul 8, 2010 at 6:48 PM, Chris Colman
chr...@stepaheadsoftware.com wrote:
 The JavaDoc for AjaxButton (and AjaxSubmitButton) says:

 A button that submits the form via ajax. Since this button takes the
 form as a constructor argument it does not need to be added to it unlike
 the Button component.

 Well I've just spent a good amount of time putting that theory to the
 test. I use the constructor that takes the form as its second parameter.
 Basically the form fails with an error saying wicket can't find the
 button component unless I explicitly add the AjaxButton object to the
 form object, seemingly contradicting the above doco quote. The Wicket
 example explicitly adds the button to the form too - which also seems to
 go against the above doco declaration.

 Maybe it's a rare case where reading the documentation is not a good
 idea =}


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



AjaxButton documentation error?

2010-07-08 Thread Chris Colman
The JavaDoc for AjaxButton (and AjaxSubmitButton) says:

A button that submits the form via ajax. Since this button takes the
form as a constructor argument it does not need to be added to it unlike
the Button component.

Well I've just spent a good amount of time putting that theory to the
test. I use the constructor that takes the form as its second parameter.
Basically the form fails with an error saying wicket can't find the
button component unless I explicitly add the AjaxButton object to the
form object, seemingly contradicting the above doco quote. The Wicket
example explicitly adds the button to the form too - which also seems to
go against the above doco declaration.

Maybe it's a rare case where reading the documentation is not a good
idea =}


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Request to improve documentation of onRuntimeException

2009-05-04 Thread Peter Ross
Hi,

I'm looking at overriding onRuntimeException[1]to do some cleanup if
there was an exception,however I want the standard error handling page
to be displayed.

I thought I would need use getInternalErrorPage and then do some
tricky stuff to instantiate it, but after inspecting
AbstractRequestCycleProcessor then it appears that just returning null
is sufficient to get the standard wicket error handling page.

It would be nice if the documentation stated that returning null will
leave it up to the RequestCycleProcessor to display what page to
display, and that the standard wicket RequestCycleProcessor will
simply display the default error page in this case.

Regards
Pete

[1] 
http://wicket.apache.org/docs/1.4/org/apache/wicket/RequestCycle.html#onRuntimeException(org.apache.wicket.Page,%20java.lang.RuntimeException)

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



wicket-auth-roles documentation

2009-03-24 Thread Linda van der Pal
Quick question, where can I find the documentation for 
wicket-auth-roles? So far all I've been able to find is where I could 
download it.


Regards,
Linda

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicket-auth-roles documentation

2009-03-24 Thread Martijn Dashorst
There are examples in the Wicket-examples project. And Wicket in
Action has a short chapter on wicket security, together with a section
on wicket-auth-roles.

Martijn

On Tue, Mar 24, 2009 at 9:53 AM, Linda van der Pal
lvd...@heritageagenturen.nl wrote:
 Quick question, where can I find the documentation for wicket-auth-roles? So
 far all I've been able to find is where I could download it.

 Regards,
 Linda

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org





-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicket-auth-roles documentation

2009-03-24 Thread Linda van der Pal

Thanks!

Martijn Dashorst wrote:

There are examples in the Wicket-examples project. And Wicket in
Action has a short chapter on wicket security, together with a section
on wicket-auth-roles.

Martijn

On Tue, Mar 24, 2009 at 9:53 AM, Linda van der Pal
lvd...@heritageagenturen.nl wrote:
  

Quick question, where can I find the documentation for wicket-auth-roles? So
far all I've been able to find is where I could download it.

Regards,
Linda

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org







  




No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.5.278 / Virus Database: 270.11.25/2019 - Release Date: 03/23/09 18:51:00


  



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicket markup documentation and question on threading/clustering

2008-04-18 Thread Doug Donohoe

Thanks for the fast response.


igor.vaynberg wrote:
 
 On Thu, Apr 17, 2008 at 6:48 PM, Doug Donohoe [EMAIL PROTECTED] wrote:

  I'm looking for a complete list of all wicket markup (e.g.,
 wicket-panel,
  wicket-child, wicket-exclude etc).  I didn't find anything obvious via
  Google or the wiki.  Am I missing something?  As a newcomer, it would be
  helpful to know what all the choices are and what they do so as to not
 miss
  anything.
 
 http://cwiki.apache.org/confluence/display/WICKET/Wicket%27s+XHTML+tags
 
  Also, I am looking for an explanation of the threading / clustering
  architecture with Wicket.  Neither of the books address these topics in
 any
  depth.  For example, in the simple Link Counter example in Wicket in
  Action, how does that counter work with multiple people accessing the
 page?
  It doesn't appear to be synchronized unless this is under the covers. 
 If
  there is an instance of each page per person that would mean the total
  displayed is per person (and not per all users).
 
 each user gets their own instance of Page. Access to the page object
 is synced on user's session (thats not exactly correct but for
 purposes of this discussion it will do) so you do not have to worry
 about all the nasty syncing yourself. if you have data that you want
 users to share/interact with it has to be kept in some global store:
 database, servlet context, memory, etc.
 
  Finally, if one wants to have multiple application servers for load
  balancing / failover, what options does one have with Wicket?  I assume
 you
  use some sort of clustered session that wicket utilizes.  Perhaps
 something
  like Gigaspaces?
 
 wicket will work with regular servlet container clustering. it stores
 the page in http session and page is serializable so it will be
 replicated.
 
 -igor
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/wicket-markup-documentation-and-question-on-threading-clustering-tp16758965p16764210.html
Sent from the Wicket - User mailing list archive at Nabble.com.


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



wicket markup documentation and question on threading/clustering

2008-04-17 Thread Doug Donohoe

Hi Wicket Community:

I'm new to Wicket - I'm using it to rebuild and enhance my www.ddpoker.com
website.  So far I am very impressed with Wicket.  I have two books - the
Wicket in Action MEAP early access edition and enjoy web development with
wicket.  

I'm looking for a complete list of all wicket markup (e.g., wicket-panel,
wicket-child, wicket-exclude etc).  I didn't find anything obvious via
Google or the wiki.  Am I missing something?  As a newcomer, it would be
helpful to know what all the choices are and what they do so as to not miss
anything.

Also, I am looking for an explanation of the threading / clustering
architecture with Wicket.  Neither of the books address these topics in any
depth.  For example, in the simple Link Counter example in Wicket in
Action, how does that counter work with multiple people accessing the page? 
It doesn't appear to be synchronized unless this is under the covers.  If
there is an instance of each page per person that would mean the total
displayed is per person (and not per all users).

Finally, if one wants to have multiple application servers for load
balancing / failover, what options does one have with Wicket?  I assume you
use some sort of clustered session that wicket utilizes.  Perhaps something
like Gigaspaces?

Thanks for any answers.  Hopefully these questions give some insight into
what an experienced developer might ask as a newcomer to the platform.

Finally,

Thanks,

-Doug
-- 
View this message in context: 
http://www.nabble.com/wicket-markup-documentation-and-question-on-threading-clustering-tp16758965p16758965.html
Sent from the Wicket - User mailing list archive at Nabble.com.


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



Re: wicket markup documentation and question on threading/clustering

2008-04-17 Thread Igor Vaynberg
On Thu, Apr 17, 2008 at 6:48 PM, Doug Donohoe [EMAIL PROTECTED] wrote:

  I'm looking for a complete list of all wicket markup (e.g., wicket-panel,
  wicket-child, wicket-exclude etc).  I didn't find anything obvious via
  Google or the wiki.  Am I missing something?  As a newcomer, it would be
  helpful to know what all the choices are and what they do so as to not miss
  anything.

http://cwiki.apache.org/confluence/display/WICKET/Wicket%27s+XHTML+tags

  Also, I am looking for an explanation of the threading / clustering
  architecture with Wicket.  Neither of the books address these topics in any
  depth.  For example, in the simple Link Counter example in Wicket in
  Action, how does that counter work with multiple people accessing the page?
  It doesn't appear to be synchronized unless this is under the covers.  If
  there is an instance of each page per person that would mean the total
  displayed is per person (and not per all users).

each user gets their own instance of Page. Access to the page object
is synced on user's session (thats not exactly correct but for
purposes of this discussion it will do) so you do not have to worry
about all the nasty syncing yourself. if you have data that you want
users to share/interact with it has to be kept in some global store:
database, servlet context, memory, etc.

  Finally, if one wants to have multiple application servers for load
  balancing / failover, what options does one have with Wicket?  I assume you
  use some sort of clustered session that wicket utilizes.  Perhaps something
  like Gigaspaces?

wicket will work with regular servlet container clustering. it stores
the page in http session and page is serializable so it will be
replicated.

-igor

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



Serialisation/serialization documentation?

2008-03-12 Thread Sam Hough

Dear All,

I'm trying to get a better understanding off when/how/where Wicket
serialises components and non-transient/non-static references they hold. To
tune and sanity check our application.

Playing with writeObject, readObject I can see it writing on every ajax
request but only reading when I restart Tomcat (with serialised session
store).

I've searched around (with both spellings) but not found a recent
explanation of this.

Many thanks. I'll try not to post twice!

Thanks

Sam
-- 
View this message in context: 
http://www.nabble.com/Serialisation-serialization-documentation--tp16002654p16002654.html
Sent from the Wicket - User mailing list archive at Nabble.com.


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



Re: Serialisation/serialization documentation?

2008-03-12 Thread Sebastiaan van Erk

Look for page store in the archives and the IPageStore interface.

To get your application to deserialize stuff, simply press the back 
button on a wicket page, and click on a wicket link in the resulting 
page. That should get your page loaded from the page store.


Regards,
Sebastiaan

Sam Hough wrote:

Dear All,

I'm trying to get a better understanding off when/how/where Wicket
serialises components and non-transient/non-static references they hold. To
tune and sanity check our application.

Playing with writeObject, readObject I can see it writing on every ajax
request but only reading when I restart Tomcat (with serialised session
store).

I've searched around (with both spellings) but not found a recent
explanation of this.

Many thanks. I'll try not to post twice!

Thanks

Sam


smime.p7s
Description: S/MIME Cryptographic Signature


Re: Serialisation/serialization documentation?

2008-03-12 Thread Sebastiaan van Erk
I just remember Johan gave a presentation about this at the last WUG in 
Amsterdam:


http://www.slideshare.net/jcompagner/session-stores-page-maps-and-pages

Regards,
Sebastiaan

Sam Hough wrote:

Dear All,

I'm trying to get a better understanding off when/how/where Wicket
serialises components and non-transient/non-static references they hold. To
tune and sanity check our application.

Playing with writeObject, readObject I can see it writing on every ajax
request but only reading when I restart Tomcat (with serialised session
store).

I've searched around (with both spellings) but not found a recent
explanation of this.

Many thanks. I'll try not to post twice!

Thanks

Sam


smime.p7s
Description: S/MIME Cryptographic Signature


Re: Serialisation/serialization documentation?

2008-03-12 Thread Sam Hough

Thanks Sebastiaan,

How does serialisation kick in when using Ajax? ie Same page all the time


Sebastiaan van Erk wrote:
 
 Look for page store in the archives and the IPageStore interface.
 
 To get your application to deserialize stuff, simply press the back 
 button on a wicket page, and click on a wicket link in the resulting 
 page. That should get your page loaded from the page store.
 
 Regards,
 Sebastiaan
 
 Sam Hough wrote:
 Dear All,
 
 I'm trying to get a better understanding off when/how/where Wicket
 serialises components and non-transient/non-static references they hold.
 To
 tune and sanity check our application.
 
 Playing with writeObject, readObject I can see it writing on every ajax
 request but only reading when I restart Tomcat (with serialised session
 store).
 
 I've searched around (with both spellings) but not found a recent
 explanation of this.
 
 Many thanks. I'll try not to post twice!
 
 Thanks
 
 Sam
 
  
 

-- 
View this message in context: 
http://www.nabble.com/Serialisation-serialization-documentation--tp16002654p16007427.html
Sent from the Wicket - User mailing list archive at Nabble.com.


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



Re: Serialisation/serialization documentation?

2008-03-12 Thread Eelco Hillenius
On Wed, Mar 12, 2008 at 9:44 AM, Sam Hough [EMAIL PROTECTED] wrote:

  Thanks Sebastiaan,

  How does serialisation kick in when using Ajax? ie Same page all the time

Same page but different versions. Each page version is separately serialized.

Eelco

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



Re: Where to find documentation for Wicket tags?

2008-02-21 Thread Igor Vaynberg
there is a wiki page that lists them...

-igor

On Thu, Feb 21, 2008 at 11:09 AM, MYoung [EMAIL PROTECTED] wrote:

  Are they documented?
  --
  View this message in context: 
 http://www.nabble.com/Where-to-find-documentation-for-Wicket-tags--tp15618680p15618680.html
  Sent from the Wicket - User mailing list archive at Nabble.com.


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



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



Re: Where to find documentation for Wicket tags?

2008-02-21 Thread Scott Swank
On the wiki

http://cwiki.apache.org/WICKET/wickets-xhtml-tags.html


On Thu, Feb 21, 2008 at 11:09 AM, MYoung [EMAIL PROTECTED] wrote:

  Are they documented?
  --
  View this message in context: 
 http://www.nabble.com/Where-to-find-documentation-for-Wicket-tags--tp15618680p15618680.html
  Sent from the Wicket - User mailing list archive at Nabble.com.


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





-- 
Scott Swank
reformed mathematician

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



Where to find documentation for Wicket tags?

2008-02-21 Thread MYoung

Are they documented?
-- 
View this message in context: 
http://www.nabble.com/Where-to-find-documentation-for-Wicket-tags--tp15618680p15618680.html
Sent from the Wicket - User mailing list archive at Nabble.com.


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



Re: Where to find documentation for Wicket tags?

2008-02-21 Thread Claudio Miranda

http://cwiki.apache.org/WICKET/wickets-xhtml-tags.html


MYoung wrote:
 
 Are they documented?
 


-
Claudio Miranda
http://weblogs.java.net/blog/claudio
http://www.claudius.com.br/blog
-- 
View this message in context: 
http://www.nabble.com/Where-to-find-documentation-for-Wicket-tags--tp15618680p15618719.html
Sent from the Wicket - User mailing list archive at Nabble.com.


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



Re: ExternalLink documentation enhancement

2007-09-22 Thread Kent Tong


Chris Colman wrote:
 
 I would have thought that an external link without any protocol prefix
 should always default to an absolute link to an http:// page and not a
 relative link from the current page. Being an external link, by
 definition, it could never be a relative link from the current page I
 wouldn't think.
 

You can indeed use a relative url without a scheme such as:

   //foo.com/bar.html 

then it will mean http://foo.com/bar.html if the current url uses the 
http scheme. It can't force you to use http though as you may
want mailto or https or something else.
-- 
View this message in context: 
http://www.nabble.com/Stripping-Javascript-comments-breaks-application-tf4478522.html#a12834564
Sent from the Wicket - User mailing list archive at Nabble.com.


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



Re: Authentication in Webapp and Wicket documentation...

2007-08-09 Thread Maurice Marrink
I'll let one of the developers go into more detail about the
documentation issue :)
Regarding security there are several sub projects for you to choose.
and i would like to refer to this page for an overview of the
differences 
http://wicketstuff.org/confluence/display/STUFFWIKI/Security+Framework+Comparison
From there you should be able to find more information although a good
place to look is also the old sourceforge mailinglist.

Maurice

On 8/9/07, Alexander Schatten [EMAIL PROTECTED] wrote:
 Greetings to all Wicket experts

 I try to get Wicket running for some rather simple web-application.
 First (no offense, but have to say that), Wicket has the worst
 documentation of an apparently good open source project I have seen in a
 long time; and this is really a pity, because it seems, that if one
 would know how to do it, many things can be performed quite easily.

 Now to my current issue: I want to add a loginpage to my project and
 protect some of the pages.

 My first thought was to make a base class (worked) and somehow hook into
 the lifecycle, check if the user is checked in (MySessio works) but this
 is not running at all. lot of redirection errors, incoherent
 documentation and so on. e.g.:

 Javadoc 1.3 of Page talks about checkAccess() method... however, this
 methdod can be found nowhere.

 Now I check the mailing list archive, only useful thing I find is a
 posting from 9.2.2006 suggesting:

 protected void init()
  {
  getSecuritySettings().setAuthorizationStrategy(new
 IAuthorizationStrategy()
  {
  public boolean authorizeAction(...) ...
  public boolean authorizeInstantiation(...) ...
  }

 starting with 1.2. Well, this interface is still here, but these methods
 are not available any longer.

 There is no documentation about this strategy I could find and the
 Javadoc (which is btw. not linked from the wicket website, and just this
 made me search for an hour) is very unconclusive.


 btw. another thing: when the documentation of a project is so bad, at
 least the javadoc should be accessible: I tried to build mvn site with
 wicket and got the error that you use a special template or somthing and
 it does not build, and this template is apparently not in the repository
 ARRRGGHHH.


 sorry, but Wicket experience was far away from beeing pleasent. I am
 quite willing to check several sources, but this here is really bad.
 outdated information is not easy to distinguish from actual
 documentation, the reference to the component doc is nice, but component
 doc very incomplete and so on...

 Wicket seems to be a quite productive and powerful framework (one of the
 best I have seen so far, at least so it seems), but getting into it is a
 damn frustrating experience, I can tell you...

 (I did not even know where to start. happyily there is a maven archetype
 at the Jetty website which was helpful.)



 So, sorry for that outburst, but I was so frustrated...


 best greetings


 Alex


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



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



Re: Authentication in Webapp and Wicket documentation...

2007-08-09 Thread Martijn Dashorst
http://cwiki.apache.org/WICKET/framework-documentation.html

On 8/9/07, Alexander Schatten [EMAIL PROTECTED] wrote:
 I completly agree; just one addition: best-practices are completly
 missing in the introduction. at least a list what is available!!

 how should I know, that there is apparently an authentication framework?
 how do I access DAOs properly? there is support for working with
 databases (is there?)

 there is apparently a validation framework. I cam so far to understand
 (by browsing javadocs and a lot of trial and error, as again,
 documentation is not coherent, wiki, javadoc) that I can add validation
 rules to form elements, like this field should be min 5 max 10 chars and
 the like. ok, I have it running so far, that no other entries are
 excepted in this field, but I have no idea how I can react within the
 application for wrong entries, missing entries (you would want to give
 the user feedback that an entry was wrong). so where is the hook?

 how is the lifecycle of objects? where do I hook in to do special
 things? always in the constructor? somewhere else...? (there was a
 similar posting on this list recently)

 these are just examples: accidentally you stumble over a feature, that
 you were just on implementing yourself, and then it takes hours or days
 to figure out how to use it properly.

 again: extremly frustrating.



 Johan Maasing wrote:
  I have been playing with wicket for the last week. I must agree with
  what Alexander says. The documentation is rather lacking and quite
  frustrating. To bad because wicket is cool. So +1 for better docs.
  As a newbie to wicket I can't help in writing it but I can tell you
  what I find frustrating:
 
  The javadocs is not linked from the wicket site, it was hard to find
  even using google.
 
  The component reference is not complete. The examples have a link to
  'view source' but it does not say which files to look at for a given
  example. It would be helpful if the component reference said which
  component belonged in which jar-file (wicket or wicket-extension).
  Personally I think that tapestrys component reference is helpful
  (http://tapestry.apache.org/tapestry4.1/components/index.html)
  Perhaps there could evolve some kind of javadoc convention or other
  documentation-convention for components that describes the component,
  the parameters, the css-classes the component renders and so on.
  Oh yeah, the component reference app is stateful so I constantly get
  session expired when looking at the examples, I can't for the life of
  me figure out why :-)
 
  It was a bit hard to find a reference to the wicket-tags, at least it
  is linked from wiki, but a schema-file would be helpful to get command
  completion in the HTML-editor.
 


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




-- 
Wicket joins the Apache Software Foundation as Apache Wicket
Apache Wicket 1.3.0-beta2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/

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



Re: Authentication in Webapp and Wicket documentation...

2007-08-09 Thread Igor Vaynberg
On 8/8/07, Alexander Schatten [EMAIL PROTECTED] wrote:

 Greetings to all Wicket experts

 I try to get Wicket running for some rather simple web-application.
 First (no offense, but have to say that), Wicket has the worst
 documentation of an apparently good open source project I have seen in a
 long time; and this is really a pity, because it seems, that if one
 would know how to do it, many things can be performed quite easily.


have you seen the wiki?

Now to my current issue: I want to add a loginpage to my project and
 protect some of the pages.

 My first thought was to make a base class (worked) and somehow hook into
 the lifecycle, check if the user is checked in (MySessio works) but this
 is not running at all. lot of redirection errors, incoherent
 documentation and so on. e.g.:


have you started by checking out Signin, Signin2, Authentication,
Authorization examples in wicket-examples?

Javadoc 1.3 of Page talks about checkAccess() method... however, this
 methdod can be found nowhere.


yes the javadoc is outdated, fixed

Now I check the mailing list archive, only useful thing I find is a
 posting from 9.2.2006 suggesting:

 protected void init()
  {
  getSecuritySettings().setAuthorizationStrategy(new
 IAuthorizationStrategy()
  {
  public boolean authorizeAction(...) ...
  public boolean authorizeInstantiation(...) ...
  }

 starting with 1.2. Well, this interface is still here, but these methods
 are not available any longer.

 There is no documentation about this strategy I could find and the
 Javadoc (which is btw. not linked from the wicket website, and just this
 made me search for an hour) is very unconclusive.


we are working on linking the javadoc...you do know wicket is a maven
project right? so there is of course javadoc in the maven repo:

http://repo1.maven.org/maven2/org/apache/wicket/wicket/1.3.0-beta2/

further, since it is open source simply attach the sources to your ide and
you are set.
if you are using maven2 and eclipse add the wicket dep to your pom and do
mvn eclipse:eclipse -DdownloadSources=true - and you are all set.

now that you have found IAuthorizationStrategy have you even looked at it?
for example have you pulled up its class hieararchy to see an example
implementation? for example when i do it it leads me directly to
SimplePageAuthorizationStrategy - which will probably get you started - even
if you havent looked at the 4 examples i have mentioned.

btw. another thing: when the documentation of a project is so bad, at
 least the javadoc should be accessible: I tried to build mvn site with
 wicket and got the error that you use a special template or somthing and
 it does not build, and this template is apparently not in the repository
 ARRRGGHHH.


yes working on that too. maven2 site generation is a pita and eats up a lot
of time to get working.

sorry, but Wicket experience was far away from beeing pleasent. I am
 quite willing to check several sources, but this here is really bad.


have you gotten the Pro Wicket book?

outdated information is not easy to distinguish from actual
 documentation, the reference to the component doc is nice, but component
 doc very incomplete and so on...


you are more then welcome to help out.

Wicket seems to be a quite productive and powerful framework (one of the
 best I have seen so far, at least so it seems), but getting into it is a
 damn frustrating experience, I can tell you...


you are meant to look at examples first. they cover all the basic usecases.
learn-by-example has been our philosophy so far.

(I did not even know where to start. happyily there is a maven archetype
 at the Jetty website which was helpful.)

So, sorry for that outburst, but I was so frustrated...


no problem

-igor


best greetings


 Alex


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




Re: Authentication in Webapp and Wicket documentation...

2007-08-09 Thread Alexander Schatten

Martijn Dashorst wrote:

http://cwiki.apache.org/WICKET/framework-documentation.html




thank you; but you see, this is again one of the things I mentioned!!

when you follow the link (wiki) from the main Wicket page, you come here:

http://cwiki.apache.org/WICKET/reference-library.html

the link you suggested (thanks for that one) is:


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



Re: Authentication in Webapp and Wicket documentation...

2007-08-09 Thread Alexander Schatten

Martijn Dashorst wrote:

http://cwiki.apache.org/WICKET/framework-documentation.html



sorry, I sent the last email to quick, was a Mistake; what I wanted to 
point out is this:


http://cwiki.apache.org/WICKET/framework-documentation.html

this is your link, and it apparently has interesting information, 
whereas when you search (as probably every newbie would) starting from 
the wicket website, you go to the wiki and reference info, you come to:


http://cwiki.apache.org/WICKET/reference-library.html


now: this is what I meant before with very confusing documentation: 
these two pages apparently cover similar topics, but are different in 
details. then there is the confusing component reference plus the 
javadoc which is also misleading sometimes (see the authentication stuff 
with reference to non-existing methods).


don't you think this information base should be consolidated?



thank you very much



Alex


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



Re: Authentication in Webapp and Wicket documentation...

2007-08-09 Thread Igor Vaynberg
so how do you propose we consolidate it?

instead of javadoc have links to the wiki?

/**
 * see wicket.apache.org/wiki/authstrat
 */
public interface IAuthorizationStrategy {...}

that would really really suck.

-igor


On 8/9/07, Alexander Schatten [EMAIL PROTECTED] wrote:

 Martijn Dashorst wrote:
  http://cwiki.apache.org/WICKET/framework-documentation.html
 

 sorry, I sent the last email to quick, was a Mistake; what I wanted to
 point out is this:

 http://cwiki.apache.org/WICKET/framework-documentation.html

 this is your link, and it apparently has interesting information,
 whereas when you search (as probably every newbie would) starting from
 the wicket website, you go to the wiki and reference info, you come to:

 http://cwiki.apache.org/WICKET/reference-library.html


 now: this is what I meant before with very confusing documentation:
 these two pages apparently cover similar topics, but are different in
 details. then there is the confusing component reference plus the
 javadoc which is also misleading sometimes (see the authentication stuff
 with reference to non-existing methods).

 don't you think this information base should be consolidated?



 thank you very much



 Alex


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




Re: Authentication in Webapp and Wicket documentation...

2007-08-09 Thread Alexander Schatten
I am sorry I do completly understand your last mail. See, you pointed me 
to the interesting page


http://cwiki.apache.org/WICKET/framework-documentation.html

(1) now, from the wicket website the reference link (was changed I 
think?) points to the other page, with the similar information. It might 
be a first start to figure out (you as experts) which of the two pages 
is the relevant one and link the right one.


(2) plus at the moment, there is still no link at all to the javadoc 
from the main website: I only found this one by accident.


this might be a second very helpful step.

(3) a third one would be best-practice guide on the main website listing 
typical issues like:


-- database connection / DAOs
-- Ajax
-- authentication
-- build management (Maven)
-- logging
...
...

and make references to the existing documentation, examples plus javadoc

(4) bring a conclusive list of examples; it seems, that there are 
several sets of examples distributed on the website, the wiki, the 
distribution... also confusing. at least a conclusive list with examples 
and where to find them would be very helpful




thank you



Alex



Igor Vaynberg wrote:

so how do you propose we consolidate it?

instead of javadoc have links to the wiki?

/**
 * see wicket.apache.org/wiki/authstrat
 */
public interface IAuthorizationStrategy {...}

that would really really suck.

-igor


On 8/9/07, Alexander Schatten [EMAIL PROTECTED] wrote:

Martijn Dashorst wrote:

http://cwiki.apache.org/WICKET/framework-documentation.html


sorry, I sent the last email to quick, was a Mistake; what I wanted to
point out is this:

http://cwiki.apache.org/WICKET/framework-documentation.html

this is your link, and it apparently has interesting information,
whereas when you search (as probably every newbie would) starting from
the wicket website, you go to the wiki and reference info, you come to:

http://cwiki.apache.org/WICKET/reference-library.html


now: this is what I meant before with very confusing documentation:
these two pages apparently cover similar topics, but are different in
details. then there is the confusing component reference plus the
javadoc which is also misleading sometimes (see the authentication stuff
with reference to non-existing methods).

don't you think this information base should be consolidated?



thank you very much



Alex


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







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



Re: Authentication in Webapp and Wicket documentation...

2007-08-09 Thread Eelco Hillenius
 honestly spoken, this is not the best strategy for everyone...

Obviously. But we have limited resources (no-one is paid for working
on Wicket), so it is hard to cater to everyone. We have tried to
attract writers (for a reference guide) from the very early start
(even offered some money) but it just doesn't seem to be a task many
people seem to be interested in doing.

 moreover,
 I think you are speaking of examples coming with the download; this
 dowload was again rather confusing (see my site problem); I am looking
 first at the exampleson the website, and there I could not find any of
 the examples you were mentioning.

What I don't get - as a regular user of open source software - what is
so difficult about just getting it from source control or creating a
quick maven based project for that? I typically dive into several
projects I didn't know before a month, and I just start with getting
it from the repo, looking at the test cases and examples and Javadocs
(which unfortunately is something most open source projects do a lot
worse at than Wicket).

 btw. this is I see now one of the real issues with the wicket docs; it
 seems, that there is actually lot available, but very cluttered, not
 properly linked and partly redundant in different versions...

We really depend on our users helping us out with that (and they have
been quite a help already). The framework is in constant development,
so this is something that needs constant attention. Help is very
welcome.

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



Re: Authentication in Webapp and Wicket documentation...

2007-08-09 Thread Eelco Hillenius
 No, actually I was not aware of that, was waiting for the Wicket in
 Action book...

http://manning.com/dashorst/

You can get the first chapters now. Two more chapters will be released
early next week.

 maybe one should also start writing some proper articles as a starting
 point; I might do that when I see clearer.

There are quite a few articles you can find if you google for it. Many
of them are for 1.2, so a bit stale if you plan to use 1.3 (which we
recommend). So keep http://cwiki.apache.org/WICKET/migrate-13.html
next to them. It's often more about the idea than that it is important
that the examples are still completely recent.

Eelco

Eelco

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



ResourceReference and Wicketstuff Dojo Documentation-related questions

2007-08-02 Thread Kirk Israel
I just discovered the jdocs for Wicket
http://www.jdocs.com/tab/91/overview-summary.html
Are there any other good, comprehensive references I should know about?

And is there a better forum for than this list for Wicketstuff-Dojo
related questions?

Specifically, I'm wondering about how to attach specific behaviors to
DojoMenuItem ; it might be following established paradigms I'm not
familiar enough with yet. When I google on DojoMenuItem nothing
documentation-y comes up.

So I guess as much as anything, I'm looking to make sure I have the
best possible reference resources to all this stuff, understanding
that a lot of stuff seems to be very lightly documented...

Also: with ResourceReference, as showin in the Wicketstuff-Dojo
Contextual menu example, does the underlying image file live in the
same directory as the .java and .html or somewhere else?

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