|
Hi,
my 2 cents:
petstore is a good thing to have in it, as it shows how
everything really works and is plugged together, spring however shouldnt be put
in a main part, more appendix or sth. like that.
For Hibernate & co. : just forget them and concentrate
on how wicket and JPA fit together, as JPA can be plugged together with
Hibernate, Toplink, Kodo and more to come and will be "the" standard for
persistence in java apps from now on. - if you ask me, JPA is the future.
Regards
Korbinian
PS: please, also remind yourself when writing that most
target developers come from a world of JSP, Struts & co meaning that they
"forgot" most of object oriented programming. They dont live in a world full of
objects but in a world of flows and tasks put together... like me as i havent
programmed OO much in last years when i was up with web developing in perl, php
& jsp.
PPS: thumbs up to Stefan for his effort :) i think this
might be a real chance to spread more wicket around.
yeah, maybe it doesn't need that. Pet store is kind of a best practices
project, so I figured it might get in there. Databinder as an alternative
would be cool with me too.
Eelco
On Oct 1, 2006, at 11:44 PM, Philip A. Chapman wrote:
Guys,
I love spring and use it with all my
wicket apps. However, should it be a part of the main body of the manual? I
wouldn't want anyone to get the idea that wicket requires spring in any way.
Perhaps it would go into an "Advanced" or "Using wicket with other
frameworks" section that could also include the use of Hibernate, Shades,
JasperReports and whatever else.
At the very least, we should make it
plain in the manual that spring is not required for the use of wicket, but
that it's being used in the example app and in the manual for reasons X,Y,
and Z.
Thanks,
On Sun, 2006-10-01 at 22:15 +0200, Eelco
Hillenius wrote:
Folks,
Stefan Kanev just volunteered to start writing on a new user guide.
He asked me to give him an idea for a TOC, so here's mine. I'm
sending this to the list in case people would like to help/ have
ideas/ ...
-----------------------------------------------
TOC user guide, Building Wicket Pet Store
1. What Is Wicket
* Explains Wicket's strong points, philosophy, etc
2. The basics
* Basic concepts, tells about Application, session, components,
markup, pages and models
3. Introducing WicketPetstore
* Describe what we'll be building, including a short look at the
domain model
* Setup project & database
* Setup Spring
* Setup the skeleton; HTML stubs and non-interactive pages
4. Browsing the store
* Implement the browsing part: list views, labels and an
introduction to models (Use compound property model here)
- Uses services wired using Spring
* Use resources to display images (with thumbnail resources)
5. Tracking the client
* Set up a custom session
* Implement shopping basket tracking, including a panel that
displays the current items in the basket
6. Working with forms
* Implement forms for adding items to the basket
* Implement validation
* Implement check out functionality
-----------------------------------------------
Good luck Stefan, and keep us informed!
Eelco
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
Philip A. Chapman
Desktop and Web Application Development:
Java, .NET, PostgreSQL, MySQL, MSSQL
Linux, Windows 2000, Windows XP
|
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of
IT
Join SourceForge.net's Techsay panel and you'll get
the chance to share your
opinions on IT & business topics through brief
surveys -- and earn cash
Wicket-user mailing list
|
